errose28 commented on PR #8881: URL: https://github.com/apache/ozone/pull/8881#issuecomment-3164663911
Good catch @ivandika3 and @adoroszlai. Looks like the order of events was: - CI green on this PR with master - #8604 is merged, which updates master in such a way that compilation for this PR fails but doesn't generate a merge conflict - This PR is merged based on the previous green CI - The first CI run of this PR with the latest master changes happens on master itself and fails I'm not sure if there's a way to prevent these sort of issues entirely, since there's always going to be a gap between when a PR's CI completes and when it is merged, during which any other change could show up in master. I guess if reviewers are aware of related changes in master they can re-trigger the CI before merge. -- 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]
