timeout in testing scripts ignores the days if set to greater than 24 hours

Bug #1906212 reported by Hemanth Nakkina
6
This bug affects 1 person
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://github.com/maas/maas/blob/master/src/metadataserver/api.py#L1251

Related branches

Revision history for this message
Hemanth Nakkina (hemanth-n) wrote :
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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers