-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Unbreak the E2E tests #370
Conversation
Major changes: * Also update E2E test return value on failures * Default build/unit test runners
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.
/lgtm
/approve
/retest |
Otherwise E2E tests won't pass.
/retest |
6 similar comments
/retest |
/retest |
/retest |
/retest |
/retest |
/retest |
Nevermind the retests, this is not flakiness:
@bobcatfish do you know what's wrong here? I don't think that this is a simple case of increasing the timeout (and it won't fix the yaml tests anyway) |
As discussed on Slack, the errors in E2E seem to be related to the Prow environment. I'm gonna disable the broken tests to unblock the pipeline and file issues for them. |
Tests passed, let me file issues and update the PR description... /hold |
/hold cancel |
/lgtm 🎉 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adrcunha, ImJasonH The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Remove ko:// prefix from release.yaml
Fixes #361.
Fixes #368.
Update test-infra
Major changes:
Fix botched rename of PipelineTrigger field
This is a copy of #369.
Disable broken tests
There are 2 tests failing consistently, and it seems that they're failing only on Prow. Disabling them here to unblock the E2E tests, filed #375 and #376 to track the fixes.