oxidecomputer / oxidecomputer/console
Test flake: ip-pools › no ranges means no utilization bar
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 228
- Forks
- 22
- Avg merge
- 19h 42m
- Merged PRs (30d)
- 32
Description
Weird one. Seems from the "transferring data..." thing that something prevented the page from finishing loading even though visually it has loaded.
https://github.com/oxidecomputer/console/actions/runs/16229622407/job/45829539180
Test timeout of 60000ms exceeded.
Error: page.goto: Test timeout of 60000ms exceeded.
Call log:
- navigating to "http://localhost:4009/system/networking/ip-pools/ip-pool-4", waiting until "load"
330 | await expect(page.getByText('IPv6(IPs)')).toBeHidden()
331 |
> 332 | await page.goto('/system/networking/ip-pools/ip-pool-4')
| ^
333 | await expect(page.getByText('IPv4(IPs)')).toBeVisible()
334 | await expect(page.getByText('IPv6(IPs)')).toBeVisible()
335 |
at /Users/runner/work/console/console/test/e2e/ip-pools.e2e.ts:332:14
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with test/e2e/ip-pools.e2e.ts at line 332 and inspect the linked CI job for the timeout during page.goto('/system/networking/ip-pools/ip-pool-4'). Re-run the ip-pools end-to-end test to determine why loading does not finish. Done means the test completes reliably and the IPv4 and IPv6 assertions pass without the timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100