Thomas Gummerer 0eededec61 generate unique stack names for tests (#15230) ... Tests can run in parallel, e.g. on different PRs/same tests on different platforms, and if a single test gets killed by the CI runner without cleaning up all future tests will fail if the stack name is not unique. Make sure the stack name is unique to avoid these failures. I a CI failure that's `error: stack 'organization/project/testing' already exists`. This PR should hopefully fix it. ## Checklist - [x] I have run `make tidy` to update any new dependencies - [x] I have run `make lint` to verify my code passes the lint check - [x] I have formatted my code using `gofumpt` <!--- Please provide details if the checkbox below is to be left unchecked. --> - [ ] I have added tests that prove my fix is effective or that my feature works <!--- User-facing changes require a CHANGELOG entry. --> - [ ] I have run `make changelog` and committed the `changelog/pending/<file>` documenting my change <!-- If the change(s) in this PR is a modification of an existing call to the Pulumi Cloud, then the service should honor older versions of the CLI where this change would not exist. You must then bump the API version in /pkg/backend/httpstate/client/api.go, as well as add it to the service. --> - [ ] Yes, there are changes in this PR that warrants bumping the Pulumi Cloud API version <!-- @Pulumi employees: If yes, you must submit corresponding changes in the service repo. -->		2024-01-24 11:41:04 +00:00
..
project	Add azure login test (#15161)	2024-01-23 09:41:20 +00:00
backend_azure_test.go	generate unique stack names for tests (#15230)	2024-01-24 11:41:04 +00:00