Milosz Wasilewski <[email protected]> writes: > On 30 July 2013 13:37, Fathi Boudra <[email protected]> wrote: >> Hi Milosz, >> >> On 30 July 2013 13:49, Milosz Wasilewski <[email protected]> >> wrote: >>> Hi, >>> >>> I made a small modification to lava-scheduler app code that enabled >>> direct linking to line numbers in full log view. The branch was posted >>> to launchpad: >>> http://bazaar.launchpad.net/~mwasilew/lava-scheduler/log_linenumbers/revision/252 >>> >>> The solution isn't perfect as it hardcodes HTML tags into django >>> templatetag, but I wanted minimal changes in the scheduler app code. >>> >>> If you like it I will request the merge :) >> >> I would love to see my feature request implemented: >> https://bugs.launchpad.net/lava-scheduler/+bug/1089800 > > The hard part is to filter the log file to find the 'valuable' output. > If someone from LAVA team has idea how to do it, I can provide the > patch. At the moment there are 3 categories of log lines: log, > console, traceback. LAVA doesn't distinguish between master and > testing images unfortunately. The UI part doesn't seem to be very > difficult. With line numbers you can at least get the URL that points > to the right place in the view.
There is some plumbing in the dispatcher to send output to different places (look at Outputter in context.py). My idea that I never got around to implementing was that instead of just dumping output into a file, it would be some kind of structured output that tagged each line somehow and then the scheduler webapp would interpret this data. Have fun :-) Cheers, mwh _______________________________________________ linaro-validation mailing list [email protected] http://lists.linaro.org/mailman/listinfo/linaro-validation
