-
Notifications
You must be signed in to change notification settings - Fork 15
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
Bump fork with more cpu #295
Conversation
/kick git doesn't like the envoy-fork commit hash https://storage.googleapis.com/solo-public-build-logs/logs.html?buildid=b1c5a616-bdb8-4f7e-918b-f52f22cff5f7 |
/kick some more |
Build failure here: https://storage.googleapis.com/solo-public-build-logs/logs.html?buildid=56070b95-1b86-4738-a9cc-53df21bbd9f0
so it looks like the job was killed due to this test timing out after compiling for 900s. also note that envoy built successfully, but that the job failed due to this test failing to build. I'm going to look into where it's set and whether it's possible to extend that 900s timeout Update: https://bazel.build/reference/test-encyclopedia#:~:text=Time%20Limit%20(sec.)&text=A%20%22large%22%20test%20with%20no,will%20be%20allotted%2060%20seconds. |
/kick now that CI has passed on another PR with the same envoy-fork dependency |
No description provided.