All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Reyna, David" <david.reyna@windriver.com>,
	"toaster@lists.yoctoproject.org" <toaster@lists.yoctoproject.org>
Subject: Re: [Toaster] [PATCH] toaster: handle changes to "ImagePkgList" event
Date: Mon, 21 Mar 2022 15:20:55 +0000	[thread overview]
Message-ID: <8896e2e934d56451828bdf83063c4cad1ae2ee02.camel@linuxfoundation.org> (raw)
In-Reply-To: <BY5PR11MB4167E128756A3935EA08C44FEA169@BY5PR11MB4167.namprd11.prod.outlook.com>

On Mon, 2022-03-21 at 00:18 +0000, Reyna, David wrote:
> > I'm seeing builds reach 100% and then just hang in the toaster UI never
> > completing.
> 
> See my recent patch for 14765 (attached).
> 
> I discovered that new race condition with long builds where the end-of-build
> event has the build record success outcome properly set, but that commit never
> makes it in time to the physical database before the build tear-down. It may
> be related to the upgrade to Django 3 (and if so it is the only oddity with
> Tim's Django 3 I have encountered).

I thought I had that applied but I'd messed up and hadn't, it does work fine
with the patch applied.

I've merged the two bitbake changes and the OE-Core change so toaster is looking
much better on master now ready for kirkstone, thanks.!
Cheers,

Richard



      reply	other threads:[~2022-03-21 15:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18 10:43 [PATCH] toaster: handle changes to "ImagePkgList" event David Reyna
2022-03-18 10:49 ` [Toaster] " Richard Purdie
2022-03-18 19:26   ` Reyna, David
2022-03-19 20:02     ` Richard Purdie
2022-03-20  7:14       ` Reyna, David
     [not found]       ` <16DE057272F55985.7848@lists.yoctoproject.org>
2022-03-20 22:37         ` Reyna, David
     [not found]           ` <89bc951abe2d02689688b1c43d7465d5751b489d.camel@linuxfoundation.org>
2022-03-21  0:18             ` Reyna, David
2022-03-21 15:20               ` Richard Purdie [this message]

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=8896e2e934d56451828bdf83063c4cad1ae2ee02.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=david.reyna@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.