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.

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

teamcity: failed test: bank/zerosum-splits #31510

Closed
cockroach-teamcity opened this issue Oct 16, 2018 · 5 comments
Closed

teamcity: failed test: bank/zerosum-splits #31510

cockroach-teamcity opened this issue Oct 16, 2018 · 5 comments
Assignees
Labels
C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot.
Milestone

Comments

@cockroach-teamcity
Copy link
Member

The following tests appear to have failed on master (roachtest): acceptance/bank/zerosum-splits

You may want to check for open issues.

#970216:

acceptance/bank/zerosum-splits
--- FAIL: roachtest/acceptance/bank/zerosum-splits (4.520s)
	test.go:584,bank.go:379,bank.go:525,acceptance.go:65: pq: splits would be immediately discarded by merge queue; disable the merge queue first by running 'SET CLUSTER SETTING kv.range_merge.queue_enabled = false'





Please assign, take a look and update the issue accordingly.

@cockroach-teamcity cockroach-teamcity added this to the 2.2 milestone Oct 16, 2018
@cockroach-teamcity cockroach-teamcity added C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot. labels Oct 16, 2018
@petermattis
Copy link
Collaborator

@m-schneider this is likely fallout of @benesch's enabling of range merges.

@benesch benesch assigned benesch and unassigned m-schneider Oct 16, 2018
@benesch
Copy link
Contributor

benesch commented Oct 16, 2018

Yup, I'm on it.

@m-schneider
Copy link
Contributor

@benesch do you think it makes sense to add the error message to acceptable messages while you work on it to deflake the test and then you can remove it?

@benesch
Copy link
Contributor

benesch commented Oct 16, 2018

Eh, I can get it fixed in the next 10m! ⌛️

benesch added a commit to benesch/cockroach that referenced this issue Oct 16, 2018
This test requires that the experimental_force_split_at session var be
set to force ALTER ... SPLIT AT to work even with the merge queue
enabled. gosql.DB's connection pool will occasionally open a new
connection which does not have the var set. Set the session var in the
same batch of statements as the ALTER ... SPLIT AT command so that the
session var is always set in the session that executes the ALTER ...
SPLIT AT command.

Fix cockroachdb#31510.

Release note: None
@benesch
Copy link
Contributor

benesch commented Oct 16, 2018

Ah, shoot, 17m. I overpromised. Anyway, this should do it: #31517

craig bot pushed a commit that referenced this issue Oct 16, 2018
31516: c-deps: bump CryptoPP to avoid SIGTRAP on macOS r=mberhault a=benesch

Bump CryptoPP to pick up a fix for #31380.
Details reproduced below.

Fix #31380.

---

As part of its CPU feature detection, CryptoPP installs a SIGILL signal
handler before issuing the cpuid instruction. The intent is to
gracefully degrade on CPUs that don't support the cpuid instruction.

The problem is that it is impossible to safely overwrite a signal
handler installed by the Go runtime in go1.10 on macOS
(golang/go#22805). This causes CockroachDB 2.0 to crash on macOS Mojave:
#31380.

The situation has improved on the Go front, as go1.11 makes it possible
to safely save and restore signal handlers installed by the Go runtime
on macOS.

Still, we can do better and support go1.10. There is no need to bother
installing a SIGILL handler, as the cpuid instruction is supported by
every x86-64 CPU. We can instead use conditional compilation to make
sure that we never execute a cpuid instruction on a non x86-64 CPU.

Note that CPU feature detection is performed at executable load time
(see the attribute(constructor) on DetectX86Features); therefore any
reference to function which calls DetectX86Features (notably HasAESNI)
corrupts the signal handler. It's not entirely clear why this corruption
later leads to the SIGTRAP seen in #31380--is
something in macOS or the Go runtime generating a SIGILL and trying to
handle it gracefully?--but regardless, not mucking with the signal
handler fixes the issue.

Release note (bug fix): CockroachDB no longer crashes due to a SIGTRAP error
soon after startup on macOS Mojave (#31380).

31517: roachtest: deflake acceptance/bank/zerosum-splits r=andreimatei a=benesch

This test requires that the experimental_force_split_at session var be
set to force ALTER ... SPLIT AT to work even with the merge queue
enabled. gosql.DB's connection pool will occasionally open a new
connection which does not have the var set. Set the session var in the
same batch of statements as the ALTER ... SPLIT AT command so that the
session var is always set in the session that executes the ALTER ...
SPLIT AT command.

Fix #31510.

Release note: None

Co-authored-by: Nikhil Benesch <[email protected]>
@craig craig bot closed this as completed in #31517 Oct 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-test-failure Broken test (automatically or manually discovered). O-robot Originated from a bot.
Projects
None yet
Development

No branches or pull requests

4 participants