stdout from subprocesses missing from output.txt
Bug #1127288 reported by
vishal
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
LAVA Dispatcher |
Fix Released
|
Critical
|
Antonio Terceiro |
Bug Description
Due to the recent changes in the way output is handled/shown in the scheduler, output from subprocesses no longer shows up in the "complete log" view of the scheduler.
Original description:
stdout logs are not getting printed in recent changes. It makes impossible to debug the issues. The logs were getting printed in jobs till Jan 28th and have stopped from jobs around feb 1. May be it came as part of 13.01 release.
Here is the job where logs are printed:
https:/
Here is a job after few days where logs are not getting printed:
https:/
Related branches
lp:~mwhudson/lava-dispatcher/subprocess-output
- Antonio Terceiro: Approve
-
Diff: 443 lines (+70/-62)9 files modifiedlava_dispatcher/actions/lava_android_test.py (+4/-5)
lava_dispatcher/client/lmc_utils.py (+7/-7)
lava_dispatcher/context.py (+27/-1)
lava_dispatcher/device/fastmodel.py (+5/-10)
lava_dispatcher/device/master.py (+3/-3)
lava_dispatcher/device/nexus.py (+6/-13)
lava_dispatcher/device/qemu.py (+1/-5)
lava_dispatcher/device/sdmux.py (+9/-11)
lava_dispatcher/utils.py (+8/-7)
lp:~nick-schutt/lava-dispatcher/nick-1130814
- Linaro Validation Team: Pending requested
-
Diff: 440 lines (+67/-62)9 files modifiedlava_dispatcher/actions/lava_android_test.py (+4/-5)
lava_dispatcher/client/lmc_utils.py (+7/-7)
lava_dispatcher/context.py (+24/-1)
lava_dispatcher/device/fastmodel.py (+5/-10)
lava_dispatcher/device/master.py (+3/-3)
lava_dispatcher/device/nexus.py (+6/-13)
lava_dispatcher/device/qemu.py (+1/-5)
lava_dispatcher/device/sdmux.py (+9/-11)
lava_dispatcher/utils.py (+8/-7)
summary: |
- stdout logs are not getting printed + stdout from subprocesses missing from output.txt |
Changed in lava-dispatcher: | |
status: | Incomplete → Triaged |
description: | updated |
Changed in lava-dispatcher: | |
status: | Triaged → In Progress |
milestone: | none → 2013.02 |
assignee: | nobody → Michael Hudson-Doyle (mwhudson) |
Changed in lava-dispatcher: | |
milestone: | 2013.02 → 2013.03 |
assignee: | Michael Hudson-Doyle (mwhudson) → Antonio Terceiro (terceiro) |
assignee: | Antonio Terceiro (terceiro) → Nicholas Schutt (nick-schutt) |
importance: | Undecided → Critical |
Changed in lava-dispatcher: | |
status: | In Progress → Fix Committed |
status: | Fix Committed → In Progress |
Changed in lava-dispatcher: | |
status: | In Progress → Fix Committed |
Changed in lava-dispatcher: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
As far as I can tell, this isn't a LAVA problem, there is no prompt printed after running "netcfg eth0 dhcp", i.e. it looks like the board hung. Is there something I'm missing?