Skip to content

test: increase coverage for internal/errors.js - #15044

Closed
starkwang wants to merge 1 commit into
nodejs:masterfrom
starkwang:test-internal-errors-improve
Closed

test: increase coverage for internal/errors.js#15044
starkwang wants to merge 1 commit into
nodejs:masterfrom
starkwang:test-internal-errors-improve

Conversation

@starkwang

@starkwangstarkwang commented Aug 26, 2017

Copy link
Copy Markdown
Contributor
Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • commit message follows commit guidelines
Affected core subsystem(s)

test

@nodejs-github-botnodejs-github-bot added the test Issues and PRs related to the tests. label Aug 26, 2017
@mscdexmscdex added the errors Issues and PRs related to JavaScript errors originated in Node.js core. label Aug 26, 2017
@hiroppy

Copy link
Copy Markdown
Member

@jasnell

Copy link
Copy Markdown
Member

@benjamingr

Copy link
Copy Markdown
Member

@refack @nodejs/build can you take a look at the repeated failure at https://ci.nodejs.org/job/node-test-commit-windows-fanned/11382/

@BridgeAR

BridgeAR commented Aug 30, 2017

Copy link
Copy Markdown
Member

Landed in 44d4865

@refack

Copy link
Copy Markdown
Contributor

@refack @nodejs/build can you take a look at the repeated failure at https://ci.nodejs.org/job/node-test-commit-windows-fanned/11382/

Will do

BridgeAR pushed a commit that referenced this pull request Aug 30, 2017
PR-URL: #15044
Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
@refack

Copy link
Copy Markdown
Contributor

@benjamingr AFAICT I fixed it:
https://ci.nodejs.org/job/node-compile-windows/11452/label=win-vs2017/console (same machine test-rackspace-win2012r2-x64-10)

@jasnell

Copy link
Copy Markdown
Member

hmm looks like a build bot failure on windows again. Trying one more time https://ci.nodejs.org/job/node-test-commit-windows-fanned/11404/

@BridgeAR

Copy link
Copy Markdown
Member

Well instead of 2017 now 2015 is failing.

cjihrig pushed a commit to cjihrig/node that referenced this pull request Aug 31, 2017
PR-URL: nodejs#15044
Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
addaleax pushed a commit to addaleax/ayo that referenced this pull request Sep 5, 2017
PR-URL: nodejs/node#15044
Reviewed-By: Yuta Hiroto <hello@about-hiroppy.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
@MylesBorins

Copy link
Copy Markdown
Contributor

The tests are failing on v8.x. Not sure exactly what is going on, but it may have something to do with util.format

AssertionError [ERR_ASSERTION]: 'The "a" argument must be of type not b' === 'The "a" argument must not be of type b'
at Object.<anonymous> (/Users/mborins/code/node/master/test/parallel/test-internal-errors.js:202:8)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
at Module.load (module.js:507:32)
at tryModuleLoad (module.js:470:12)
at Function.Module._load (module.js:462:3)
at Function.Module.runMain (module.js:609:10)
at startup (bootstrap_node.js:194:16)
at bootstrap_node.js:619:3

@jasnell

Copy link
Copy Markdown
Member

I believe this depends on a previous semver-major. Marking don't land on v8.x

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

errorsIssues and PRs related to JavaScript errors originated in Node.js core.testIssues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants

@starkwang@hiroppy@jasnell@benjamingr@BridgeAR@refack@MylesBorins@addaleax@mscdex@nodejs-github-bot