[GitHub] [maven-surefire] Tibor17 edited a comment on pull request #422: [SUREFIRE-1975] JDK18 - The Security Manager is deprecated and will be removed in a future release
Tibor17 edited a comment on pull request #422: URL: https://github.com/apache/maven-surefire/pull/422#issuecomment-1003637159 @slawekjaranowski One of our colleagues told me that the Github CI reserves 14GB of disk space. Maybe the problem is that we execute 20 parallel builds. We should try to avoid the duplicates (push, pull_request) which makes 1.4GB per each run configuration. I would propose to additionally overriding the Java version with min and max, means 8 and 17 only, if 10 parallel builds still does not help. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-surefire] Tibor17 edited a comment on pull request #422: [SUREFIRE-1975] JDK18 - The Security Manager is deprecated and will be removed in a future release
Tibor17 edited a comment on pull request #422: URL: https://github.com/apache/maven-surefire/pull/422#issuecomment-1003593211 This investigation has helped me. It looks like the GH build runs out of disk space. I made a [ZIP of the largest sub-module](https://github.com/apache/maven-surefire/actions/runs/1643753265) and its target folder occupies 1.2GB and I deleted binary files. So the real consumption of the disk space must be much bigger. The problem is that the ZIP does not contain the logs of the last 40 integration test however they were executed but their files are no more on the disk! Still we are somewhere in the middle of the entire test set. How can we prove my hypothesis other way that the particular build runs out of disk space? It looks like one build crashed but the other did not. -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-surefire] Tibor17 edited a comment on pull request #422: [SUREFIRE-1975] JDK18 - The Security Manager is deprecated and will be removed in a future release
Tibor17 edited a comment on pull request #422: URL: https://github.com/apache/maven-surefire/pull/422#issuecomment-1003593211 This investigation has helped me. It looks like the GH build runs out of disk space. I made a [ZIP of the largest sub-module](https://github.com/apache/maven-surefire/actions/runs/1643753265) and its target folder occupies 1.2GB and I deleted binary files. So the real consumption of the disk space must be much bigger. The problem is that the ZIP does not contain the logs of the last 40 integration test however they were executed but their files are no more on the disk! Still we are somewhere in the middle of the entire test set. How can we prove my hypothesis other way that the particular build runs out of disk space? -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [maven-surefire] Tibor17 edited a comment on pull request #422: [SUREFIRE-1975] JDK18 - The Security Manager is deprecated and will be removed in a future release
Tibor17 edited a comment on pull request #422: URL: https://github.com/apache/maven-surefire/pull/422#issuecomment-1003593211 This investigation has helped me. It looks like the GH build runs out of disk space. I made a ZIP of the largest sub-module and its target folder occupies 1.2GB and I deleted binary files. So the real consumption of the disk space must be much bigger. The problem is that the ZIP does not contain the logs of the last 40 integration test however they were executed but their files are no more on the disk! Still we are somewhere in the middle of the entire test set. How can we prove my hypothesis other way that the particular build runs out of disk space? -- 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: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
