ProgramTest upgrade tests can fail right after recording #76
Labels
impact/reliability
Something that feels unreliable or flaky
kind/engineering
Work that is not visible to an external user
What happened?
Looks like under some conditions, the upgrade tests fail right after being recorded, when no changes have happened.
In this example, the diff has:
For the resource under test, the
staging
property is not available in the baseline version and has a default in the newer version. We probably compare a diff using the old version to a diff using the new version?Example
https://github.com/pulumi/pulumi-aws/actions/runs/8265739539/job/22614819405?pr=3610
Output of
pulumi about
tested on pulumi/pulumi-aws@17db4d7
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: