You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are c4.8xlarge sanity tests running at the moment, they should push in about
an hour. They started at 4pm, but then failed due to disk-space running out (some
git repos have got biiiig). They should run to completion now, hopefully completing
around 6:30-ish. However, I'm not watching them, so if they fail nothing will happen.
The biggest problem I've noticed is people printing to stdout, which is not such a
big problem to deal with.
It won't be possible to get g3 sanity tests done in a useful time-frame before 22:00.
The text was updated successfully, but these errors were encountered:
Hi @m8pple, how long was the run time for certify_std? Because we know that our code compiles and runs within 2min but we don't seem to be receiving any logs for certify_std.run.stdout. Will the same amount of time used for the sanity tests be used for the actual submission?
There are c4.8xlarge sanity tests running at the moment, they should push in about
an hour. They started at 4pm, but then failed due to disk-space running out (some
git repos have got biiiig). They should run to completion now, hopefully completing
around 6:30-ish. However, I'm not watching them, so if they fail nothing will happen.
The biggest problem I've noticed is people printing to stdout, which is not such a
big problem to deal with.
It won't be possible to get g3 sanity tests done in a useful time-frame before 22:00.
The text was updated successfully, but these errors were encountered: