Fix SeccompTests bug on older kernels / add defense#14126
Merged
rmuir merged 1 commit intoelastic:masterfrom Oct 15, 2015
Merged
Fix SeccompTests bug on older kernels / add defense#14126rmuir merged 1 commit intoelastic:masterfrom
rmuir merged 1 commit intoelastic:masterfrom
Conversation
This test failed only on a feature branch, because that feature branch has a different build randomization script and is the only place randomizing tests.security.manager (this test cannot run with it enabled). On old kernels without TSYNC support, the test fails because (surprise to me) the thread that runs the test is not the same thread that runs static initializers: https://github.com/randomizedtesting/randomizedtesting/blob/7571489190d677969c768836e1576f4e851f83e8/randomized-runner/src/main/java/com/carrotsearch/randomizedtesting/RandomizedRunner.java#L573-L574 To fix this test (its not an issue in practice, since we do this before creating threadpools), we just record for testing purposes that we couldn't TSYNC, and re-run the whole thing for the test thread in setUp(), failing if something goes wrong. Also add a bunch of additional paranoia and narrow our defensive checks better here after reading through more chrome bug reports: they don't impact us but those linux distros are too cowboy with the backports and the spirit of the checks makes me feel better.
Member
|
LGTM |
rmuir
added a commit
that referenced
this pull request
Oct 15, 2015
Fix SeccompTests bug on older kernels / add defense
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This test failed only on a feature branch, because that feature branch has
a different build randomization script and is the only place
randomizing tests.security.manager (this test cannot run with it enabled).
On old kernels without TSYNC support, the test fails because (surprise to me) the thread that
runs the test is not the same thread that runs static initializers:
https://github.com/randomizedtesting/randomizedtesting/blob/7571489190d677969c768836e1576f4e851f83e8/randomized-runner/src/main/java/com/carrotsearch/randomizedtesting/RandomizedRunner.java#L573-L574
To fix this test (its not an issue in practice, since we do this before creating threadpools),
we just record for testing purposes that we couldn't TSYNC, and re-run the whole thing for the test thread in setUp(), failing if something goes wrong.
Also add a bunch of additional paranoia and narrow our defensive checks better here after reading
through more chrome bug reports: they don't impact us but those linux distros are too cowboy
with the backports and the spirit of the checks makes me feel better.