afs commented on code in PR #2329:
URL: https://github.com/apache/jena/pull/2329#discussion_r1522124611
##########
jena-geosparql/src/test/java/org/apache/jena/ext/io/github/galbiston/expiring_map/ExpiringMapTest.java:
##########
@@ -441,6 +437,7 @@ public void testExpiry_change_expiry_interval_reduced()
throws InterruptedExcept
*
* @throws java.lang.InterruptedException
*/
+ @Ignore // This test is not stable on loaded CI servers.
Review Comment:
This test has been unstable on all OSes. It's weird - it goes through phases
of failing over a period of a few days/weeks for a particular environment, then
nothing, then back again. All I can think of is that it is the particular
server it gets allocated and that's sticky.
This test is time related - it has built-in fixed time intervals and
expected timeouts so long stalls in the test suite trigger the unexpected
failure. I don't think it is that likely to affect a downstream build but it
could. It's only used in jena-geosparql.
My experience is that the effect of a heavily loaded server is different
between Linux and Windows - there seems to be tendency to longer pauses on
Windows - no idea why.
The proper solution is now issue #2330 (replace custom `ExpiringMap`) -
hopefully someone with geosparql knowledge can help.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
