From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 644FAC4706C for ; Fri, 12 Jan 2024 19:39:05 +0000 (UTC) Received: from mail-yw1-f181.google.com (mail-yw1-f181.google.com [209.85.128.181]) by mx.groups.io with SMTP id smtpd.web10.1443.1705088344333929939 for ; Fri, 12 Jan 2024 11:39:04 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20230601 header.b=Rxp6nQsN; spf=pass (domain: gmail.com, ip: 209.85.128.181, mailfrom: ticotimo@gmail.com) Received: by mail-yw1-f181.google.com with SMTP id 00721157ae682-5f07f9d57b9so68492297b3.1 for ; Fri, 12 Jan 2024 11:39:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705088343; x=1705693143; darn=lists.yoctoproject.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=p5DGjJPRoAu3Z4yJwYP25ppZv18YIU6gyCfoqrnOS5k=; b=Rxp6nQsN3OgI4A6p+17dKDwtVewI1imO2CBZqdQXKbpMHv6VfR0fWStZVayFSSY0fx UR2qPckeDsP8c6nvA33Wgktgd3fw1coaR39cz9LPyL066lgt5r3SM+Od0MQvcoyISV/8 ZL4uWbHlfMnkyXGEDKK7YCFbfmlJCxyDo1aJWrxPoNNvdpGt5hHTK+E8DaIBrLRZcsJ4 M82SHc/m+MJ0b7WeU7zPZYv14JQx9K/3bAz35w/vwYTZPU1Cx+LflF5W1kdeIbr0cxAB 2qcjpeYFz1OFfAQxNuf8ycL0H8uYuUeEBMBxN8zPPJmvsJJXDi/XpdgxKDs0ugi6dMrn HLqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705088343; x=1705693143; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=p5DGjJPRoAu3Z4yJwYP25ppZv18YIU6gyCfoqrnOS5k=; b=I0LTa0RKFg3Tu9Bh+xy8G69MqXuoWCMwTGqPNBux9OdZINsx+Fi0sSXv5fDGew54He ICDcqZZQ0HWVnZeXN0NMBCEVRIK8xz4gtPjFB0kq+dOoZQIwAmKW75tAuoWlubiiIB1g +FGj0PQO4Rpfjvae0w3KrnPiletIwj37TGA4JfDMnvM7dS0GdNFZ4cB+lMp6K0FTG77v aTPrALICsNA6sI0YoHTLms+PJ46CWgiFfX1sVvbc/ZO9P2G5hQRx77623oGn7wiSwcwS gMsj9Khy+UGP6KnFePGOcmxGLac3ae+qNVPxNl6YoCY3is3icJ3dFCtFXXT2/qpo11z0 kn3g== X-Gm-Message-State: AOJu0YyWmBk5AHydnL/xtuGf+389eHTT25zaC+BsFXzZrAYVbPxj2rtB bnV4pEBVc0Fq8K/47nxGMv9cUeIsK8fuWmBu/tQ= X-Google-Smtp-Source: AGHT+IF+HhI9wXeIFDzwWIZbhNem4+i15ojs4/Q4cSQRgOnTq+RD/H589vCn2nLqtmMF8Bo+5r3Pa1xr/22hapkp5Qw= X-Received: by 2002:a81:4e81:0:b0:5f7:7de:2c4b with SMTP id c123-20020a814e81000000b005f707de2c4bmr1816843ywb.51.1705088343274; Fri, 12 Jan 2024 11:39:03 -0800 (PST) MIME-Version: 1.0 References: <81d4da494bd7b892c906e82caee977ef986b98c3.camel@linuxfoundation.org> In-Reply-To: <81d4da494bd7b892c906e82caee977ef986b98c3.camel@linuxfoundation.org> From: Tim Orling Date: Fri, 12 Jan 2024 11:38:51 -0800 Message-ID: Subject: Re: [Toaster] My notes on importing commandline builds into toaster To: Richard Purdie Cc: Alexander Kanavin , Martin Jansa , Mohammed Raza , bitbake-devel , "toaster@lists.yoctoproject.org" Content-Type: multipart/alternative; boundary="00000000000002fa60060ec4d15d" List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Fri, 12 Jan 2024 19:39:05 -0000 X-Groupsio-URL: https://lists.yoctoproject.org/g/toaster/message/6143 --00000000000002fa60060ec4d15d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Jan 12, 2024 at 7:40=E2=80=AFAM Richard Purdie < richard.purdie@linuxfoundation.org> wrote: > 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.z= st > > 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. > Thank you for capturing this. It will be invaluable in any attempts to improve the features. > > Cheers, > > Richard > > > > > > -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- > Links: You receive all messages sent to this group. > View/Reply Online (#6142): > https://lists.yoctoproject.org/g/toaster/message/6142 > Mute This Topic: https://lists.yoctoproject.org/mt/103684954/924729 > Group Owner: toaster+owner@lists.yoctoproject.org > Unsubscribe: https://lists.yoctoproject.org/g/toaster/unsub [ > ticotimo@gmail.com] > -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D- > > --00000000000002fa60060ec4d15d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, Jan 12, 2024 at 7:40=E2=80=AFAM Richard Purdie <= richard.purdie@linuxf= oundation.org> wrote:
Since we now have to= aster 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.yoctoproje= ct.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 f= or
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<= br> 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/faile= d-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.

Thank you for ca= pturing this. It will be invaluable in any attempts to improve the features= .

Cheers,

Richard





-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
Links: You receive all messages sent to this group.
View/Reply Online (#6142): https://lists.yoctop= roject.org/g/toaster/message/6142
Mute This Topic: https://lists.yoctoproject.org/mt= /103684954/924729
Group Owner: toaster+owner@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/toaster/= unsub [ticotimo= @gmail.com]
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-

--00000000000002fa60060ec4d15d--