std::run::test_pipes is xfail'd #10016
Comments
bors
added a commit
that referenced
this issue
Feb 24, 2014
The std::run module is a relic from a standard library long since past, and there's not much use to having two modules to execute processes with where one is slightly more convenient. This commit merges the two modules, moving lots of functionality from std::run into std::io::process and then deleting std::run. New things you can find in std::io::process are: * Process::new() now only takes prog/args * Process::configure() takes a ProcessConfig * Process::status() is the same as run::process_status * Process::output() is the same as run::process_output * I/O for spawned tasks is now defaulted to captured in pipes instead of ignored * Process::kill() was added (plus an associated green/native implementation) * Process::wait_with_output() is the same as the old finish_with_output() * destroy() is now signal_exit() * force_destroy() is now signal_kill() Closes #2625 Closes #10016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm about to xfail it. It creates some pipes, forks a process, and then does I/O on those pipes. For some reason, the forked program,
cat, never sees that the input to the process is closed, meaning that the test will hang forever.I'm not entirely sure why, and this test should hopefully get fixed soon.
The text was updated successfully, but these errors were encountered: