Team, For those who have been watching the builds on Github Actions they have become substantially less stable. Initially it was just Java 11 builds that became problematic and that happened as soon as the latest azul jdk 11 became the default. David H fixed the tests using the now different API (different exceptions thrown). Then we started seeing other tests failing due to timeouts. These issues and the brittleness are starting to remind me a lot of what we faced with Travis CI as that infrastructure clearly struggled. I dont know what changed in Github CI recently but...it isn't the same.
Now, all the said it is still our problem to figure out. I'll relax the timing of the tests again as during all this I tried to utilize more of the core(s) available. That might well add to the timing issues. But we must also be far more careful on the reliability/repeatability/assumptions of these tests. They do an awful lot of socket creation, timing checks, etc.. that are probably better as integration tests. We don't run integration tests nearly as often though either. We also need to really split out the many nars from the core framework. Build times are pretty brutal and the convenience build is constantly at the limit that ASF will allow. So we have some strategery to sort through soon. Thanks
