-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
projects-test intermittently fails with "TimeoutError: Navigation Timeout Exceeded: 30000ms exceeded" #21191
Comments
@TristanWatanabe If you're feeling better, could you help look into this? I think a good first step would be adding a log listing the files in the directory being served (and maybe their contents), and/or seeing if |
Actually I think it's a race condition--search this build log for "Starting server on port" and you'll see that there are two different tests trying to run on port 8000. This is weird because I thought portfinder (this line) should have ensured the ports didn't collide? So we can either look into why |
Reopening as this issue occurred once again after initial fix. |
run into another issue with
|
Because this issue has not had activity for over 180 days, we're automatically closing it for house-keeping purposes. Still require assistance? Please, create a new issue with up-to date details. |
Because this issue has not had activity for over 180 days, we're automatically closing it for house-keeping purposes. Still require assistance? Please, create a new issue with up-to date details. |
Northstar
projects-test
rollup
test intermittently fails with this timeout error, on the last step where it's trying to load the built page. (I may have also seen other similar tests failing with the same error.)example build with this failure
For the rollup test it's this part of the test:
fluentui/packages/fluentui/projects-test/src/rollup.ts
Lines 55 to 56 in 18549da
Specifically this line:
fluentui/scripts/projects-test/performBrowserTest.ts
Line 63 in 18549da
It's not clear to me why this is happening or exactly how to debug. Ideas:
The text was updated successfully, but these errors were encountered: