Baunsgaard commented on PR #1820: URL: https://github.com/apache/systemds/pull/1820#issuecomment-1567276199
> On another note, I've only set up the deletion workflow to run if the triggering javaTests were a success. This is because some of the tests in require retries, and if you were to retry the tests after deleting the artifacts, the code-coverage report generated would be missing all of the prior successful tests. I'd like to suggest automating the retries of the common test failures in the java workflow. However, this comes with its own issues since tests real negative test results will also then be retried. (Unrelated to the PR) Ideally we need to change our testing methodology for the failing tests, currently the ones that produce errors most commonly are because we do not do callback based testing, rather we wait a specified time frame, and that makes it sometimes fail when running in parallel with other tests. -- 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: dev-unsubscr...@systemds.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
