Skip to content

test: don't use cwd for relative path - #4477

Merged
jbergstroem merged 1 commit into
nodejs:masterfrom
jbergstroem:fix/realpath-relative-baseurl
Dec 30, 2015
Merged

test: don't use cwd for relative path#4477
jbergstroem merged 1 commit into
nodejs:masterfrom
jbergstroem:fix/realpath-relative-baseurl

Conversation

@jbergstroem

Copy link
Copy Markdown
Member

With the introduction of temporary paths in the test runner realpath tests would bail in scenarios where the temporary folder wasn't in the same directory as the source code.

/R=@Trott?

@jbergstroemjbergstroem added the test Issues and PRs related to the tests. label Dec 30, 2015
@jbergstroem

Copy link
Copy Markdown
MemberAuthor

CI: https://ci.nodejs.org/job/node-test-commit/1571/

Will likely get a fail on raspberry pi because the path to common pipe will be too long. A fix for that would either be making it flaky for a while ("fix") or changing the temporary path which we explore through #4476.

@jbergstroem

Copy link
Copy Markdown
MemberAuthor

@Trott mentions that this actually doesn't properly address relative tests. Will address shortly.

@Trott

Copy link
Copy Markdown
Member

LGTM if CI is happy (or happier)

@jbergstroem

Copy link
Copy Markdown
MemberAuthor

@mscdexmscdex added the fs Issues and PRs related to the fs subsystem / file system. label Dec 30, 2015
@Trott

Copy link
Copy Markdown
Member

Bonus benefit is that you can run this with CWD of test/parallel where the previous version fails in that case.

With the introduction of temporary paths in the test runner
realpath tests would bail in scenarios where the temporary folder
wasn't in the same directory as the source code.
PR-URL: nodejs#4477
Reviewed-By: Rich Trott <rtrott@gmail.com>
@jbergstroem
jbergstroemforce-pushed the fix/realpath-relative-baseurl branch from ccc802d to 6efa031CompareDecember 30, 2015 06:51
@jbergstroem
jbergstroem merged commit 6efa031 into nodejs:masterDec 30, 2015
Fishrock123 pushed a commit to Fishrock123/node that referenced this pull request Jan 6, 2016
With the introduction of temporary paths in the test runner
realpath tests would bail in scenarios where the temporary folder
wasn't in the same directory as the source code.
PR-URL: nodejs#4477
Reviewed-By: Rich Trott <rtrott@gmail.com>
@richardlau

Copy link
Copy Markdown
Member

@thealphanerd This will need land on v4.x-staging since #3325 has landed and made the temp dir customizable via NODE_TEST_DIR while removing NODE_COMMON_PIPE.

jasnell pushed a commit that referenced this pull request Jan 15, 2016
With the introduction of temporary paths in the test runner
realpath tests would bail in scenarios where the temporary folder
wasn't in the same directory as the source code.
PR-URL: #4477
Reviewed-By: Rich Trott <rtrott@gmail.com>
@jasnell

Copy link
Copy Markdown
Member

Landed in v4.x-staging in bb2e2d0

MylesBorins pushed a commit that referenced this pull request Jan 19, 2016
With the introduction of temporary paths in the test runner
realpath tests would bail in scenarios where the temporary folder
wasn't in the same directory as the source code.
PR-URL: #4477
Reviewed-By: Rich Trott <rtrott@gmail.com>
@MylesBorinsMylesBorins mentioned this pull request Jan 19, 2016
scovetta pushed a commit to scovetta/node that referenced this pull request Apr 2, 2016
With the introduction of temporary paths in the test runner
realpath tests would bail in scenarios where the temporary folder
wasn't in the same directory as the source code.
PR-URL: nodejs#4477
Reviewed-By: Rich Trott <rtrott@gmail.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fsIssues and PRs related to the fs subsystem / file system.testIssues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

@jbergstroem@Trott@richardlau@jasnell@mscdex@rvagg