-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
changed to cosmic-version so the api error page will show cosmic #71
Conversation
go build |
1 similar comment
go build |
Hi @miguelaferreira, I not sure, mainly because we had the test run three times now and every time something else failed... 😞 |
Well, when I changed this test the last time it was because the test assumed the VM would stop and automatically be started again. But in fact it did never stop (due to an error with exception on management server log) and the test would pass because it never checked that it actually had stopped. Now it does wait until the VM stops and breaks if timeout is reached. What you could do, while running it in a bubble, is:
However, when random weirdness starts to happen, rebooting the slaves is usually a solution too. |
Rebooting the slaves is exactly what @remibergsma did last weekend, and still it does fail at random tests BTW thanks for you help @miguelaferreira |
go build |
…ead of cloud-stack
00347f2
to
b8812b9
Compare
@ddegoede Rebased with latest master |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All green, merging
changed to cosmic-version so the api error page will show cosmic instead of cloud-stack this way there is way to distinguish between cloudstack and cosmic in using the api