-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
test: add unexpected behavior repro test #55095
test: add unexpected behavior repro test #55095
Conversation
Review requested:
|
Thanks for bringing this up, I realised this bug as well, and I forgot to create an issue for it 😄 |
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.
I know this is a draft, I only have one nitpick
if (testRuns.length === 1) { | ||
firstRunCompleted.resolve(); | ||
} else if (testRuns.length === 2) { | ||
secondRunCompleted.resolve(); | ||
} else if (testRuns.length === 3) { | ||
thirdRunCompleted.resolve(); | ||
} else if (testRuns.length === 4) { | ||
fourthRunCompleted.resolve(); | ||
} |
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.
Switch statement?
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.
Yep no problem at all 🚀
I'm closing this since another PR it's proposing a fix 🚀 |
I'm opening this PR as a draft since I have not had the time to fix the issue yet.
This test highlights what I believe to be an issue related to file watcher owners.
Basically, given a specific series of updates to files under watch, the link between the test file and its dependency is being lost.
@cjihrig @jakecastelli, FYI