From 6d5b234ba2705f1bb67da522ab606a26f249eb75 Mon Sep 17 00:00:00 2001 From: Graham Christensen Date: Tue, 11 Jan 2022 14:29:05 -0500 Subject: [PATCH] hydra-eval-jobset/notification.t: comment which jobs produced which messages I tried to write the test in such a way to assert the content matched what we expected, but since the ordering of them is not known, it is quite tricky to write. --- t/scripts/hydra-eval-jobset/notifications.t | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/t/scripts/hydra-eval-jobset/notifications.t b/t/scripts/hydra-eval-jobset/notifications.t index 6cf2a12f..d0bbb3af 100644 --- a/t/scripts/hydra-eval-jobset/notifications.t +++ b/t/scripts/hydra-eval-jobset/notifications.t @@ -79,9 +79,17 @@ subtest "on a fresh evaluation with changed sources" => sub { $listener->block_for_messages(0)->()->{"channel"} )], [ + # The `variable-job` build since it is the only one that is + # totally different in this evaluation. "build_queued", + + # The next two are `stable-job-passing` and `stable-job-failing`, + # since those are the two we explicitly built above "cached_build_finished", "cached_build_finished", + + # Finally, this should be `stable-job-queued` since we never + # built it. "cached_build_queued", ], "we get a notice that a build is queued, one is still queued from a previous eval"