raito/hydra
0
0
Fork 0
forked from lix-project/hydra
Code Pull requests Activity

hydra-eval-jobset/notification.t: comment which jobs produced which messages

Browse source 
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.
This commit is contained in:
Graham Christensen 2022-01-11 14:29:05 -05:00
parent 42edd3a9d8
commit 6d5b234ba2
1 changed files with 8 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
t/scripts/hydra-eval-jobset/notifications.t
View file

@ -79,9 +79,17 @@ subtest "on a fresh evaluation with changed sources" => sub {
$listener->block_for_messages(0)->()->{"channel"} $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", "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",
"cached_build_finished", "cached_build_finished",
# Finally, this should be `stable-job-queued` since we never
# built it.
"cached_build_queued", "cached_build_queued",
], ],
"we get a notice that a build is queued, one is still queued from a previous eval" "we get a notice that a build is queued, one is still queued from a previous eval"