jeantil commented on PR #2845: URL: https://github.com/apache/james-project/pull/2845#issuecomment-3493151219
I had a look at the [build scan](https://develocity.apache.org/s/zox5yhmf7p37w/performance/execution) of the jobs the one which failed executed only 10 cacheable goals and only tests <img width="2101" height="780" alt="2025-11-05_09-02" src="https://github.com/user-attachments/assets/6ce7048c-5bc8-469d-830c-1ecbd0f5be62"; /> the one that succeeded executed 97 cacheable goals including 3 test compilations (only 2 are visible on the screenshot but there is a 3rd one <img width="2103" height="1178" alt="2025-11-05_09-03" src="https://github.com/user-attachments/assets/08dc3e8a-cb2e-436b-9303-52c878425794"; /> In between commit 35a3bc44632d09d6cb6cf6dc68f65d0e04101ba3 was added to master which affects a project upstream of JMAP triggering a cache invalidation for the affected project because of changed dependencies. So as I said disabling/enabling the build cache did not solve the issue. Now I'll try to dig into the various builds on your initial branch to try to understand how we got to the corrupted state. -- 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]
