Hi Arne,
Sorry to hear that.
That one is known as well as test_cancel_concurrent_3 and one in
geosparql (which is rarer). It seems to be related to the load on the
machine. It may indicate a problem but it is only the conistency
tracking that is complaining. Oddly, I have only ever seen one of the
tests fail at a time, not both.
It's happened to me on my desktop once in the last 6 months that I can
recall and I've been doing a lot of whole-jena builds over the last few
months with the clearfing up for Jena6.
It does happen on Jenkins and github actions. For GH actions, rerunning
almost always then succeeds (uses the same build VM?)
Andy
On 04/02/2026 14:34, Arne Bernhardt wrote:
Still no luck today:
--> Is this the possible race condition below considered critical?
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR] TS_API.test_cancel_concurrent_2 � Runtime
java.lang.RuntimeException: Encountered open iterators.
[INFO]
[ERROR] Tests run: 19631, Failures: 0, Errors: 1, Skipped: 3
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary for Apache Jena 6.0.0:
[INFO]
[INFO] Apache Jena ........................................ SUCCESS [05:25
min]
[INFO] Apache Jena - IRI3986 .............................. SUCCESS [
16.427 s]
[INFO] Apache Jena - Language tags ........................ SUCCESS [
8.496 s]
[INFO] Apache Jena - Base ................................. SUCCESS [
20.614 s]
[INFO] Apache Jena - Core ................................. SUCCESS [02:03
min]
[INFO] Apache Jena - ARQ .................................. FAILURE [07:55
min]
Am Mi., 4. Feb. 2026 um 14:44 Uhr schrieb Andy Seaborne <[email protected]>:
Could we have another PMC vote on the release please?
Andy
