{"push_id":828227435,"size":1,"distinct_size":1,"ref":"refs/heads/feature/geopointfield_v2","head":"7c35141b625d2f4d76c86f02a4bb4fe122aa3dd0","before":"5d3b0ffe3d675b8ed7e6e8444680a34d0ab3a30d","commits":[{"sha":"7c35141b625d2f4d76c86f02a4bb4fe122aa3dd0","author":{"email":"7658bca979a635f8885feb26fcbf4288a9fb3170@apache.org","name":"Robert Muir"},"message":"Fix SeccompTests bug on older kernels\n\nThis test failed only on a feature branch, because that feature branch has\na different build randomization script and is the only place\nrandomizing tests.security.manager (this test cannot run with it enabled).\n\nOn old kernels without TSYNC support, the test fails because (surprise to me) the thread that\nruns the test is not the same thread that runs static initializers:\nhttps://github.com/randomizedtesting/randomizedtesting/blob/7571489190d677969c768836e1576f4e851f83e8/randomized-runner/src/main/java/com/carrotsearch/randomizedtesting/RandomizedRunner.java#L573-L574\n\nTo fix this test (its not an issue in practice, since we do this before creating threadpools),\nwe just record for testing purposes that we couldn't TSYNC, and re-run the whole thing for the test thread\nin setUp(), failing if something goes wrong.\n\nAlso add a bunch of additional paranoia and narrow our defensive checks better here after reading\nthrough more chrome bug reports: they don't impact us but those linux distros are too cowboy\nwith the backports and the spirit of the checks makes me feel better.","distinct":true,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/7c35141b625d2f4d76c86f02a4bb4fe122aa3dd0"}]}