| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
LGTM if CI is happy (which means the tests pass linting). I don't mind going with this test for #728 and closing the PR I opened for that. |
Sorry, something went wrong.
|
All of these tests appear to use the wrong path for common. Should be ../common rather than ./test/common. |
Sorry, something went wrong.
|
Oops, I had been working on the tests in a different directory. Fixed now. |
Sorry, something went wrong.
|
And make jslint passes. |
Sorry, something went wrong.
|
I guess make test-known-issues passes too? Tangent: Should test and/or test-ci include test-known-issues so that we make sure we remove tests from there when the issues are fixed (especially if we fix them accidentally)? |
Sorry, something went wrong.
|
(And, of course: Still LGTM!) |
Sorry, something went wrong.
I'm leaning toward no. I wanted this functionality mostly to help triage the issue tracker. I created the repro-exists label to add to known issues that have tests. If we accidentally fix something, I'd hate to see it cause any friction at all with a legitimate PR. That said, if others wanted to add this to test or test-ci, I wouldn't fight over it. |
Sorry, something went wrong.
This commit adds tests for several known issues. Refs: nodejs#1901 Refs: nodejs#728 Refs: nodejs#4778 Refs: nodejs#947 Refs: nodejs#2734 PR-URL: nodejs#5653 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
|
Landed in 10bc673. Thanks for the reviews. |
Sorry, something went wrong.
|
Marking this lts-watch but it depends on landing the original PR that adds this capability (can't recall the pr number off hand) |
Sorry, something went wrong.
|
+1 for LTS as with the original addition of this dir |
Sorry, something went wrong.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Pull Request check-list
Please make sure to review and check all of these items:
this change (including linting)?
test (or a benchmark) included?
existing APIs, or introduces new ones)?
Affected core subsystem(s)
test
Description of change
This commit adds tests for several known issues.
Refs: #1901
Refs: #728
Refs: #4778
Refs: #947
Refs: #2734
R=@Trott