GChuf commented on PR #6036: URL: https://github.com/apache/activemq-artemis/pull/6036#issuecomment-3504744612
My fingers were way too fast, I thought I was merging into my own main branch. I hope that explains the horrendous typos ... I wish I saw your comment earlier. > We would most likely stick to the separate cache action over the more basic 'setup-java built in' one Removing this was also the reason why I removed the cleanup job - if we let github take care of all the cache, it wouldn't make sense to do the cleanup manually ... well, at least if we trust it. I'll take a closer look at what's being cached. > The maven download logging being there is actually desired I'm just beginning to play with this. I would ask - what's the minimum amount of logging that's desired? 100k lines in the log, mostly due to downloading, isn't great ... Actually it doesn't even load in the browser for me. I think removing the progress is a great way to keep the log smaller, while keeping the essential info. The next step, I'm thinking, is to suppress "[INFO] Downloading from ..." while keeping "[INFO] Downloaded from ..." > various modules will run tests that cannot run at the same time, so that seems unlikely to be too reliable. Got there! ... > -T1C I ran nproc to check how many cores there are available, and the answer is 4. So theoretically this should help. But. I tried this with builds as well and it doesn't look like it's making a world of difference, plus ... it's the tests that take longer like you said. -- 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
