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
Revert "[ci] enable coverage on merge job" #14804
Conversation
Changelog[uncommitted] (2023-12-08)Bug Fixes
|
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.
LGTM, but needs a changelog entry about not emitting the warning.
As a follow-up, we should also have an integration test that runs a command like pulumi version
and ensures we're not getting unexpected output to stderr/stdout.
b95bae0
to
fc6317e
Compare
Just added this take a look. |
fc6317e
to
4daf352
Compare
Will merge this after #14804 merges.
…erage (#14806) Fixes #14817 As a follow-up to #14804, we need to re-enable code coverage without releases being built with coverage. #14804 includes a test in the release job to catch `pulumi` being released with coverage data. Also fixes the test to check that the pulumi binary is not built with coverage. Background: Coverage was disabled on merge jobs in order to fix [#14799]. [#14716] removed nightly coverage workflows in favor of collecting coverage on merges [#14727]. The binaries built with coverage were used in the downstream prepare-release job causing a noticable bug [#14799].
Fixes #14799
Reverts #14727
This PR reverts enabling coverage on the merge job.
prepare-release uses the binaries built during tests which were built with coverage.