Commit 20b8404
authored
fix: wait for CloudFormation stack deletion in pipeline bootstrap tearDown (#8744)
The test_interactive_pipeline_user_only_created_once integration test
was flaky because tearDown called delete_stack without waiting for
completion. On reruns or subsequent test executions, the stack could
still exist (DELETE_IN_PROGRESS), causing CreateChangeSet to fail with
'Stack already exists and cannot be created again with the changeSet
InitialCreation'.
Add a waiter after delete_stack calls in tearDown that polls every 10s
up to a 180s timeout, ensuring stacks are fully deleted before the next
test begins. Timeouts are logged as warnings without failing teardown.1 parent 1636f3e commit 20b8404
1 file changed
Lines changed: 19 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
65 | 65 | | |
66 | 66 | | |
67 | 67 | | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
68 | 71 | | |
69 | 72 | | |
70 | 73 | | |
71 | 74 | | |
| 75 | + | |
72 | 76 | | |
73 | 77 | | |
74 | 78 | | |
| 79 | + | |
| 80 | + | |
| 81 | + | |
| 82 | + | |
| 83 | + | |
| 84 | + | |
| 85 | + | |
| 86 | + | |
| 87 | + | |
| 88 | + | |
| 89 | + | |
| 90 | + | |
| 91 | + | |
| 92 | + | |
| 93 | + | |
75 | 94 | | |
76 | 95 | | |
77 | 96 | | |
| |||
0 commit comments