Closed volodya-lombrozo closed 1 week ago
@volodya-lombrozo maybe you should wait a bit longer. On my machine I'm getting this:
[INFO] --- failsafe:3.5.2:integration-test (snippet-test) @ eo-runtime ---
[WARNING] useSystemClassLoader setting has no effect when not forking
[WARNING] The parameter forkCount should likely not be 0. Forking a JVM for tests improves test accuracy. Ensure to have a <forkCount> >= 1.
[INFO] Tests will run in random order. To reproduce ordering use flag -Dfailsafe.runOrder.random.seed=1543381430071541
[INFO] Failsafe report directory: /Volumes/sec/code/o/eo/eo-runtime/target/failsafe-reports
[INFO] Using auto detected provider org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
[INFO] Running org.eolang.PhiUnphiIT
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.750 s -- in org.eolang.PhiUnphiIT
[INFO] Running org.eolang.SnippetIT
[INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 226.3 s -- in org.eolang.SnippetIT
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0
@yegor256 Well, I managed to wait around ~11 min and it passed. But the problem is still here:
mvn clean test
, we actually run integration tests? I didn't call mvn clean integration-test
.@volodya-lombrozo are you sure mvn clean test
runs those integration tests? I just checked and they don't (on my machine):
mvn test -pl :eo-runtime
@volodya-lombrozo after 6ae091863, it should be a bit better
@yegor256 Yes, it is a bit better, thank you:
[INFO] Running org.eolang.SnippetIT
WARN c.y.MayBeSlow - We're still running runsAllSnippets[#2] (6s), please wait...
WARN c.y.MayBeSlow - We're still running runsAllSnippets[#2] (16s), please wait...
WARN c.y.MayBeSlow - We're still running runsAllSnippets[#2] (31s), please wait...
WARN c.y.MayBeSlow - We're still running runsAllSnippets[#2] (51s), please wait...
I cloned the recent version of the repository, then run
and after some time, the process stacked with the following message:
And nothing happens. It just doing something for a long time. I waited around
~5 min
and stopped the test. I believe we should remove this test from "unit" tests and add at least some logging.