fix #154064 which was running the wrong taskgroups#164983
Merged
meganrogge merged 1 commit intomicrosoft:mainfrom Nov 1, 2022
Merged
fix #154064 which was running the wrong taskgroups#164983meganrogge merged 1 commit intomicrosoft:mainfrom
meganrogge merged 1 commit intomicrosoft:mainfrom
Conversation
alexr00
approved these changes
Oct 31, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #154064
This fixes the issue where "Run Test Task" would trigger a build task and vice versa. This is behaviour which shouldn't happen.
The bug was here where we were doing
taskGroup._id === taskGroup._idso the group was being tested against itself and would always be true. So this would execute the first task where the file glob matched (even if the task group was not the one you asked for).Now we properly check the correct task group matches before executing.
I'm surprised TypeScript didn't catch this as we were just comparing the same value with itself.
@alexr00