influxdata / influxdata/influxdb
Flaky Test: `TestLauncher_Pkger/managing_pkg_lifecycle_with_stacks` on `test-windows` job
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
Saw this fail on a merge to master, where they had previously passed on a PR branch:

This was only for the `test-windows` job, so possibly specific to windows.
Link to failed circle job: https://app.circleci.com/pipelines/github/influxdata/influxdb/25056/workflows/4a3e5b6b-b018-4e9f-8f23-82b8b5541a05/jobs/222130/steps
Relevant log lines are below:
```
=== Failed
=== FAIL: cmd/influxd/launcher TestLauncher_Pkger/managing_pkg_lifecycle_with_stacks/updating_a_stack/bootstrapped_updates_successfully (0.00s)
pkger_test.go:586:
Error Trace: pkger_test.go:568
pkger_test.go:586
Error: Should be true
Test: TestLauncher_Pkger/managing_pkg_lifecycle_with_stacks/updating_a_stack/bootstrapped_updates_successfully
pkger_test.go:590:
Error Trace: pkger_test.go:568
pkger_test.go:590
Error: Should be true
Test: TestLauncher_Pkger/managing_pkg_lifecycle_with_stacks/updating_a_stack/bootstrapped_updates_successfully
--- FAIL: TestLauncher_Pkger/managing_pkg_lifecycle_with_stacks/updating_a_stack/bootstrapped_updates_successfully (0.00s)
=== FAIL: cmd/influxd/launcher TestLauncher_Pkger/managing_pkg_lifecycle_with_stacks/updating_a_stack (0.01s)
--- FAIL: TestLauncher_Pkger/managing_pkg_lifecycle_with_stacks/updating_a_stack (0.01s)
=== FAIL: cmd/influxd/launcher TestLauncher_Pkger/managing_pkg_lifecycle_with_stacks (0.84s)
--- FAIL: TestLauncher_Pkger/managing_pkg_lifecycle_with_stacks (0.84s)
=== FAIL: cmd/influxd/launcher TestLauncher_Pkger (2.04s)
logger.go:130: 2021-10-20T15:23:12.995Z ERROR api error encountered {"test_name": "TestLauncher_Pkger", "handler": "bucket", "error": "bucket not found"}
logger.go:130: 2021-10-20T15:23:12.999Z ERROR api error encountered {"test_name": "TestLauncher_Pkger", "handler": "dashboards", "error": "dashboard not found"}
logger.go:130: 2021-10-20T15:23:13.000Z ERROR api error encountered {"test_name": "TestLauncher_Pkger", "error": "label not found"}
logger.go:130: 2021-10-20T15:23:13.027Z ERROR api error encountered {"test_name": "TestLauncher_Pkger", "handler": "bucket", "error": "bucket not found"}
logger.go:130: 2021-10-20T15:23:13.028Z ERROR api error encountered {"test_name": "TestLauncher_Pkger", "handler": "dashboards", "error": "dashboard not found"}
logger.go:130: 2021-10-20T15:23:13.029Z ERROR api error encountered {"test_name": "TestLauncher_Pkger", "error": "label not found"}
logger.go:130: 2021-10-20T15:23:13.041Z ERROR failed to read stack {"test_name": "TestLauncher_Pkger", "service": "pkger", "error": "stack not found for key \"0000000000002328\"", "id": "0000000000002328", "took": "0s"}
logger.go:130: 2021-10-20T15:23:13.041Z ERROR api error encountered {"test_name": "TestLauncher_Pkger", "handler": "stacks", "error": "stack not found for key \"0000000000002328\""}
logger.go:130: 2021-10-20T15:23:13.175Z ERROR failed to apply template {"test_name": "TestLauncher_Pkger", "service": "pkger", "orgID": "44b9e3d149ae8caf", "userID": "0853927f96b5a000", "error": "resource_type=\"removed_label_mapping\" err=\"failed to apply resource\"\n\tmetadata_name=\"notificationRules:0853927fd26e1000:0853927fd035a000\" err_msg=\"reached kill count\"", "took": "71.8664ms"}
logger.go:130: 2021-10-20T15:23:13.395Z ERROR api error encountered {"test_name": "TestLauncher_Pkger", "handler": "bucket", "error": "bucket \"z-roll-me-back\" not found"}
logger.go:130: 2021-10-20T15:23:13.396Z ERROR api error encountered {"test_name": "TestLauncher_Pkger", "handler": "bucket", "error": "bucket \"z-rolls-back-too\" not found"}
logger.go:130: 2021-10-20T15:23:13.460Z ERROR failed to apply template {"test_name": "TestLauncher_Pkger", "service": "pkger", "orgID": "44b9e3d149ae8caf", "userID": "0853927f96b5a000", "error": "resource_type=\"\" err=\"failed to apply resource\"\n\tmetadata_name=\"z-rules-back-3\" err_msg=\"failed to create notificationRules[\\\"z-rules-back-3\\\"]: reached kill count\"", "took": "66.2234ms"}
logger.go:130: 2021-10-20T15:23:13.470Z ERROR api error encountered {"test_name": "TestLauncher_Pkger", "handler": "bucket", "error": "bucket \"z-roll-me-back\" not found"}
logger.go:130: 2021-10-20T15:23:13.471Z ERROR api error encountered {"test_name": "TestLauncher_Pkger", "handler": "bucket", "error": "bucket \"z-rolls-back-too\" not found"}
logger.go:130: 2021-10-20T15:23:13.535Z ERROR api error encountered {"test_name": "TestLauncher_Pkger", "handler": "bucket", "error": "bucket \"display name\" not found"}
logger.go:130: 2021-10-20T15:23:13.804Z ERROR api error encountered {"test_name": "TestLauncher_Pkger", "handler": "bucket", "error": "bucket \"rucketeer\" not found"}
logger.go:130: 2021-10-20T15:23:13.845Z ERROR api error encountered {"test_name": "TestLauncher_Pkger", "handler": "bucket", "error": "404 page not found"}
logger.go:130: 2021-10-20T15:23:13.860Z ERROR api error encountered {"test_name": "TestLauncher_Pkger", "handler": "bucket", "error": "404 page not found"}
logger.go:130: 2021-10-20T15:23:13.863Z ERROR api error encountered {"test_name": "TestLauncher_Pkger", "handler": "dashboards", "error": "404 page not found"}
logger.go:130: 2021-10-20T15:23:14.171Z ERROR api error encountered {"test_name": "TestLauncher_Pkger", "handler": "bucket", "error": "bucket \"rucket-1\" not found"}
logger.go:130: 2021-10-20T15:23:14.263Z ERROR failed to apply template {"test_name": "TestLauncher_Pkger", "service": "pkger", "orgID": "44b9e3d149ae8caf", "userID": "0853927f96b5a000", "error": "kind=Telegraf field=root[0].metadata.name reason=\"name \\\"with_underscore-is-bad\\\" is invalid; a DNS-1123 label must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character (e.g. 'my-name', or '123-abc', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?')\"", "took": "0s"}
```
Contributor guide
Research direction
Start with cmd/influxd/launcher/pkger_test.go around lines 568-590 and the TestLauncher_Pkger/managing_pkg_lifecycle_with_stacks/updating_a_stack test. Reproduce the failure on the test-windows job using the linked CircleCI run as context. Done means the lifecycle test no longer flakes on Windows and the relevant assertions pass reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100