-
Notifications
You must be signed in to change notification settings - Fork 250
test: try gpu test case seq [draft] #8205
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -86,6 +86,11 @@ func RunScenario(t *testing.T, s *Scenario) error { | |
| return runScenario(t, s) | ||
| } | ||
|
|
||
| func RunScenarioSequential(t *testing.T, s *Scenario) error { | ||
| // Default path | ||
| return runScenario(t, s) | ||
| } | ||
|
Comment on lines
+89
to
+92
|
||
|
|
||
| func runScenarioWithPreProvision(t *testing.T, original *Scenario) { | ||
| // This is hard to understand. Some functional magic is used to run the original scenario in two stages. | ||
| // 1. Stage 1: Run the original scenario with pre-provisioning enabled, but skip the main validation and validate only pre-provisioning. | ||
|
|
||
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.
This comment is now misleading: the subtests are not marked
t.Parallel()and the scenario runner used isRunScenarioSequential, so this test is no longer set up for parallel execution. Update/remove the comment (and thetc := tcnote) to match the intended sequential behavior, or addt.Parallel()if parallel subtests are still desired.