From d1f5f225664a03ad505038955f72d1c643365583 Mon Sep 17 00:00:00 2001 From: John Ousterhout Date: Fri, 1 May 2020 16:56:30 -0700 Subject: [PATCH] Mark test alarm-priority as timing-sensitive --- doc/threads.texi | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) 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., -- 2.30.2