elek commented on pull request #911: URL: https://github.com/apache/hadoop-ozone/pull/911#issuecomment-637541097
Thanks the proposal @adoroszlai. I have seen acceptance test timeouts in the previous builds (which is not on the master). I think it should be checked before the merge (if visible with the latest snapshot). It's the same effort to check here or the master, but on master makes the merge of PRs harder. > Further proposals: And thank you for the proposals: > Archive failures of pr-check, too (currently only post-commit on master is archived), to get info on significantly more CI runs, ie. more data points. We can do it. It requires more space and it will include a lot of noise (failures which are real failures). We need some smart filtering (eg. check only the failures which are passed later with a different build but no difference between the two commits). > Create Ratis snapshot release more frequently (automate it?). We can check the purge policy on snapshot.apache.org. If snapshots are kept until the next release we can do a daily snapshot build and use `mvn versions:lock-snapshots` + `versions:unlock-snapshots` commands (it replaces a SNAPSHOT version with an exact timestamped version) > Test Ozone with each "significant" snapshot (eg. one that is not a test-only or build infrastructure change) on a dedicated branch. Also archive these runs. +1. We can create a daily build with full Ozone + latest Ratis. Would help a lot IMHO. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
