Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

bazel,ci: link error when running tests under race #73997

Closed
rickystewart opened this issue Dec 17, 2021 · 0 comments · Fixed by #74110
Closed

bazel,ci: link error when running tests under race #73997

rickystewart opened this issue Dec 17, 2021 · 0 comments · Fixed by #74110
Assignees
@rickystewart
Labels
A-ci Continuous Integration C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. T-dev-inf

Comments

@rickystewart
Copy link
Collaborator 

[15:07:24][Run stress tests] _cgo_callers: relocation target x_cgo_callers not defined
[15:07:24][Run stress tests] _cgo_init: relocation target x_cgo_init not defined
[15:07:24][Run stress tests] _cgo_mmap: relocation target x_cgo_mmap not defined
[15:07:24][Run stress tests] _cgo_munmap: relocation target x_cgo_munmap not defined
[15:07:24][Run stress tests] _cgo_notify_runtime_init_done: relocation target x_cgo_notify_runtime_init_done not defined
[15:07:24][Run stress tests] _cgo_sigaction: relocation target x_cgo_sigaction not defined
[15:07:24][Run stress tests] _cgo_thread_start: relocation target x_cgo_thread_start not defined
[15:07:24][Run stress tests] external/go_sdk/pkg/tool/linux_amd64/link: too many errors
[15:07:24][Run stress tests] unexpected fault address 0x7f4a812f2120
[15:07:24][Run stress tests] fatal error: fault
[15:07:24][Run stress tests] unexpected fault address 0x7f4a811f2020

#73805
https://teamcity.cockroachdb.com/viewLog.html?buildId=3942375&tab=buildResultsDiv&buildTypeId=Cockroach_Ci_Tests_MaybeStressrace

Epic CRDB-8306
@rickystewart rickystewart added C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. T-dev-inf A-ci Continuous Integration labels Dec 17, 2021
@adityamaru adityamaru mentioned this issue Dec 17, 2021
Merged
@rickystewart rickystewart mentioned this issue Dec 20, 2021
Merged
craig bot pushed a commit that referenced this issue Dec 21, 2021
@knz @RaduBerinde
@cucaroach @mgartner @rickystewart @ajwerner
Merge #72992 #73937 #73978 #74102 #74110 #74111 #74152
779f08b 
72992: util/log: fix redactability of logging tags r=abarganier a=knz

Fixes #72905.

Some time in the v21.2 cycle, the log entry preparation logic was
refactored and a mistake was introduced: the logging tags were not any
more subject to the redaction logic. The result was that redaction
markers were missing in log tag values, and if a value had contained
unbalanced redaction markers in a value string (say, as part of a SQL
table key), it would have caused log file corruption and possibly a
confidential data leak.

This patch fixes that, by preparing the logging tags in the same way
as the main message for each entry.

Release note (cli change): A bug affecting the redactability of
logging tags in output log entries has been fixed. This bug had
been introduced in the v21.2 release.

73937: setting: introduce setting classes r=RaduBerinde a=RaduBerinde

This commit introduces the three setting classes in the RFC (#73349):
`SystemOnly`, `TenantReadOnly`, and `TenantWritable`. The `SystemOnly`
class replaces the existing `WithSystemOnly()`.

In this change we don't yet implement the advertised semantics. We
mechanically use `TenantWritable` for all settings except those that
were using `WithSystemOnly()` which use `SystemOnly`; this should not
change any existing behavior. The classes will be revisited in a
separate change, after we implement the semantics.

Release note: None

73978: opt: fix like escape processing for span constraints r=cucaroach a=cucaroach

Fixes: #44123

Previously no attempt was made to properly handle escape ('\\') sequence
in like patterns being turned into constraints. Refactor code used to
process like at runtime to generate a regexp and use that to properly
handle index constraint generation.

Release note (sql change): Escape character processing was missing from
constraint span generation which resulted in incorrect results when
doing escaped like lookups.

74102: sql: do not fetch virtual columns during backfill r=mgartner a=mgartner

Fixes #73372

Release note (bug fix): A bug has been fixed that caused internal errors
when altering the primary key of a table. The bug was only present if
the table had a partial index with a predicate that referenced a virtual
computed column. This bug was present since virtual computed columns
were added in version 21.1.0.

74110: bazel: require setting `cockroach_cross=y` to opt into cross toolchains r=irfansharif a=rickystewart

With `--incompatible_enable_cc_toolchain_resolution` set in #73819, now
Bazel selects the appropriate toolchain for you. Bazel was selecting the
`cross_linux_toolchain` when building for the host platform on Linux,
resulting in link errors when trying to compile `stress` under `race`.
We update the toolchains to instead require opting into the cross
toolchains by defining `cockroach_cross=y`.

Closes #73997.

Release note: None

74111: bench/rttanalysis: allow roundtrips to be off by 1 r=ajwerner a=ajwerner

If we don't have a range, let the currently estimate be wrong by 1.
We mostly care about the ballpark and the growth rate. I'm sick of
these flakes.

Fixes #73884.

Release note: None

74152: ci: don't delete `test.json.txt` after processing r=tbg a=rickystewart

We've seen some issues where Bazel jobs are failing in `github-post`
(#73841, #74013) with the following output:

    found outstanding output. Considering last test failed:

It's hard to say what the problem is because these scripts haven't kept
the `test.json.txt` in `artifacts`. Here I remove the logic to clean up
the file so we can RC further instances of the problem.

Release note: None

Co-authored-by: Raphael 'kena' Poss <[email protected]>
Co-authored-by: Radu Berinde <[email protected]>
Co-authored-by: Tommy Reilly <[email protected]>
Co-authored-by: Marcus Gartner <[email protected]>
Co-authored-by: Ricky Stewart <[email protected]>
Co-authored-by: Andrew Werner <[email protected]>
@craig craig bot closed this as completed in 59f8eaa Dec 21, 2021
gustasva pushed a commit to gustasva/cockroach that referenced this issue Jan 4, 2022
@rickystewart
bazel: require setting cockroach_cross=y to opt into cross toolchains
a8aed70 
With `--incompatible_enable_cc_toolchain_resolution` set in cockroachdb#73819, now
Bazel selects the appropriate toolchain for you. Bazel was selecting the
`cross_linux_toolchain` when building for the host platform on Linux,
resulting in link errors when trying to compile `stress` under `race`.
We update the toolchains to instead require opting into the cross
toolchains by defining `cockroach_cross=y`.

Closes cockroachdb#73997.

Release note: None
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rickystewart rickystewart

Labels
A-ci Continuous Integration C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. T-dev-inf
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

bazel: require setting cockroach_cross=y to opt into cross toolchains rickystewart/cockroach
1 participant
@rickystewart