gemmellr commented on PR #6036: URL: https://github.com/apache/activemq-artemis/pull/6036#issuecomment-3540898236
I never really use batch mode. I want the extra logs, like the colouring, and definitely want to know if its somehow expecting input when I dont expect it should be doing so. There is rarely a point/need to run without a cache, so the initial more verbose logs run really doesnt seem like an issue and either way its little different than doing it locally for the first time. The use of fixed (and often non-latest) ubuntu versions was deliberate on my part. I prefer that doesnt float, and I dont think changing the runner every X years is really any concern in terms of maintenance, we do way more maintenance on the jobs in general and for other specific stuff like the actions/JDK/etc. Yes, the new cache is a bit bigger (difference is a bit larger than I exected though); it wouldnt have been more effective now than it was before if it didnt get bigger. The way it prevents the 'Downloading/ed' logs is that it now contains things the cache did not before, as the 'checks' jobs are doing things they didnt previously [in the then-faster runs that tended to win the race to populate the cache], and now also includes some bits the test jobs need that the old cache did not (since the test jobs only won the race if all the checks jobs failed, but theyd often fail too in many cases deepending on the issue). -- 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] For further information, visit: https://activemq.apache.org/contact
