Tests are making the installation to loop forever
See original GitHub issueWhen I tried to install the project using maven 3.6 with the command mvn install
at some point the installation kind of “stopped” without proceeding for about 7 hours. After that I stopped it manually. When providing the clean install with no tests - mvn clean install -DskipTests=true
it was installed successfully.
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Running Jest tests loop forever - Stack Overflow
It turns out that the jest.setup file was writing a configuration file to disk, while setting up a temporary mongoDB.
Read more >Infinite build loop when running selected CTests tests
I have a CMake solution with a Google Test project. If, via Test Explorer, I click “Run All” tests, the tests are run...
Read more >Test with infinite loop in TearDown cannot be aborted #352
An infinite loop in the SetUp is handled the same as one in the test but a loop in TearDown causes the entire...
Read more >Easy Fix: Yarn OR NPM install / Test Infinite Loop Error
This video covers solving a ridiculously trivial error that I had earlier with yarn install.
Read more >Unit Test How? Infinite Loops - Mark.VanderVoord
But, an infinite loop is a great place to apply our powerful TEST define friend. We're going to create a macro called FOREVER....
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 FreeTop 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
Top GitHub Comments
Thanks @xxLestadxx. We’ve seen a few reports from other sources for the same issue, and with the same file handle limit. I recreated inside a Vagrant VM, with that same limit, and the test took 20 minutes to run. Although it was a VM, it is still quite a powerful machine, so machines with lower specs will take even longer.
I opened a pull request to bypass the test for high limits. Our local development and the Travis CI limit as both lower than the bypass requisite, so we still make sure the coverage is kept.
Thanks for reporting!
Ok, thanks. I see this thread as well on Slack: https://go-quorum.slack.com/archives/C68NY0QQZ/p1568024356139900
Looking at the
CmdLineExecutorTest
, there is one possible culprit:directoryStoreAndSqliteWithLotsOfFilesWorks
. This test reads/writes LOTS of files, so it may be slow on systems with slow read/write speeds. Still, I would not have expected it to stall for 7 hours. I’ll see if we can reduce the strain the the test causes (if it is the cause).