From 53cdaa58d30216c1f8f2536ab8cb307e3cec8611 Mon Sep 17 00:00:00 2001
From: Alex Crichton <alex@alexcrichton.com>
Date: Thu, 2 Oct 2014 13:14:14 -0700
Subject: [PATCH] std: Help diagnose a flaky test
This test has recently been failing on the bots, and I'm not entirely sure why.
I haven't been able to reproduce locally or on the bots, so I'm adding some
messages to help diagnose the problem hopefully.
---
src/libstd/io/process.rs | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/src/libstd/io/process.rs b/src/libstd/io/process.rs
index 5220e5c984a..d8be92e4514 100644
--- a/src/libstd/io/process.rs
+++ b/src/libstd/io/process.rs
@@ -958,7 +958,9 @@ mod tests {
// don't check windows magical empty-named variables
assert!(k.is_empty() ||
output.as_slice()
- .contains(format!("{}={}", *k, *v).as_slice()));
+ .contains(format!("{}={}", *k, *v).as_slice()),
+ "output doesn't contain `{}={}`\n{}",
+ k, v, output);
}
}
#[cfg(target_os="android")]