[Bug 4345] RFE: display QA_LOGS

[bugzilla-daemon at amethyst.openembedded.net]

http://bugs.openembedded.net/show_bug.cgi?id=4345





--- Comment #2 from Rolf 'Laibsch' Leggewie <bugs.openembedded.org at rolf.leggewie.biz>  2008-05-30 18:10:41 ---
excerpt from #oe

(17:16:57) ant|work: Laibsch: referring to oestats, how would you treat the QA
(17:20:49) ant|work: bjour, do you happen to have some script for parsing the
QA logs?
(17:21:28) cyrilRomain: ant|work: no
(17:22:01) ant|work: I think the logs are too long to insepct
(17:22:08) cyrilRomain: ant|work: hmm what are you looking for? publishing QA
result to oestats ?
(17:22:09) ant|work: *inspect
(17:22:25) ant|work: some sort of trigger, like elogs in gentoo
(17:23:05) cyrilRomain: ant|work: heh :)
(17:23:17) ant|work: nobady seems to read them...
(17:23:54) ant|work: I found a couple yesterday building gpsd
(17:24:19) ant|work: with single packages it is easy to see them scroll
(17:24:41) cyrilRomain: ant|work: probably because nobody activate 'QA_LOG =
"1"' in their conf file ?
(17:24:57) ant|work: first reason is this :-D
(17:25:21) cyrilRomain: ant|work: but indeed if you don't look at the scrolling
text, it's easy to miss them :-/
(17:25:33) ant|work: too easy
(17:27:35) cyrilRomain: hm the qa log file is generated only on QA issue
(17:28:05) cyrilRomain: so I'll think about a elog-like script that looks into
temp directories for such qa log files
(17:28:15) Laibsch: ant|work: file an RFE against the tinderbox component to
upload qa logs as well
(17:28:35) ant|work: ok
(17:28:38) cyrilRomain: Laibsch: yeah better even :)
(17:29:08) Laibsch: that will need a bit of work though to add a way to sift
through them, too
(17:29:26) Laibsch: so it will on jeremy having time for this and deeming it
important enough
(17:34:29) cyrilRomain: hmm the problem is that qa log file can be created even
if a package does'nt fail. So maybe a 'Succeed but...' (or a better name) need
to be added in case the package build but with some warnings
(17:35:34) Laibsch: cyrilRomain: LEt's leave that up to jeremy
(17:35:55) Laibsch: My favourite would be a somewhat separate interface to
those logs
(17:36:21) Laibsch: qa logs need not be fatal, but they are only created *if* a
problem is present
(17:36:40) Laibsch: so, IMHO just a long list of qa logs uploaded would be all
that is necessary
(17:39:00) cyrilRomain: Laibsch: you mean separating QA issue from build log?
Hmm I would prefer seing QA issue within the current oestat interface, although
I agree with you a separate interface to see QA issue only is a plus :)
(17:57:49) ant|work: cyrilRomain: a small field of one char would be enough on
screen (green - yellow - red) for oestats
(17:57:53) Laibsch: cyrilRomain: I also meant current oestats interface, but
possibly a separate page
(17:58:11) Laibsch: but let's leave that to Jeremy to consider
(17:59:04) cyrilRomain: ant|work, Laibsch: ok

-- 
Configure bugmail: http://bugs.openembedded.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.