-
Notifications
You must be signed in to change notification settings - Fork 13k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
modify fds-are-cloexec test to open a file that exists #35885
Conversation
I'd argue it is not. |
Maybe the test should create a temporary file, close it, and then open it again? |
If such an assumption was “good enough” for the version opening Makefile, I feel it is good enough for the new version as well. You could also use any of the non-autogenerated files from project root, like |
@bors r=nagisa |
📌 Commit b40754f has been approved by |
modify fds-are-cloexec test to open a file that exists Fixes rust-lang#35753. Is it a valid assumption that the current directory is always the root of the repo when the tests are run? r? @nagisa
modify fds-are-cloexec test to open a file that exists Fixes rust-lang#35753. Is it a valid assumption that the current directory is always the root of the repo when the tests are run? r? @nagisa
modify fds-are-cloexec test to open a file that exists Fixes rust-lang#35753. Is it a valid assumption that the current directory is always the root of the repo when the tests are run? r? @nagisa
https://buildbot.rust-lang.org/builders/auto-mac-64-opt/builds/10287/steps/test/logs/stdio |
I guess... it's not a valid assumption? Is that a non-rustbuild builder? On Aug 25, 2016 07:36, "Manish Goregaokar" notifications@github.com wrote:
|
Thats make. It should operate The same way since there can only ever be one Anyhow, if a path to the test does not work, then in order to avoid writing On Aug 25, 2016 4:53 PM, "Alex Burka" notifications@github.com wrote:
|
This will break out-of-tree builds. |
@arielb1 I guess they didn't work before either. |
The test already doesn't run on Windows, how about opening /dev/null? |
Out-of-tree builds did work before. I was using them all the time. I imagine you could open |
Well, it was assuming that the Makefile was in the current directory. I On Thu, Aug 25, 2016 at 12:33 PM, arielb1 notifications@github.com wrote:
|
The way you do an out-of-tree build is
That way, you end up with a |
You can do |
Let's try that. |
@bors r+ I don't want to rollup this |
📌 Commit b2cd3e5 has been approved by |
Fixes #35753.
Is it a valid assumption that the current directory is always the root of the repo when the tests are run?
r? @nagisa