Re: [OE-core] [PATCH v3 0/6] scripts/resulttool/regression: add metadata filtering

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Sun, 2023-02-26 at 16:42 +0100, Alexis Lothoré wrote:
> > I'm hoping we don't have many of these quirks. We have a huge history
> > at this point so it would be sad if the tool can't work with it. From
> > what I've seen so far, we can manage with the code in the regression
> > module itself. I've tried to add some comments.
> > 
> > I wondered what to do with this series since I needed to get M3 built.
> > Since this series was available and mostly usable, it would be better
> > to have a nicer report this time, it is a good test of the code.
> > 
> > In the end I've merged most of it, along with my two tweaks to handle
> > LTP and the bigger ptest results issue. I couldn't take one set of the
> > selftests since they simply don't work. This will give us a useful
> > realworld test of the M3 report.
> 
> Ok, great. For the selftest failing, my bad, adding proper logging was one of
> those "one last change before sending", and obviously I did forget to re-run the
> tests before sending.
> > 
> > I'm working on the assumption you'll send a follow up series with the
> > tests, the oe-core check and some of the other issues I've mentioned in
> > other emails?
> 
> Absolutely. Besides the tests, oecore check and the improvements mentioned in
> this mail thread, the next thing I was keeping in mind is fixing the report
> generation against "master-next" branches you have mentioned a few weeks ago.


FWIW, here is the result from M3 rc1:

https://autobuilder.yocto.io/pub/releases/yocto-4.2_M3.rc1/testresults/testresult-regressions-report.txt

It looks like a couple of runs were mismatched so the ltp issue isn't
quite resolved with my tweak. All in all it is definitely a lot more
readable than it was though so progress :)

Looks like dbus may need the same fix as curl.

Cheers,

Richard