Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Sporadic unit test failure: DataFrameBuilder-ObjectClosedException
See original GitHub issueProblem description Observed unit test failure due to ObjectClosedException in segment store.
Observed in travis build:
io.pravega.segmentstore.server.mocks.SynchronousStreamSegmentStoreTests > testEndToEnd FAILED
java.util.concurrent.CompletionException: io.pravega.common.ObjectClosedException: Object 'DataFrameBuilder' has been closed and cannot be accessed anymore.
Caused by:
io.pravega.common.ObjectClosedException: Object 'DataFrameBuilder' has been closed and cannot be accessed anymore.
Observed in Jenkins and local build:
io.pravega.segmentstore.server.containers.StreamSegmentContainerTests > testTransactionOperations FAILED
java.util.concurrent.ExecutionException: io.pravega.common.ObjectClosedException: Object 'DataFrameBuilder' has been closed and cannot be accessed anymore.
at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1915)
at io.pravega.segmentstore.server.containers.StreamSegmentContainerTests.testTransactionOperations(StreamSegmentContainerTests.java:659)
Caused by:
io.pravega.common.ObjectClosedException: Object 'DataFrameBuilder' has been closed and cannot be accessed anymore.
Problem location Segment store
Suggestions for an improvement Fix sporadic failures of these unit tests.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Unit tests sometimes failing, sometimes passing - Stack Overflow
Tests can fail intermittently for a number of reasons and identifying why they fail is often revealing about your codebase and environment.
Read more >Unit test not working on Xcode 14 … | Apple Developer Forums
Hello, When I lunch any Unit Test with Xcode 14 RC and iPhone 13 iOS 16 I get this error, any ideas?? Details....
Read more >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 >Diagnosing Random Angular Test Failures - WalkingRiver.com
Have you ever had an intermittent or random failure in your unit tests? ... Out of the box, your unit tests are run...
Read more >How to deal with flaky tests that have intermittent failures?
Common solutions to those problems are: do less in the test, shift from out of proc to in-proc and shift from end-to-end to...
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
I am unable to reproduce this at all on my dev machine or on my mac, even after running for thousands of times. I shall keep an eye on the builds to see if this happens again in Travis, otherwise I will close this on 7/21/2017 if I don’t see it again.
wrong already-closed object