orpiske commented on PR #12739:
URL: https://github.com/apache/camel/pull/12739#issuecomment-1889687215
> Many tests fail due to threading issues that are related to setting
`camel.surefire.reuseForks` to `true`. I'm not proposing to disable forks
permanently, just until the root causes of the test failures are found and
fixed. Yes, the full build with tests runs more slowly and takes about 3.5
hours to complete on my MacBook Pro. But, because the tests are broken, nobody
runs the full build with unit tests anyway. Can you recommend an alternative
approach? Because I don't see a better one.
Our tests are not perfect. We know that we (I, in particular) have been
fixing them for quite a while. That said, to say that they are "broken" is a
**very big stretch**.
- The tests run on the ASF CI, in multiple platforms (x86, ppc64le, s390x)
- The tests run on GitHub Actions
- The tests are regularly run manually by me (on arm, x86, ppc64le, s390x)
and other core contributors.
And, although we do have occasional failures, the incidence is *very* small.
So, what can be done to improve the reliability of the tests? Look for flaky
tests using the [dashboard from The ASF
Develocity](https://ge.apache.org/scans?search.rootProjectNames=Camel&search.tasks=verify&search.timeZoneId=Europe%2FParis#)
environment.
When finding a problem on a test, focus on the source of the problem: if
there is a threading problem, try to reproduce it, provide traces and dumps for
the community so we can fix or assist with the fix/review (it's very likely the
fix will require internal knowledge of the core code).
--
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: commits-unsubscr...@camel.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
