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
Testground reports failure for instances when they appear to succeed #1382
Comments
I've bumped into the same issue during a run of my composition (it is successful in the logic itself, but the outcome says failure as mentioned in the bug description) |
Thanks for raising this, I couldn't reproduce this, but that's an issue I've seen a couple of time:
I use the following command: docker stop $(docker container ls -q --filter name='testground*') # restart containers
# then restart the `testground daemon` |
I was not doing this! After using
I've still seen this very sporadically when running pingpong test locally (even after restarting the testground containers) I noticed that there is always a warning from each instance in the logs when it does report failures:
I tried to reproduce the pingpong failure on a debian cloud vm and was unable to. I suspect that this is some kind of timing/ performance issue caused by the fact that I'm using a M1 mac? Let me know if there's any more info I can provide to help! |
Version information:
Macbook pro (M1)
Description:
Testground reports that instances have failed
run finished with outcome = failure (single:0/2)
even though it looks like they have succeeded:I've noticed this when running my own tests but I'm also able to reproduce it by running the
ping-pong
sample test case. It doesn't happen all the time but does happen quite frequently.Testground collect output:
cb67fo7semvi2emk8gog.tgz
Full console output:
The text was updated successfully, but these errors were encountered: