Skip to content
This repository was archived by the owner on Jan 30, 2025. It is now read-only.
This repository was archived by the owner on Jan 30, 2025. It is now read-only.

Fix flaky tracing test that fails with web_vital span err #1150

@inancgumus

Description

@inancgumus

Brief summary

When the integration tests are ran in CI, the workflow often fails on one of the TestTracing, specifically the web_vital sub test.

When this test fails we can usually rerun the failed workflow and the test will pass the second time round, so it's flakey. It would be good if this wasn't the case so that it gives us confidence in our tests and workflows, as well as making it easier to contribute to for external contributors.

xk6-browser version

fcc7f9e

OS

NA

Chrome version

NA

Docker version and image (if applicable)

NA

Steps to reproduce the problem

Run the test in CI, e.g.: https://github.com/grafana/xk6-browser/actions/runs/8138217177/job/22238484745?pr=1228

Expected behaviour

The integration test passes.

Actual behaviour

It fails with:

--- FAIL: TestTracing (3.71s)
    tracing_test.go:161: 
        	Error Trace:	/home/runner/work/xk6-browser/xk6-browser/tests/tracing_test.go:161
        	Error:      	Received unexpected error:
        	            	"web_vital" span was not found
        	Test:       	TestTracing
### Tasks
- [ ] https://github.com/grafana/xk6-browser/pull/1262
- [ ] https://github.com/grafana/k6/pull/3709

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingcinextMight be eligible for the next planning (not guaranteed!)tests

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions