| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
CI (without passing NODE_TMP_DIR): https://ci.nodejs.org/job/node-test-commit/804/ |
Sorry, something went wrong.
There was a problem hiding this comment.
__dirname perhaps?
Sorry, something went wrong.
|
I'm still catching up but did NODE_COMMON_PIPE get removed from all the tests already? |
Sorry, something went wrong.
|
AFAIK it was never in tests, just passed to exports.PIPE [edit: if passed to common.js]. |
Sorry, something went wrong.
|
I'll leave it to someone more in tune with the entirety of the build process to LGTM or not, but I'm +1. The common.PIPE improvements that build on this to enable parallel testing will be in a subsequent PR? |
Sorry, something went wrong.
|
Prior to removal, if NODE_COMMON_PIPE was unset exports.PIPE would be stored in the temporary directory which works fine in parallel runs since the thread id is appended to common.tmpDir. The change I'm introducing is the ability to change where tmpDir lives. |
Sorry, something went wrong.
|
@jbergstroem ... what's the status on this? Looks like it needs to be rebased at a minimum |
Sorry, something went wrong.
|
@jasnell waiting for feedback/review. I'll rebase. |
Sorry, something went wrong.
|
@Trott to answer your question regarding "enabling" parallel builds -- that would be something we'd most likely be changing in the jenkins setup. |
Sorry, something went wrong.
|
LGTM Can you ensure that testRoot exists? Since this is now a variable, it can be useful to set it to a directory that does not exist yet. To run parallel tests on Windows, the pipe name should also depend on the thread number. What about adding something like lines 64 and 66 after 139? |
Sorry, something went wrong.
|
@joaocgreis does the pipe really have to depend on a thread number since it already lives in its own thread folder (tmp.$thread)? Regarding creating the directory, that's already part of refreshTmpDir. |
Sorry, something went wrong.
|
@jbergstroem the pipe is defined differently in windows, it is a global name, not a file in the test folder (as created in line 139). The tmp.$thread directories are created by refreshTmpDir, but testRoot is not. Currently this is not a problem since the test directory always exists, but if you set NODE_TEST_DIR to a directory that does not exit, tests fail. There could be a mkdir(testRoot) or just a descriptive exception if it does not exist, but on the other hand the error is pretty clear so feel free to ignore this suggestion. |
Sorry, something went wrong.
|
Rebased and fixed an issue with two tests that assumed a specific folder structure. CI (which again shouldn't branch into this): https://ci.nodejs.org/job/node-test-commit/1324/ |
Sorry, something went wrong.
|
Oh, and @joaocgreis -- I now create the dir through refreshTmp. |
Sorry, something went wrong.
There was a problem hiding this comment.
existsSync() is deprecated so maybe use one of the suggested alternatives?
Sorry, something went wrong.
|
ping! |
Sorry, something went wrong.
There was a problem hiding this comment.
needs space between + and '.'
Sorry, something went wrong.
There was a problem hiding this comment.
should be +=
Sorry, something went wrong.
|
@jbergstroem wouldn't checking the NODE_TEST_DIR directly in the test runner be better? |
Sorry, something went wrong.
|
@joaocgreis checking in the runner now. Also, created an option called --test-dir supplementing NODE_TEST_DIR. |
Sorry, something went wrong.
|
CI (should be unaffected): https://ci.nodejs.org/job/node-test-commit/1560/ |
Sorry, something went wrong.
In CI we previously passed `NODE_COMMON_PIPE` to the test runner to avoid long filenames. Add an option to the test runner that allows the user to change the temporary directory instead. This also allows us to run test suites in parallel since `NODE_COMMON_PIPE` otherwise would have been used from multiple tests at the same time. PR-URL: #3325 Reviewed-By: Joao Reis <reis@janeasystems.com>
A few tests assumed that temp dirs always lived in the same parent folder as fixtures. Make these use `common.tmpDir` instead. PR-URL: #3325 Reviewed-By: Joao Reis <reis@janeasystems.com>
Sorry, something went wrong.
In CI we previously passed `NODE_COMMON_PIPE` to the test runner to avoid long filenames. Add an option to the test runner that allows the user to change the temporary directory instead. This also allows us to run test suites in parallel since `NODE_COMMON_PIPE` otherwise would have been used from multiple tests at the same time. PR-URL: #3325 Reviewed-By: Joao Reis <reis@janeasystems.com>
A few tests assumed that temp dirs always lived in the same parent folder as fixtures. Make these use `common.tmpDir` instead. PR-URL: #3325 Reviewed-By: Joao Reis <reis@janeasystems.com>
In CI we previously passed `NODE_COMMON_PIPE` to the test runner to avoid long filenames. Add an option to the test runner that allows the user to change the temporary directory instead. This also allows us to run test suites in parallel since `NODE_COMMON_PIPE` otherwise would have been used from multiple tests at the same time. PR-URL: nodejs#3325 Reviewed-By: Joao Reis <reis@janeasystems.com>
A few tests assumed that temp dirs always lived in the same parent folder as fixtures. Make these use `common.tmpDir` instead. PR-URL: nodejs#3325 Reviewed-By: Joao Reis <reis@janeasystems.com>
| Back | FazBrowse Home | New Git URL |
In CI we previously passed NODE_COMMON_PIPE to the test runner to avoid long filenames on Windows. Avoid long paths by changing the temporary directory instead. This also allows us to run test suites in parallel since NODE_COMMON_PIPE otherwise would have been used from multiple tests.
/R=@nodejs/build, @Trott ?