-
Notifications
You must be signed in to change notification settings - Fork 630
Run upgrade tests in separate Prow check #3173
Copy link
Copy link
Closed
knative/test-infra
#2152Labels
area/test-and-releaseTest infrastructure, tests or releaseTest infrastructure, tests or releasekind/feature-requestpriority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Metadata
Metadata
Assignees
Labels
area/test-and-releaseTest infrastructure, tests or releaseTest infrastructure, tests or releasekind/feature-requestpriority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Problem
Now, that PR #2388 is merged the upgrade tests are executed in the same run as regular e2e tests, sequential. It isn't perfect as the log is double the size and it's harder to follow.
Example of such run can be seen here: https://prow.knative.dev/view/gcs/knative-prow/pr-logs/pull/knative_eventing/2388/pull-knative-eventing-integration-tests/1263045362487136256
Persona:
Which persona is this feature for? Contributors
Exit Criteria
There are separate Prow runs defined, one for regular e2e tests, and one for upgrade tests. Regular e2e test run should not include the upgrade tests.
Time Estimate (optional):
1d
Additional context (optional)
It was discussed before #2388 (comment)