-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Continuous benchmark stalled #4634
Comments
I don't think it is stalled. Right now it is going through the four variants of vibed, which each timeout after one hour of building. Hopefully we'll see new results in a half hour or so after it gets through the last variant of vibed. From the current run's
|
Perhaps will be useful to try #4543, to lower that 4 hours. |
I'm not sure vibed is a good example of re-using the same dockerfile. Most of the differences happen during the build step; compiling with different configurations. |
The run got past vibed and tfb-status shows new data now, so I'm going to close this issue. I agree that we should fix vibed at some point, but I see that as part of the always-present meta-issue of "we should fix or remove all failing frameworks". |
@nbrady-techempower @michaelhixson |
https://tfb-status.techempower.com/
The text was updated successfully, but these errors were encountered: