-
Notifications
You must be signed in to change notification settings - Fork 747
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
testComplexSuggestions2, testGetPopularityDataAll sometimes fails #2704
Comments
like in https://travis-ci.org/oracle/opengrok/jobs/499311368 but I have also seen the failures in AppVeyor builds. |
The job you provided is still running and I see no logs :/ |
Sorry, just restarted the build because this was a release build.
Dne st 27. 2. 2019 17:01 uživatel Adam Hornáček <notifications@github.com>
napsal:
… From my experience it fails because of this race condition which is
bugging us for a long time: #2030
<#2030>
The link you provided is still running and I see no logs :/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2704 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACzGDGslvbm4dxSosDInUKTR1Lt2TtaTks5vRqvCgaJpZM4bU2fm>
.
|
Getting more failure in
|
The await().atMost(15, TimeUnit.SECONDS).until(() ->
getSuggesterProjectDataSize() == env.getProjectList().size()); which makes me wonder whether this is enough and how/if Awaitility provides any feedback/log if the timeout expired and the condition is not met. |
Also, for both the failed cases listed above the setup of the test reported:
For completeness, this was on Windows with OpenJDK 8. |
w.r.t. suggester timeouts: both failed cases listed above had:
so it seems the 15 seconds is enough. |
The question is whether the failure to initialize Chronicle map can lead to the observed test case failures, i.e. if there is a implicit dependency. Given that the failed test cases do test popularity, this seems plausible. |
added a catch for
|
Added a "debug" print to
|
Both numbers on the right side of the expression here
NaN for the double value (that will be represented as Double in the averageLengths map).
|
The workaround could be not to put the entry to the |
Interestingly the setup/tests seems to fail only when failing to build average lengths map for field |
Actually, the |
The popularity tests fail because the term count cannot be updated using |
It seems that the trouble is that In one of the failed cases the log goes like this:
We can see this sequence of events:
|
When |
I found out that When the Anyhow, either ordering is not good - if the |
The text was updated successfully, but these errors were encountered: