On 01/14/2013 08:32 PM, Michael Hudson-Doyle wrote:
Apologies if this mail is a little incomprehensible. I'm brain dumping
in a hurry :-)
The lava dispatcher currently communicates where the results it has
uploaded to the dashboard have ended up to the scheduler by having an
extra file descriptor open to the scheduler monitor process -- both
stdout and stderr are pretty messy and I didn't want to take the risk of
e.g. a boot message being mis-interpreted as structured data.
As well as being silly and over-engineered, this is implicated in my
debugging of the "jobs don't always exit properly" bug. So let's stop
using it.
What I'd like to do instead is add an --output-dir option to the
dispatcher, pass it from the scheduler, have the scheduler write the
location of the uploaded results to a known location in this output
directory. In fact, I've done this:
http://bazaar.launchpad.net/~mwhudson/lava-dispatcher/output-dir/revision/530
http://bazaar.launchpad.net/~mwhudson/lava-scheduler/use-dispatcher-output-dir/revision/236
Doesn't seem so bad really.
This fixed the immediate problem, but I want to go further: I want to
store more structured log output (filtering boot logs away, for example)
in this output directory and gradually teach the scheduler web bits how
to interpret this structured data.
Thoughts?
It simplifies things and looks better, so I'm a big fan. I have a couple
of minor nitpicks with the actual patches, but that can wait until the
MP's are created if you prefer.
_______________________________________________
linaro-validation mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/linaro-validation
