toaster.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bitbake-devel <bitbake-devel@lists.openembedded.org>,
	 "toaster@lists.yoctoproject.org"
	<toaster@lists.yoctoproject.org>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
	Martin Jansa <martin.jansa@gmail.com>,
	Mohammed Raza <mohammed.raza@savoirfairelinux.com>
Subject: My notes on importing commandline builds into toaster
Date: Fri, 12 Jan 2024 15:40:42 +0000	[thread overview]
Message-ID: <81d4da494bd7b892c906e82caee977ef986b98c3.camel@linuxfoundation.org> (raw)

Since we now have toaster back and operational and able to import
commandline builds, and we have a usecase where this might be useful, I
thought I'd try it and see what works/doesn't work.

Alex Kanavin mentioned this build has issues:

https://autobuilder.yoctoproject.org/typhoon/#/builders/88/builds/3515

I went in and saved the eventlog:

https://autobuilder.yocto.io/pub/failed-builds-data/20240112030913.json.zst

then I tried to import this into a locally running instance of toaster.
I had to compress/decompress the file as it was large.

Toaster failed locally to import the build with no error given on the
UI. Form the commandline it became clear it was trying to do "mkdir
/home/pokybuild" which clearly isn't my local username. I created the
directory just to move past this.

The build then imported from the commandline. The issues I noticed were
then:

* the build duration was incorrect as it timed the event replay rather
than the original build
* toaster.bbclass wasn't included so the layerconfig is missing
* buildstats info was missing as those weren't present
* log links don't work as I didn't download the logs locally
* the UI doesn't use any of the event timestamp data, just that from
buildstats.
* the cooker log is the replayed cooker log rather than the original
one
* trying to view logs results in tracebacks

Unfortunately toaster doesn't display start/end times of the task and
doesn't let you view the events themselves so it wasn't so useful for
what I wanted to look into. You can get the task ordering if you add
that field to the display (it isn't there by default) which did help a
bit.

I did save the buildstats so I could try a second run with more data:

https://autobuilder.yocto.io/pub/failed-builds-data/stats.tgz

Since I'm documenting this, I may as well save the logs too:

tar -czf stats2.tgz buildstats log work/*/*/*/temp/

https://autobuilder.yocto.io/pub/failed-builds-data/stats2.tgz

Sadly even with that data restored to the correct place, it didn't load
into the system correctly for some reason. I realised this may be
because I didn't have the json eventlog in situ so retried again with
that in the original build path but that didn't improve anything.

I also realised toaster does read the packageinfo task data which I
didn't have present so package information wasn't added.

All in all, an interesting learning experience and we've some work to
to do improve the experience here.

Cheers,

Richard






             reply	other threads:[~2024-01-12 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 15:40 Richard Purdie [this message]
2024-01-12 19:38 ` [Toaster] My notes on importing commandline builds into toaster Tim Orling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=81d4da494bd7b892c906e82caee977ef986b98c3.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=martin.jansa@gmail.com \
    --cc=mohammed.raza@savoirfairelinux.com \
    --cc=toaster@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).