-
Notifications
You must be signed in to change notification settings - Fork 43
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
TestConfigureSimpleValues test is flaky #2530
Comments
The test is flaky, so it should be skipped until we have time to dig into it. addresses #2530
Skipped the test, no longer a p1 but we should fix it |
I'm unable to get the flake on my computer, even with `--count 1000`. The test wasn't previously running in parallel, so it shouldn't be an interaction with other tests. I've added better asserts so we can see which result is unexpectedly nil. I think our best chance at fixing the test is to turn the test back on and then re-engage if/when it flakes again. Fixes #2530
I'm unable to get the flake on my computer, even with `--count 1000`. The test wasn't previously running in parallel, so it shouldn't be an interaction with other tests. I've added better asserts so we can see which result is unexpectedly nil. I think our best chance at fixing the test is to turn the test back on and then re-engage if/when it flakes again. Part of investigating #2530
As part of diagnosing #2530, this commit tightens `crosstests.Configure`. My assumption is that we will occasionally see failures in the bridged provider here.
As part of diagnosing #2530, this commit tightens `crosstests.Configure`. My assumption is that we will occasionally see failures in the bridged provider here.
As part of diagnosing #2530, this commit tightens `crosstests.Configure`. My assumption is that we will occasionally see failures in the bridged provider here.
As part of diagnosing #2530, this commit fixes some assertions in `crosstests.Configure`. My assumption is that we will occasionally see failures in the bridged provider here.
As part of diagnosing #2530, this commit tightens `crosstests.Configure`. My assumption is that we will occasionally see failures in the bridged provider here.
The occasions I saw were hitting on ubuntu default, but that might just be chance |
This PR tests the theory that provider creation or configuration may be skipped if they are depended on by no resources. Part of #2530
This PR tests the theory that provider creation or configuration may be skipped if they are depended on by no resources. Part of #2530
This PR tests the theory that provider creation or configuration may be skipped if they are depended on by no resources. Part of #2530
The error trace is
This is the PF configure call. The rest of the issue has been about the SDKv2 Configure call. |
Another TestConfigure flake: https://github.com/pulumi/pulumi-terraform-bridge/actions/runs/11972273455/job/33378845348?pr=2656 |
Is it the error that pulumi/pulumi#17825 is supposed to fix? |
No, doesn't look like it
|
This will hopefully help address #2530.
#2661 implements the same strategy as helped reduce |
This will hopefully help address #2530.
What happened?
The test seems to panic intermittently: https://github.com/pulumi/pulumi-terraform-bridge/actions/runs/11579563225/attempts/1?pr=2497
Example
.
Output of
pulumi about
.
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: