[2.3, trunk] Running old format test script results in it being reported as failed (even if suceeded)

Bug #1714580 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Expired
High
Unassigned

Bug Description

smartctl had not been ported to the new format of tests.

When running hardware testing, the test will successfully ran (you could see the log), however, it will always be marked as failed.

This makes it seem that tests written in old format are not being correctly marked as failed/succeeded.

Changed in maas:
importance: Undecided → Critical
milestone: none → 2.3.0
status: New → Triaged
tags: added: hardware-testing testing
Changed in maas:
milestone: 2.3.0 → 2.3.0beta2
Changed in maas:
milestone: 2.3.0beta2 → 2.3.0beta3
Changed in maas:
milestone: 2.3.0beta3 → 2.3.0beta4
Changed in maas:
milestone: 2.3.0beta4 → 2.3.x
Changed in maas:
importance: Critical → High
status: Triaged → Incomplete
Changed in maas:
milestone: 2.3.x → 2.4.x
Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.