From 506c71c980ab97f28e89032c2bba9a471c0b1fd4 Mon Sep 17 00:00:00 2001
From: Andrew Chin <achin@eminence32.net>
Date: Fri, 24 Jan 2014 19:15:06 -0500
Subject: [PATCH] Use an absolute path in test_process_output_fail_to_start

This test is designed to ensure that running a non-existent executable
results in a correct error message (FileNotFound in this case of this
test).  However, if you try to run an executable that doesn't exist, and
that requires searching through the $PATH, and one of the $PATH components
is not readable, then a PermissionDenied error will be returned, instead
of FileNotFound.
---
 src/libstd/run.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/libstd/run.rs b/src/libstd/run.rs
index f42163791a6a..d0ca6efd2472 100644
--- a/src/libstd/run.rs
+++ b/src/libstd/run.rs
@@ -360,7 +360,7 @@ mod tests {
             trapped_io_error = true;
             assert_eq!(e.kind, FileNotFound);
         }).inside(|| -> Option<run::ProcessOutput> {
-            run::process_output("no-binary-by-this-name-should-exist", [])
+            run::process_output("/no-binary-by-this-name-should-exist", [])
         });
         assert!(trapped_io_error);
         assert!(opt_outp.is_none());