[2.3, HWTv2] Hardware tests do not provide start, current running or estimated run time
Bug #1723425 reported by
Andres Rodriguez
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
High
|
Blake Rouse | ||
Bug Description
Hardware Testing needs to provide one or all of the following:
1. start time
2. current running time
3. total estimated runtime
What we could also do is something line:
0:00:01 of Unknown
0:00:02 of Unknown
0:00:03 of Unknown
0:00:04 of Unknown
Once the test finishes, we show the current runtime, e.g:
3:36:46
On the subsequent runtime, we could show:
0:00:01 of 3:36:46 (approximately)
0:00:02 of 3:36:46 (approximately)
0:00:02 of 3:36:46 (approximately)
0:00:02 of 3:36:46 (approximately)
Related branches
~blake-rouse/maas:lp1723425
- MAAS Lander: Approve
- Lee Trager (community): Approve
- Mike Pontillo (community): Approve
-
Diff: 519 lines (+316/-8)12 files modifiedsrc/maasserver/api/scriptresults.py (+3/-0)
src/maasserver/api/tests/test_scriptresults.py (+9/-0)
src/maasserver/static/js/angular/directives/script_runtime.js (+57/-0)
src/maasserver/static/js/angular/directives/tests/test_script_runtime.js (+89/-0)
src/maasserver/static/partials/script-results-list.html (+8/-8)
src/maasserver/views/combo.py (+1/-0)
src/maasserver/websockets/handlers/node.py (+6/-0)
src/maasserver/websockets/handlers/node_result.py (+6/-0)
src/maasserver/websockets/handlers/tests/test_machine.py (+12/-0)
src/maasserver/websockets/handlers/tests/test_node_result.py (+6/-0)
src/metadataserver/models/scriptresult.py (+45/-0)
src/metadataserver/models/tests/test_scriptresult.py (+74/-0)
~newell-jensen/maas:lp1723425
- Mike Pontillo (community): Needs Fixing
-
Diff: 436 lines (+217/-8)11 files modifiedsrc/maasserver/api/scriptresults.py (+6/-0)
src/maasserver/api/tests/test_scriptresults.py (+18/-0)
src/maasserver/static/js/angular/directives/script_runtime.js (+47/-0)
src/maasserver/static/js/angular/directives/tests/test_script_runtime.js (+62/-0)
src/maasserver/static/partials/script-results-list.html (+8/-8)
src/maasserver/views/combo.py (+1/-0)
src/maasserver/websockets/handlers/node.py (+6/-0)
src/maasserver/websockets/handlers/node_result.py (+6/-0)
src/maasserver/websockets/handlers/tests/test_machine.py (+12/-0)
src/maasserver/websockets/handlers/tests/test_node_result.py (+6/-0)
src/metadataserver/models/scriptresult.py (+45/-0)
| Changed in maas: | |
| milestone: | none → 2.3.0beta4 |
| importance: | Undecided → High |
| status: | New → Triaged |
| description: | updated |
| description: | updated |
| Changed in maas: | |
| assignee: | nobody → Maria Vrachni (m-vrachnis) |
Revision history for this message
| Lee Trager (ltrager) wrote | #1 |
| summary: |
- [2.3, HWTv2] Hardware tests do not provide start, current running and + [2.3, HWTv2] Hardware tests do not provide start, current running or estimated run time |
| Changed in maas: | |
| assignee: | Maria Vrachni (m-vrachnis) → Newell Jensen (newell-jensen) |
| status: | Triaged → In Progress |
| Changed in maas: | |
| milestone: | 2.3.0beta4 → 2.3.0rc1 |
| Changed in maas: | |
| milestone: | 2.3.0rc1 → 2.3.0rc2 |
| Changed in maas: | |
| assignee: | Newell Jensen (newell-jensen) → Blake Rouse (blake-rouse) |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
The hardware results table is pretty full right now. I think we should allow the runtime column to display a counter when running. To accomplish this we would implement a new directive which would accept a start time and runtime value.
* If runtime isn't blank the value of runtime will be displayed.
* If only the start time is set and the script is running a counter will be displayed which increments every seconds.
* If the script hasn't started running or was aborted runtime will remain blank.