Re: Autobuilder data collection for intermittent bugs

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

On Thu, 2021-03-25 at 20:00 -0400, Randy MacLeod wrote:
> Thanks for the update Sakib.
> 
> We're planning to follow Steve's example of getting commit access to
> contrib branches of y-a-h and poky and using the YP AB to start custom 
> workers/job initially.  We'll also keep working to duplicate the
> AB behaviour locally. Trevor has asked Konrad for an additional system
> or two since when jobs are running, the web UI is
> painfully slow since it's runnig on the same node right now.
> 
> The one part that Sakib didn't ask about is how to get all the workers
> to do the data collection but that's not urgent since we'll be doing
> some smaller scale experiments tomorrow. If you can point out a helpful
> example, that'd be good.

The easiest is the fact that the workers all share an NFS mount which
is at BASE_SHAREDDIR in config.json. See also WEBPUBLISH_DIR and 
WEBPUBLISH_URL.

We use this to share the reproducible build failures and to share the 
reproducible build failures/diffoscope and test results, e.g.:
OEQA_DEBUGGING_SAVED_OUTPUT=${BASE_SHAREDDIR}/pub/repro-fail/

or perhaps more useful is scripts/collect-results:

"""
#!/bin/bash
WORKDIR=$1
DEST=$2
target=$3

RESFILE=$WORKDIR/tmp/log/oeqa/testresults.json 

if [ -e $RESFILE ]; then
    mkdir -p $DEST/$target
    cp $WORKDIR/tmp/log/oeqa/testresults.json  $DEST/$target/
fi
"""

would let you do something similar and DEST here is specific to a given 
build (date stamp + number). An example would be:

https://autobuilder.yocto.io/pub/non-release/20210129-3/

and then you could create a folder per target. You may need to 
include the worker name in the log.

Cheers,

Richard