-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Add debug testTimeout value #12415
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
Merged
kodiakhq
merged 7 commits into
main
from
trek/zero-2805-add-larger-vitest-timeout-when-in-debug-mode
Oct 29, 2024
Merged
Add debug testTimeout value #12415
kodiakhq
merged 7 commits into
main
from
trek/zero-2805-add-larger-vitest-timeout-when-in-debug-mode
Oct 29, 2024
Conversation
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
🦋 Changeset detectedLatest commit: 273bf57 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
EndangeredMassa
previously approved these changes
Oct 29, 2024
erikareads
previously approved these changes
Oct 29, 2024
Co-authored-by: Sean Massa <EndangeredMassa@gmail.com>
onsclom
previously approved these changes
Oct 29, 2024
erikareads
previously approved these changes
Oct 29, 2024
TooTallNate
requested changes
Oct 29, 2024
Co-authored-by: Nathan Rajlich <n@n8.io>
erikareads
approved these changes
Oct 29, 2024
TooTallNate
approved these changes
Oct 29, 2024
EndangeredMassa
approved these changes
Oct 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For those of us who use a debugger, the test suit exiting early is frustrating. You can get around this by setting this value yourself or running with
--testTimeout
in the terminal but adding this behavior globally seems like a nice quality of life change.I couldn't find a 100% guaranteed way to detect if node is in debug mode but the rough consensus was detecting
debugPort
covered the largest number of cases.I audited all the uses of
vi.setConfig({ testTimeout });
inpackages/cli
and only found one that looked like it could definitely be removed. The use case it covered was negated by #12354.The others mostly came from 413706d or had a comment explaining their need.