afs commented on issue #3008: URL: https://github.com/apache/jena/issues/3008#issuecomment-2700477083
The codebase does not have my experiments improving the situation (they are on a branch [`tests-experiment`](https://github.com/afs/jena/tree/tests-experiment) on my account). `TestModelStore` is like `TestGSP`, `TestDSP`. I haven't had that failing but it uses `EnvTest` and has one server per test suite. These have a (not a ) fix - simply leave the server running - not stop it in `@afterClass`. > Is it reproducible in other Github runners than Ubuntu I'll check - from memory, the Mac and Windows can fail but much less likely. (Update: 1 in 10 MSWindows failure but the failure is in the UI test suite ) ASF Jenkins also has been known to be failures but they are far less infrequent and I don't have record of the causes. They may be unrelated. Jenkins also has a completely different failure mode - the build gets to "SUCCESS" then the artifact collection fails after maven has run. https://ci-builds.apache.org/job/Jena/ > or outside of github actions? If it does, it is very rare. > After some reading/searching, I have theory: Could the domain localhost sometimes be served on ipv6, and sometimes on ipv4 ,and not resolve properly on ipv6? [cypress-io/github-action#802](https://github.com/cypress-io/github-action/issues/802) > Could try to update the tests to use 127.0.0.1 and see if we can then get fuseki to listen on both (if it isn't)? That cypress error could explain the UI build-test failures we get from the browser matrix. Until now they have been intermittent but updates in https://github.com/apache/jena/pull/3037 make the Firefox run reliably fail. (But I think our tests run on node 21.) Re: TestModelStore `Tests run: 19, Failures: 0, Errors: 1` So some tests are running. "EOF reached while reading" suggests the TCP connection has been established but the server went away before the response. I'll try the localhost/127.0.0.1 thing but it looks to be different. -- 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]
