GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||
GeezerVison is showing github.com — test: fixup failing test/internet/test-dns.js by jasnell · Pull Request #38241 · nodejs/node Conversation
Member
The Signed-off-by: James M Snell [email protected]
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
addaleax
approved these changes
richardlau
approved these changes
This comment has been minimized.
marsonya
approved these changes
ycjcl868
approved these changes
Contributor
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
|
There was an error while loading. Please reload this page.
|
CI: https://ci.nodejs.org/job/node-test-pull-request/37483/ 💚 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
CI is green, there's no reason to make this wait the full 48 hours. Please 👍🏻 to fast-track |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
@jasnell Should we update this comment here as well:
| // Try to set an invalid TTL (valid ttl is > 0 and < 256) |
- // Try to set an invalid TTL (valid ttl is > 0 and < 256) + // Try to set an invalid TTL (valid ttl is >= 0 and < 256)
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There's the known failing Build from tarball action. Our collaborator guide says
You could argue the failing test is nothing to do with this PR, but if collaborators are free to ignore failing CI we might as well not bother running them. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Ugh... I missed that failing github ci bit...extremely frustrating. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
The `ttl` for the `nodejs.org` DNS record is returning `0` currently. The test checks for `> 0`, causing the test to fail. Signed-off-by: James M Snell <[email protected]>
0d92399 to
312ad3a
Compare
There was an error while loading. Please reload this page.
|
Landed in 5e588c1 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
The `ttl` for the `nodejs.org` DNS record is returning `0` currently. The test checks for `> 0`, causing the test to fail. Signed-off-by: James M Snell <[email protected]> PR-URL: #38241 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Darshan Sen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
The `ttl` for the `nodejs.org` DNS record is returning `0` currently. The test checks for `> 0`, causing the test to fail. Signed-off-by: James M Snell <[email protected]> PR-URL: #38241 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Darshan Sen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
The `ttl` for the `nodejs.org` DNS record is returning `0` currently. The test checks for `> 0`, causing the test to fail. Signed-off-by: James M Snell <[email protected]> PR-URL: #38241 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Darshan Sen <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.