Broken or Flaky test: ExternalCompaction_2_IT
See original GitHub issueTest name(s)
- org.apache.accumulo.test.compaction.ExternalCompaction_2_IT.testExternalCompactionsSucceedsRunWithTableOffline
Describe the failure observed
[ERROR] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 105.877 s <<< FAILURE! - in org.apache.accumulo.test.compaction.ExternalCompaction_2_IT
[ERROR] org.apache.accumulo.test.compaction.ExternalCompaction_2_IT.testExternalCompactionsSucceedsRunWithTableOffline Time elapsed: 9.167 s <<< FAILURE!
java.lang.AssertionError: expected:<STARTED> but was:<SUCCEEDED>
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.failNotEquals(Assert.java:835)
at org.junit.Assert.assertEquals(Assert.java:120)
at org.junit.Assert.assertEquals(Assert.java:146)
at org.apache.accumulo.test.compaction.ExternalCompactionTestUtils.confirmCompactionRunning(ExternalCompactionTestUtils.java:278)
at org.apache.accumulo.test.compaction.ExternalCompaction_2_IT.testExternalCompactionsSucceedsRunWithTableOffline(ExternalCompaction_2_IT.java:196)
Testing Environment:
- Version of this project: 2.1.0-SNAPSHOT
- First commit known to fail (or current commit): 4ce9ab25d061a7cb1f79b49746637b91c22c40ec
Executing Maven: -B -f /var/lib/jenkins/workspace/2.1/pom.xml -V verify -Dfailsafe.rerunFailingTestsCount=5
Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Maven home: /var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.8.1
Java version: 11.0.14, vendor: Red Hat, Inc., runtime: /usr/lib/jvm/java-11-openjdk-11.0.14.0.9-2.fc35.x86_64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.16.8-200.fc35.x86_64", arch: "amd64", family: "unix"
What have you tried already? Jenkins re-ran the test and it passed the second time
Additional context N/A
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
How to Fix Flaky Tests - Semaphore CI
Randomly failing tests are the hardest to debug. Here's a framework you can use to fix them and keep your test suite healthy....
Read more >A Practical Guide to Reducing the Burden of Flaky Tests
Flaky tests can be frustrating and detrimental to your testing efforts. This post covers what causes flaky tests and what you can do...
Read more >Handling Flaky Tests at Scale: Auto Detection & Suppression
At this point, on the main branch the test is actually broken but it keeps running and being filtered out on CI from...
Read more >Flaky Tests: Getting Rid Of A Living Nightmare In Testing
A flaky test is one that fails to produce the same result each time the same analysis is run. The build will fail...
Read more >8 Common Causes of Flaky Tests in Elixir - AppSignal Blog
Flaky tests are tests that sometimes fail. They erode confidence in your test suite and are hard to fix because they are hard...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The test code is not communicating with the Compactor. I think what I can do is have each test use a different compaction queue. Then, if a Compactor is running from a previous test for some reason, it won’t pick up the compaction. I’ll start on that change now. Is ExternalCompaction2_IT the only one currently failing?
I think you are right. I haven’t seen it fail once since this change. My bet would be the distinct queue names did the trick. They seem to be very reliable now.