summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCole Faust <colefaust@google.com>2024-05-15 11:38:31 -0700
committerCole Faust <colefaust@google.com>2024-05-15 11:38:31 -0700
commit1213947699f1469bc29315955ba3c10d3a60c8b4 (patch)
treed4094e39abcb84e1e86afd25fbaad2fb1069402e
parentea9d45feebc5954989fcb1273fa5bfb095de4eaa (diff)
downloadn2-main.tar.gz
Increase the sleep before/after running commandsmain
Adding this sleep did seem to drastically reduce the flakiness, but we recently got another flake. Increase the length of the sleep to hopefully hammer out the last bit of flakeyness. Test: Cargo test Change-Id: I3b0ef31efc92357f90e49d04876f17397fa507e5
-rw-r--r--tests/e2e/mod.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/tests/e2e/mod.rs b/tests/e2e/mod.rs
index ec0e348..e1a8f61 100644
--- a/tests/e2e/mod.rs
+++ b/tests/e2e/mod.rs
@@ -96,9 +96,9 @@ impl TestSpace {
// run n2 again, but when they flake, n2 is not noticing the changes. So maybe
// the filesystem changes happen so fast after n2 finishes that they're getting
// the same mtime?
- std::thread::sleep(std::time::Duration::from_millis(1));
+ std::thread::sleep(std::time::Duration::from_millis(10));
let result = cmd.current_dir(self.dir.path()).output();
- std::thread::sleep(std::time::Duration::from_millis(1));
+ std::thread::sleep(std::time::Duration::from_millis(10));
result
}