Skip to content
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

timers: test timeout NaN warning in promises version #53622

Merged
merged 2 commits into from
Jul 22, 2024

Conversation

benjamingr
Copy link
Member

@benjamingr benjamingr commented Jun 28, 2024

Hey, #46678 landed adding a warning when NaN is passed to timers. I noticed a test was missing for timers/promises there (the code works on both paths) - rather than holding that PR I figured we'd land it and I'd PR a test for timers/promises in a separate PR.

cc @jakecastelli

Refs: #46678

@benjamingr benjamingr added the semver-major PRs that contain breaking changes and should be released in the next major version. label Jun 28, 2024
@nodejs-github-bot nodejs-github-bot added needs-ci PRs that need a full CI run. test Issues and PRs related to the tests. labels Jun 28, 2024
@debadree25 debadree25 added the request-ci Add this label to start a Jenkins CI on a PR. label Jun 28, 2024
@debadree25
Copy link
Member

debadree25 commented Jun 28, 2024

weird the CI bot is not here yet 🤔

Edit: ah CI is in lockdown missed the PSA oops

@aduh95 aduh95 added author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue-squash Add this label to instruct the Commit Queue to squash all the PR commits into the first one. dont-land-on-v18.x PRs that should not land on the v18.x-staging branch and should not be released in v18.x. dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. dont-land-on-v21.x dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. and removed semver-major PRs that contain breaking changes and should be released in the next major version. labels Jun 29, 2024
@aduh95
Copy link
Contributor

aduh95 commented Jun 29, 2024

The subsystem should be test: given it only touch the tests. Removed semver-major PRs that contain breaking changes and should be released in the next major version. in favor of dont-land labels.

@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jul 3, 2024
@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot
Copy link
Collaborator

@aduh95 aduh95 merged commit 2591638 into nodejs:main Jul 22, 2024
68 checks passed
@aduh95
Copy link
Contributor

aduh95 commented Jul 22, 2024

Landed in 2591638

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
author ready PRs that have at least one approval, no pending requests for changes, and a CI started. commit-queue-squash Add this label to instruct the Commit Queue to squash all the PR commits into the first one. dont-land-on-v18.x PRs that should not land on the v18.x-staging branch and should not be released in v18.x. dont-land-on-v20.x PRs that should not land on the v20.x-staging branch and should not be released in v20.x. dont-land-on-v22.x PRs that should not land on the v22.x-staging branch and should not be released in v22.x. needs-ci PRs that need a full CI run. test Issues and PRs related to the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants