collect logs and warnings/errors count per target
<khilman> terceiro: have you thought much about how to seprate warnings/errors from the different targets?
<khilman> for that matter, is tuxmake doing any parsing/counting of errors/warnings already? I haven't noticed
that come to think of it.
<khilman> ah, I see errors/warnings counts in the metadata.json, but there's overall "results", but would be ideal to
have those per-target
<terceiro> khilman: that didn't occur to me yet, but it's a good idea
<terceiro> at the moment there is only a single log and that's what is parsed to get warnings/errors
<terceiro> but doing it per-target makes more sense I guess
<khilman> terceiro: as background, we were discussing today on how to do this kind of thing for kernelci builds, because
existing kselftest builds are causing some noise in the the "normal" kernel build logs. since they're all
collected together
<terceiro> right
<khilman> e.g. you see obvious build errors that are actually from kselftest, but then a kernel build PASS, which ends up
to be a bit confusing, so keeping them separate in the underlying JSON/db would be helpful