test runner should give access to testbed log in all cases
Bug #1287256 reported by
Vincent Ladeuil
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu CI Engine |
Fix Released
|
Critical
|
Vincent Ladeuil | ||
Ubuntu CI Services |
Fix Released
|
Critical
|
Vincent Ladeuil |
Bug Description
To help debug testbed setups, the test runner (which already track the console log) should archive that in a place that we can reach or as an artifact (preferred).
This may a bit tricky as the test runner poll that console log to detect when cloud-init is done and we don't want the repeated parts.
Related branches
lp:~vila/ubuntu-ci-services-itself/1287256-tr-logs
- Chris Johnston (community): Approve
-
Diff: 136 lines (+35/-12)3 files modifiedci-utils/ci_utils/amqp_worker.py (+5/-4)
test_runner/tstrun/run_worker.py (+26/-7)
test_runner/tstrun/testbed.py (+4/-1)
Changed in ubuntu-ci-services-itself: | |
milestone: | none → phase-0 |
Changed in ubuntu-ci-services-itself: | |
status: | Confirmed → Fix Committed |
Changed in ubuntu-ci-services-itself: | |
status: | Fix Committed → Invalid |
status: | Invalid → Fix Released |
Changed in uci-engine: | |
assignee: | nobody → Vincent Ladeuil (vila) |
importance: | Undecided → Critical |
milestone: | none → phase-0 |
status: | New → Fix Released |
To post a comment you must log in.
syslog will help for bug #1290716