-
Notifications
You must be signed in to change notification settings - Fork 55
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
serial_test_import_glb
rust test is flaky
#2396
Comments
it might just be we've changed the format and need to update the file idk |
It looks like it has something to do with the websocket timing out:
|
It looks like lots of other tests are failing with the same cause:
|
If the websocket is timing out, it's unsurprising that it would do so when importing geometry because that can be a slow operation. |
you arent running them serially (the glb one is the only flaky one the others fail w too many connections), so yes the websocket is timing out for that one but it didn't before and thats the weird thing... like is it a symptom of something else it has 60 seconds to import the file, that seems excessive |
also get this quite often
that means the server is closing it not us... i just think something is suspicious |
With
|
another fun fact, you can run against a local engine w |
I'm not able to reproduce this locally anymore. Is this still a problem? |
these seem less flakey now |
when the rust tests fail its usually becuase of this test, which is weird since it passes sometimes too
not the biggest priority but want to rule out its a symptom of something bigger, cc @alteous
The text was updated successfully, but these errors were encountered: