timeout in testing scripts ignores the days if set to greater than 24 hours
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Hemanth Nakkina |
Bug Description
The following testing script gets TIMEDOUT in 10 minutes.
Expectation is to run successfully or time out after 1 day 10 minutes. (24:05:00 from script + 5 min grace period in timeout in maas)
# --- Start MAAS 1.0 script metadata ---
# name: shouldfail5m
# title: CPU validation
# description: Run stress-ng memory tests for 12 hours.
# script_type: test
# hardware_type: cpu
# packages: {apt: stress-ng}
# timeout: 24:05:00
# --- End MAAS 1.0 script metadata ---
sudo -n stress-ng --aggressive -a 0 --class cpu,cpu-cache --ignite-cpu \
--log-brief --metrics-brief --times --tz --verify --timeout 24h
Seems like the conversion of timeout datetime object in metadataserver code is ignoring the number of days [1]
[1] https:/
Related branches
- Lee Trager (community): Approve
- MAAS Lander: Approve
- Hemanth Nakkina (community): Needs Resubmitting
- Dougal Matthews (community): Needs Fixing
-
Diff: 145 lines (+58/-9)2 files modifiedsrc/metadataserver/api.py (+4/-2)
src/metadataserver/tests/test_api.py (+54/-7)
Changed in maas: | |
assignee: | nobody → Hemanth Nakkina (hemanth-n) |
importance: | Undecided → Medium |
milestone: | none → 2.10-next |
status: | New → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | 3.0.0 → 3.0-beta1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
PR submitted for review: https:/ /code.launchpad .net/~hemanth- n/maas/ +git/maas/ +merge/ 394615