blob: 91d8e4f381a368af580596eacf6a6bd236212725 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
|
// run-pass
// ignore-emscripten no processes
// ignore-sgx no processes
use std::env;
use std::fs;
use std::path::Path;
use std::process::Command;
fn main() {
// Checks the behavior of current_dir when used with a relative exe path.
let me = env::current_exe().unwrap();
if matches!(env::args().skip(1).next().as_deref(), Some("current-dir")) {
let cwd = env::current_dir().unwrap();
assert_eq!(cwd.file_name().unwrap(), "bar");
std::process::exit(0);
}
let exe = me.file_name().unwrap();
let cwd = me.parent().unwrap();
eprintln!("cwd={:?}", cwd);
// Change directory to where the exectuable is located, since this test
// fundamentally needs to use relative paths. In some cases (like
// remote-test-server), the current_dir can be somewhere else, so make
// sure it is something we can use. We assume we can write to this
// directory.
env::set_current_dir(&cwd).unwrap();
let foo = cwd.join("foo");
let bar = cwd.join("bar");
fs::create_dir_all(&foo).unwrap();
fs::create_dir_all(&bar).unwrap();
fs::copy(&me, foo.join(exe)).unwrap();
// Unfortunately this is inconsistent based on the platform, see
// https://github.com/rust-lang/rust/issues/37868. On Windows,
// it is relative *before* changing the directory, and on Unix
// it is *after* changing the directory.
let relative_exe = if cfg!(windows) {
Path::new("foo").join(exe)
} else {
Path::new("../foo").join(exe)
};
let status = Command::new(relative_exe)
.arg("current-dir")
.current_dir("bar")
.status()
.unwrap();
assert!(status.success());
}
|
