Re: [OE-core] [PATCH 2/7] selftest/sstatetests: fix up printdiff test to match rework of printdiff logic

2024-01-02 Thread Alexander Kanavin
I just sent a patch for this: "lib/sstatesig/find_siginfo: raise an error instead of returning None when obtaining mtime" It will not fix the issue, but it will get better diagnostics (the error can be suppressed, but it's something that shouldn't be happening, so I want to see what is really the

Re: [OE-core] [PATCH 2/7] selftest/sstatetests: fix up printdiff test to match rework of printdiff logic

2024-01-01 Thread Alexander Kanavin
RP has reported the same issue elsewhere: https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/6254/steps/14/logs/stdio File "/home/pokybuild/yocto-worker/oe-selftest-ubuntu/build/bitbake/lib/bb/runqueue.py", line 1799, in

Re: [OE-core] [PATCH 2/7] selftest/sstatetests: fix up printdiff test to match rework of printdiff logic

2024-01-01 Thread Alexandre Belloni via lists.openembedded.org
Hello, I've been carrying the series for a while without any issue but got this yesterday: https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/6262/steps/14/logs/stdio On 18/12/2023 09:43:58+0100, Alexander Kanavin wrote: > Other than the formatting changes, there are two

[OE-core] [PATCH 2/7] selftest/sstatetests: fix up printdiff test to match rework of printdiff logic

2023-12-18 Thread Alexander Kanavin
Other than the formatting changes, there are two functional ones: - use perlcross instead of quilt, as quilt is special in the sense of being excluded from task hash calculcations. perlcross is a full participant. - run the full test (local + sstate) for gcc do_preconfiure change as the