Github user ajs6f commented on the pull request:
https://github.com/apache/jena/commit/8601cd3028c0e57dbc805efc5d54d7b9ee272c3f#commitcomment-20400171
In
jena-arq/src/test/java/org/apache/jena/sparql/core/pergraph/MultithreadingTest.java:
In
jena-arq/src/test/java/org/apache/jena/sparql/core/pergraph/MultithreadingTest.java
on line 45:
What's needed is several points of sync or at least ordering, because one
txn must be completely overlapped by the other, to prove that it successfully
began and committed while another one was going on, and then that the first one
still managed to finish. I will think about it some more and make sure I have a
very clear schema in mind and have worked out the various permutations (which
will end up as other tests).
That blog post is quite a laugh. I know I've fallen for some of those
before. I'll admit, the polling isn't the best thing, although I don't mind it
so much hidden behind a good facade as it is. I am going to finish writing the
tests in the current style because I can write quickly in that way, and then I
will translate them into something more durable.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
