ivandika3 commented on PR #8881: URL: https://github.com/apache/ozone/pull/8881#issuecomment-3166275348
Thanks @adoroszlai for helping to resolve the issue promptly and @errose28 for tracing the issue. > 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. Yes, IMO it's an acceptable tradeoff between occasional compile issue and needing to merge to latest master (which will slow down merge). I think it's an acceptable tradeoff if we can be rectify the issue quickly (e.g. checking master branch frequently + checking for notification for CI failures on master when the PR is meregd). @adoroszlai By the way, can I check whether any committer / PMC has the privilege to push directly to master to fix compile issue or is there any SOP that we need to follow? -- 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]
