GoogleChrome / GoogleChrome/lighthouse

`NO_NAVSTART` in api tests and smoke tests

Open
#15,382 2 comments 6 reactions 0 assignees View on GitHub
bug P2 test backlog
Dominant language
JavaScript
Stars
30.8k
Forks
9.8k
Avg merge
1d 14h
Merged PRs (30d)
20

Description

Retries added to unblock CI: https://github.com/GoogleChrome/lighthouse/pull/15378

-----
Example failure: https://github.com/GoogleChrome/lighthouse/actions/runs/5871078774/job/15919549134?pr=15378

Example failure trace: https://trace.cafe/t/K4uwDnVkKA

- Entire main thread track is missing for some reason.
- Navigation tests fail with `NO_NAVSTART` on a bunch of audits
- Timespan tests fail because the INP event is missing, making the INP audits N/A

`NO_NAVSTART` also appears on smoke tests: https://github.com/GoogleChrome/lighthouse/actions/runs/5894225760/job/15987413301?pr=15353

Contributor guide

Open the contributing guide

Research direction

Start with the linked CI runs and trace, then reproduce the navigation, timespan, and smoke-test failures. Investigate why the main-thread track and navigation start are missing, and verify that the affected audits receive the expected navigation and INP data without retries.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.