-
Notifications
You must be signed in to change notification settings - Fork 112
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
IOSETTINGS test failure #1342
Comments
@acomodi Does it happen every time? What's the SHA of the failing commit? |
@mkurc-ant I wasn't able to reproduce this locally, saw this only in CI runs, didn't see this in a while though. |
@acomodi / @mkurc-ant Can we close this? |
I haven't encountered that error neither locally not in CI. Maybe it was due to some previous Kokoro configuration running too many parallel builds? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are multiple CI runs that failed due to the
iosettings
tests. This happens on the VtR+SymbiFlow build and the failure is probably due to the router exhausting memory as it gets in an unroutable situation, having the target aborted as a result.The text was updated successfully, but these errors were encountered: