All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Guðni Már Gilbert" <gudni.m.g@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] sqlite3: upgrade 3.48.0 -> 3.50.1
Date: Wed, 02 Jul 2025 01:46:57 -0700	[thread overview]
Message-ID: <18523.1751446017821038910@lists.openembedded.org> (raw)
In-Reply-To: <DB1CTEVUVWZP.13OQTLFJG9G9S@bootlin.com>

[-- Attachment #1: Type: text/plain, Size: 392 bytes --]

Thank for taking the time to test this Antonin. I saw this error locally rarely, and usually deleting the entire build folder resolved the problem.

I am not sure how to fix this issue, if anybody has any ideas then I would gladly listen/appreciate it. I'm not very familiar with the underlying Python code that is detecting a broken pipe. I wonder if this is some sort of race condition?

[-- Attachment #2: Type: text/html, Size: 431 bytes --]

  reply	other threads:[~2025-07-02  8:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27 18:12 [PATCH v2] sqlite3: upgrade 3.48.0 -> 3.50.1 Guðni Már Gilbert
2025-07-02  6:26 ` [OE-core] " Antonin Godard
2025-07-02  8:46   ` Guðni Már Gilbert [this message]
2025-07-02  8:49     ` Guðni Már Gilbert
2025-07-02  9:50       ` [OE-core] " Richard Purdie

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=18523.1751446017821038910@lists.openembedded.org \
    --to=gudni.m.g@gmail.com \
    --cc=openembedded-core@lists.openembedded.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.