-
Notifications
You must be signed in to change notification settings - Fork 59
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
kola tests fail in GCP environment when running in pipeline #487
Comments
OK after a few changes I made (coreos/fedora-coreos-pipeline#238, coreos/fedora-coreos-pipeline#239) I've had a few successful runs of the non-upgrade tests. Now the upgrade tests are failing: now that I got upgrade tests working I'm seeing this failure in the upgrade test:
Do we maybe need to bump the timeout? |
I think this was as simple as changing it so that the --platform option had an Only remaining issue is to debug the upgrade test failure because of the timeout. |
I don't think it's a timeout issue, but something else wrong with the test itself (possibly a version/checksum mismatch in the synthetic update graph). Zincati is scraping the update server on
|
Sorry, I missed this ticket previously in my notifications.
(There should've been an obvious error message to help with this, but the error-handling was buggy.) Working on that now. |
Upgrade tests use the image of the previous release, not the candidate release we're testing itself. The `--find-parent-image` swithc will automatically find the starting image to use. Closes: coreos/fedora-coreos-tracker#487
Upgrade tests use the image of the previous release, not the candidate release we're testing itself. The `--find-parent-image` switch will automatically find the starting image to use. Closes: coreos/fedora-coreos-tracker#487
Upgrade tests use the image of the previous release, not the candidate release we're testing itself. The `--find-parent-image` switch will automatically find the starting image to use. Closes: coreos/fedora-coreos-tracker#487
I recently added a kola GCP pipeline so we can CI our GCP images we're now uploading to GCP. For some reason the images are failing in CI but passing when I run them from a local box. The only real difference I know of is that one is running in the pipeline and one is running from my desktop.
Below is the output when I run it locally (all PASS):
I wonder if the
Error saving console
messages are what is marking it as failed?The text was updated successfully, but these errors were encountered: