Skip to content
This repository has been archived by the owner on Oct 15, 2020. It is now read-only.

test: cleanup chakracore customization #580

Merged
merged 1 commit into from
Jul 30, 2018
Merged

Conversation

kfarnung
Copy link
Contributor

Undo obsolete test modifications and enable more tests.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines

@kfarnung kfarnung self-assigned this Jul 30, 2018
@kfarnung
Copy link
Contributor Author

Copy link
Contributor

@sethbrenith sethbrenith left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@@ -21,4 +21,4 @@ async function runTests() {
assert.strictEqual(0, (await instance.expectShutdown()).exitCode);
}

runTests().catch((err) => { console.log(err); process.exit(-1); });
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this just to make us the same as upstream? I believe that we added this because without it, if the test fails it is often via a timeout with no additional information. I suppose we should just upstream that change though.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe this was actually a problem before we had unhandled promise rejection handling. It should correctly print the unhandled rejection and exit with an error now.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like it should do the right thing:

> .\Release\node.exe --expose-internals .\test\sequential\test-inspector-break-e.js
[test] Connecting to a child Node process
[test] Testing /json/list
[err] Debugger listening on ws://127.0.0.1:2957/8bb3dc33-f1f0-43be-98f3-f36d7e0e68d0
[err] For help, see: https://nodejs.org/en/docs/inspector
[err]
[err] Debugger attached.
[err]
Error: foo
   at runTests (E:\GitHub\node-chakracore\test\sequential\test-inspector-break-e.js:19:3)
   at Generator.prototype.next (native code)
   at _tickCallback (internal/process/next_tick.js:68:7)
1
> $LASTEXITCODE
1

@kfarnung
Copy link
Contributor Author

* Undo obsolete test modifications and enable more tests.
* Remove unnecessary deltas with upstream
* Fix lint issues

PR-URL: nodejs#580
Reviewed-By: Seth Brenith <sethb@microsoft.com>
Reviewed-By: Jimmy Thomson <jithomso@microsoft.com>
@kfarnung
Copy link
Contributor Author

It looks like parallel/test-inspector-port-zero-cluster has gotten flakier, but I haven't changed it in this or the previous PR. Will land as is and investigate if it keeps hitting.

@kfarnung kfarnung merged commit 82aa002 into nodejs:master Jul 30, 2018
@kfarnung kfarnung deleted the testfixes branch July 30, 2018 20:54
kfarnung added a commit to kfarnung/node-chakracore that referenced this pull request Aug 6, 2018
* Undo obsolete test modifications and enable more tests.
* Remove unnecessary deltas with upstream
* Fix lint issues

PR-URL: nodejs#580
Reviewed-By: Seth Brenith <sethb@microsoft.com>
Reviewed-By: Jimmy Thomson <jithomso@microsoft.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants