-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
prototype: Parallelize tf unit tests #36294
base: main
Are you sure you want to change the base?
Conversation
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.
Nice, I do like this as a starting point but I'd want to push it further. For example we can add provider and variable nodes into the new test graph as well so these also benefit from the up front computation that the runs are also getting.
But, we could definitely do that iteratively. So start with just the run blocks, then in a follow up PR add the variables, then add the providers, etc.
dependency, ok := prevs[runName] | ||
if !ok { | ||
// TODO: should we catch this error, or leave it, as it will still be caught in the test? | ||
return fmt.Errorf("dependency %q not found for run %q", runName, run.Name) |
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.
one of the advantages of moving to the graph is exactly this - we can catch these kind of errors right at the beginning and then report this as a kind of compilation error. So definitely leave this as is.
7ded152
to
eae3add
Compare
eae3add
to
5811743
Compare
Fixes #
WIP
Target Release
1.11.x
CHANGELOG entry