New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CMake] All post-commit buildbots should build with --no-fatal-warnings #5710
[CMake] All post-commit buildbots should build with --no-fatal-warnings #5710
Conversation
I'm sure there's a better way to do this, but this should allow me to land #5708 without triggering an apocalypse on any post-release bots. |
0d64f55
to
2065253
Compare
EWS run on previous version of this PR (hash 2065253)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These changes will need to be landed either squashed or in two separate PRs, we'll also need to coordinate a build.webkit.org restart.
Sorry, that was just an error. It was supposed to be only one commit. Fixed. |
How much coordination is required here? Any chance it's just a big blue button that you press and then everything restarts smoothly? BTW it looks like the build.webkit.org unit tests are failing due to what appears to be a preexisting issue:
|
Tested locally and this failure doesn't appear in the current main, but appears in the pull request. The cause is in https://github.com/WebKit/WebKit/blob/main/Tools/CISupport/build-webkit-org/factories.py#L180
So in practice it was incidentally passing before because |
It's not quite that easy, usually it's best to have the restarted and the lander be the same person. If this is ready to go tomorrow morning and @mcatanzaro you let me know you're ready to land it, I can land and do the restart first thing tomorrow morning when I get on.
Looks like @lauromoura broke down what happened here. |
It's not ready currently. I will try to implement Lauro's suggestion and then we'll see if that works. Will let you know.
After updating this pull request, I'll no longer be touching additionalArguments, so want to report a bug for this? |
I can submit it, alongside the fix. |
2065253
to
4abb3ad
Compare
EWS run on previous version of this PR (hash 4abb3ad)
|
@lauromoura does this look better? |
(I need to update the test expectations... incoming.) |
4abb3ad
to
f6c7213
Compare
EWS run on current version of this PR (hash f6c7213)
|
I think this is ready from my side. Let's just wait and see if Lauro is happy. Thanks @JonWBedard ! |
Looks better now. Thanks for the update. |
OK, this is ready to land. |
https://bugs.webkit.org/show_bug.cgi?id=246760 Reviewed by Jonathan Bedard. We need to enable fatal warnings on EWS to prevent developers from introducing new warnings. But we do not want fatal warnings on post-commit bots, since that may result in lost test results, which would be a very harsh price to pay for an unused variable or whatnot. Note this is not needed for the JSC bots since those do not use ENABLE_DEVELOPER_MODE. * Tools/CISupport/build-webkit-org/steps.py: (CompileWebKit): * Tools/CISupport/build-webkit-org/steps_unittest.py: (TestCompileWebKit.test_success): (TestCompileWebKit.test_success_gtk): (TestCompileWebKit.test_success_wpe): (TestCompileWebKit.test_failure): Canonical link: https://commits.webkit.org/255954@main
f6c7213
to
e868bfe
Compare
Committed 255954@main (e868bfe): https://commits.webkit.org/255954@main Reviewed commits have been landed. Closing PR #5710 and removing active labels. |
e868bfe
f6c7213
π§ͺ api-mac