-
Notifications
You must be signed in to change notification settings - Fork 7
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
{"error":"Navigation timeout of 30000 ms exceeded"} #292
Comments
@deniak @marcoscaceres this seems to be happening frequently. Is there anything that can be done to have a way to restart the server if jobs keep on failing? |
I guess we need to figure out what the root cause is that is causing it to stall on the server. There is a regression somewhere or some dependency is locking things up. @deniak, any output on the server for you? |
Looking at the logs below, it seems the second spec is missing the respecConfig.
|
cc'ing @sidvishnoi., who can look at respec2html to see if anything in the generator might need more robust exit strategy to kill the process. |
@jnurthen, sent a PR to fix the reference errors: |
I looked a bit and it seems the process gets stuck on the document generation and the browser never gets closed. This can be reproduced with the following command:
|
Thanks for a reduced test case @deniak. I'll investigate this in a while. |
Released ReSpec v25.6.1 with a fix for stalling on unresolved promise. |
Legend! Hopefully it makes the W3C server happy. |
I just redeployed and I confirm the processes are correctly killed. Thanks @sidvishnoi ! |
Thanks all. |
again
Example URLs that fail
https://labs.w3.org/spec-generator/?type=respec&url=https://raw.githack.com/w3c/aria/removeDefer/index.html
https://labs.w3.org/spec-generator/?type=respec&url=https://rawcdn.githack.com/w3c/aria-practices/c74e8e46b38c7df5f4c1079f8d3dedf5373af1ab/aria-practices.html&isPreview=true
The text was updated successfully, but these errors were encountered: