From: John Ousterhout <ouster@cs.stanford.edu>
Date: Fri, 1 May 2020 23:56:30 +0000 (-0700)
Subject: Mark test alarm-priority as timing-sensitive
X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3f6660db7e24d6efb4c4b5136131ca8ebfa54bde;p=pintos-anon

Mark test alarm-priority as timing-sensitive
---

diff --git a/doc/threads.texi b/doc/threads.texi
index bf8546e..c9094bc 100644
--- a/doc/threads.texi
+++ b/doc/threads.texi
@@ -648,7 +648,8 @@ to cause many of the tests to fail.
 Using the jitter feature in Bochs (@pxref{Debugging versus Testing})
 is a great way to discover bugs that are timing dependent. However,
 the following tests are known to
-fail with jitter even if your code is correct: @code{alarm-simultaneous},
+fail with jitter even if your code is correct: @code{alarm-priority},
+@code{alarm-simultaneous},
 @code{mlfqs-recent-1}, @code{mlfqs-fair-2}, @code{mlfqs-fair-20},
 @code{mlfqs-nice-2}, @code{mlfqs-nice-10}, and @code{priority-fifo}.
 The behavior of these tests can sometimes vary based on timing (e.g.,