summaryrefslogtreecommitdiff
path: root/.github/workflows/build.yaml
diff options
context:
space:
mode:
authorNat Goodspeed <nat@lindenlab.com>2023-10-05 10:17:09 -0400
committerNat Goodspeed <nat@lindenlab.com>2023-10-05 10:17:09 -0400
commit7504b1c319373c950e8b8c2c7a8b2f0d9abf1d8b (patch)
treebd9c123c1a2ee1355eecc353e99d0e85e1df2e8f /.github/workflows/build.yaml
parent18b8a68c4688fd1002dab11759d431eab36604ef (diff)
SL-18837: When llrand_test.cpp fails, display the failing value.
It's frustrating and unactionable to have a failing test report merely that the random value was greater than the specified high end. Okay, so what was the value? If it's supposed to be less than the high end, did it happen to be equal? Or was it garbage? We can't reproduce the failure by rerunning! The new ensure_in_exc_range(), ensure_in_inc_range() mechanism is somewhat complex because exactly one test allows equality with the high end of the expected range, where the rest mandate that the function return less than the high end. If that's a bug in the test -- if every llrand function is supposed to return less than the high end -- then we could simplify the test logic.
Diffstat (limited to '.github/workflows/build.yaml')
0 files changed, 0 insertions, 0 deletions