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

CharArraysTests#testCharsBeginsWith fails with an assertion error. #34765

Closed
jtibshirani opened this issue Oct 23, 2018 · 2 comments · Fixed by #34816
Closed

CharArraysTests#testCharsBeginsWith fails with an assertion error. #34765

jtibshirani opened this issue Oct 23, 2018 · 2 comments · Fixed by #34816
Assignees
Labels
:Core/Infra/Core Core issues without another label >test-failure Triaged test failures from CI

Comments

@jtibshirani
Copy link
Contributor

jtibshirani commented Oct 23, 2018

The failure reliably reproduces for me locally on master and 6.x.


Link to the build: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+matrix-java-periodic/ES_BUILD_JAVA=java11,ES_RUNTIME_JAVA=java11,nodes=virtual&&linux/14/console

Command to reproduce:

./gradlew :libs:core:test \
  -Dtests.seed=35653EB3A532F612 \
  -Dtests.class=org.elasticsearch.common.CharArraysTests \
  -Dtests.method="testCharsBeginsWith" \
  -Dtests.security.manager=true \
  -Dtests.locale=ar-DZ \
  -Dtests.timezone=Africa/Bujumbura \
  -Dcompiler.java=11 \
  -Druntime.java=11

Relevant excerpt from the logs:

FAILURE 0.39s | CharArraysTests.testCharsBeginsWith <<< FAILURES!
   > Throwable #1: java.lang.AssertionError
   >    at __randomizedtesting.SeedInfo.seed([35653EB3A532F612:78C0CECE95797639]:0)
   >    at org.elasticsearch.common.CharArraysTests.testCharsBeginsWith(CharArraysTests.java:50)
   >    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   >    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
   >    at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   >    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
   >    at java.base/java.lang.Thread.run(Thread.java:834)
@jtibshirani jtibshirani added :Core/Infra/Core Core issues without another label >test-failure Triaged test failures from CI labels Oct 23, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@jtibshirani
Copy link
Contributor Author

Muted the test in 5a4866f.

@jaymode jaymode self-assigned this Oct 24, 2018
jaymode added a commit to jaymode/elasticsearch that referenced this issue Oct 24, 2018
The testCharsBeginsWith test has a check that a random prefix of length
2 is not the prefix of a char[]. However, there is no check that the
char[] is not randomly generated with the same two characters as the
prefix. This change ensures that the char[] does not begin with the
prefix.

Closes elastic#34765
jaymode added a commit that referenced this issue Oct 25, 2018
The testCharsBeginsWith test has a check that a random prefix of length
2 is not the prefix of a char[]. However, there is no check that the
char[] is not randomly generated with the same two characters as the
prefix. This change ensures that the char[] does not begin with the
prefix.

Closes #34765
jaymode added a commit that referenced this issue Oct 25, 2018
The testCharsBeginsWith test has a check that a random prefix of length
2 is not the prefix of a char[]. However, there is no check that the
char[] is not randomly generated with the same two characters as the
prefix. This change ensures that the char[] does not begin with the
prefix.

Closes #34765
kcm pushed a commit that referenced this issue Oct 30, 2018
The testCharsBeginsWith test has a check that a random prefix of length
2 is not the prefix of a char[]. However, there is no check that the
char[] is not randomly generated with the same two characters as the
prefix. This change ensures that the char[] does not begin with the
prefix.

Closes #34765
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Core Core issues without another label >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants