Skip to content
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

Sanity tests running #51

Open
m8pple opened this issue Dec 15, 2017 · 1 comment
Open

Sanity tests running #51

m8pple opened this issue Dec 15, 2017 · 1 comment

Comments

@m8pple
Copy link
Contributor

m8pple commented Dec 15, 2017

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.

@bngzl
Copy link

bngzl commented Dec 15, 2017

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?

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants