From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Ricardo Salveti" <ricardo.salveti@oss.qualcomm.com>
Cc: <bitbake-devel@lists.openembedded.org>, <jose.quaresma@oss.qualcomm.com>
Subject: Re: [bitbake-devel] [PATCH] fetch/wget: rename the partial download on checksum mismatch
Date: Thu, 08 Oct 2026 16:41:31 +0200 [thread overview]
Message-ID: <DLZJAED98DO0.J98TMY81UG2C@bootlin.com> (raw)
In-Reply-To: <CAA_5yot9BGhTmHH1v+NJicxrdpRM9+nkbryESmG5V18GW1+vzQ@mail.gmail.com>
On Thu Oct 8, 2026 at 4:15 PM CEST, Ricardo Salveti wrote:
> Hi,
>
> On Thu, Oct 8, 2026 at 8:59 AM Mathieu Dubois-Briand
> <mathieu.dubois-briand@bootlin.com> wrote:
>>
>> On Tue Sep 29, 2026 at 3:28 AM CEST, Ricardo Salveti via lists.openembedded.org wrote:
>> > The wget fetcher downloads into a .tmp file which is resumed with
>> > --continue and is shared with the mirrors of the same file. When it
>> > fails checksum verification it is left in place, so MIRRORS reuse the
>> > bad file instead of downloading their own copy and, without a mirror,
>> > every retry fails the same way until it is removed by hand. Rename it
>> > with rename_bad_checksum(), as done for any other file with a bad
>> > checksum, so it can be inspected and the next attempt starts from
>> > scratch. Mirror downloads skip this check and are still handled by the
>> > existing code once moved into place.
>> >
>> > Seen with parallel CI runners sharing DL_DIR on Amazon FSx for OpenZFS
>> > mounted over NFSv4.2. What corrupts the file there is not addressed,
>> > only the recovery on retry. Tested with the new tests, which fail
>> > without the fix.
>> >
>> > AI-Generated: Uses Claude Code (Claude Fable 5.1)
>> > Signed-off-by: Ricardo Salveti <ricardo.salveti@oss.qualcomm.com>
>> > ---
>>
>> Hi Ricardo,
>>
>> I suspect this patch is responsible of intermittent failures we can see
>> during test_wget_corrupt_partial_download selftest, only on Fedora
>> workers.
>>
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=16445
>>
>> Do you have any clue about what might be wrong here?
>
> Should be fixed with
> https://patchwork.yoctoproject.org/project/bitbake/patch/20261006213334.3360919-1-ricardo.salveti@oss.qualcomm.com/,
> mind giving it a try?
>
> Thanks,
>
> Ricardo
Sorry, I thought it was still failing, but this is something else. I'll
keep you updated.
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-10-13 17:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 1:28 [PATCH] fetch/wget: rename the partial download on checksum mismatch Ricardo Salveti
2026-09-29 16:48 ` [bitbake-devel] " Alexander Kanavin
2026-09-29 23:01 ` Ricardo Salveti
2026-10-02 9:06 ` Richard Purdie
[not found] ` <18DAAB270E5DB286.1715499@lists.openembedded.org>
2026-10-02 9:20 ` Richard Purdie
2026-10-06 21:30 ` Ricardo Salveti
2026-10-06 21:33 ` [PATCH] tests/fetch: don't rely on wget --continue in the corrupt partial test Ricardo Salveti
2026-10-06 22:50 ` [bitbake-devel] " Yoann Congal
2026-10-08 14:07 ` Ricardo Salveti
2026-10-08 14:21 ` Yoann Congal
2026-10-08 6:59 ` [bitbake-devel] [PATCH] fetch/wget: rename the partial download on checksum mismatch Mathieu Dubois-Briand
2026-10-08 14:15 ` Ricardo Salveti
2026-10-08 14:41 ` Mathieu Dubois-Briand [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=DLZJAED98DO0.J98TMY81UG2C@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=jose.quaresma@oss.qualcomm.com \
--cc=ricardo.salveti@oss.qualcomm.com \
/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.