Red Hat Bugzilla – Bug 1270627
report a result whenever extendtesttime.sh is run in /distribution/reservesys
Last modified: 2015-10-15 03:09:44 EDT
To make it easier to see when a reservation has been extended, and for how long, we can make extendtesttime.sh report a result every time it's run. We can record the number of seconds it has been extended for as the result score.
Alex Todorov has contributed a patch for this: http://gerrit.beaker-project.org/4427
Tagged as /distribution/reservesys 3.4-6.
Steps to verify:
1. Run a job with /distribution/reservesys (for example, use Reserve Workflow)
2. Wait for the system to be reserved, e-mail sent
3. Log in and extend the watchdog by 2 hours by running: extendtesttime.sh 2
In the recipe, a new result for /distribution/reservesys named "extend-test-time" appears, with the score equal to the number of hours reservation was extended by.
While trying this out on beaker-devel, I noticed that each extendtesttime.sh invocation does dmesg and AVC checking which creates new task log files. For some reason the log files are prefixed with some kind of UUID, like this:
I've never seen that before, not sure where the UUID is coming from... anyway I guess it's not a big deal.
/distribution/reservesys 3.4-6 has been released.