Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[E2E Scenario Test] Reduce time taken for upgrade tests #724

Open
mukundansundar opened this issue May 21, 2021 · 1 comment
Open

[E2E Scenario Test] Reduce time taken for upgrade tests #724

mukundansundar opened this issue May 21, 2021 · 1 comment
Labels
area/test/e2e P2 triaged/resolved The issue has been triaged

Comments

@mukundansundar
Copy link
Collaborator

Describe the proposal

[E2E Scenario Test] Reduce time taken for upgrade tests

Potential ideas:
Split out the upgrade tests based on versions and run each in parallel in GitHub Actions.
Also only run one of the the latest and previous version upgrade paths in PRs to reduce time taken there.

Release Note

RELEASE NOTE:
@mukundansundar mukundansundar mentioned this issue May 21, 2021
Merged
3 tasks
@dapr-bot
Copy link
Collaborator

dapr-bot commented Jan 4, 2022

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added the stale label Jan 4, 2022
@mukundansundar mukundansundar added triaged/resolved The issue has been triaged and removed stale labels Jan 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/test/e2e P2 triaged/resolved The issue has been triaged
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dapr-bot @mukundansundar