On Sun, 2021-04-04 at 15:56 -0400, Randy MacLeod wrote: > > > > > > Rather than messing with the main index which is "production", could you > > just create > > your own for now for testing? :) > > Yes, we've figured all that out, thanks. > We'll send you a patch once we've completed testing on our instance of > the YP AB, early this week. > > > > > FWIW I added tmpfs testing for qemu images into master-next (needs ab-helper > > master-next too) so it will be interesting to compare builds running with > > that > > with the previous build bug trends. > > Any conclusions so far?
I think it helps make the runtime testing more consistent but we are seeing a number of "qemu didn't start in 120s" messages instead. That is probably more desirable than random runtime failures in qemu. We have still seen one valgrind ptest failure with the tmpfs patch too so it doesn't remove all of them. It also won't fix the bitbake server starting timeout problem. I'm leaning to merging it. I did note that in the 120s qemu timeout, we did get a list of other processes that were running: https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/1973 and it shows webkit being built. Would be interesting to correlate against other failures, see what the pattern of running tasks is. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#150215): https://lists.openembedded.org/g/openembedded-core/message/150215 Mute This Topic: https://lists.openembedded.org/mt/81615102/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
