From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: io-uring@vger.kernel.org
Subject: Re: [RESEND PATCH liburing 2/2] test/iopoll: Fix clang CI build failure
Date: Mon, 31 Aug 2026 20:18:21 -0300 [thread overview]
Message-ID: <87a4q17ubm.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <626ca0d4-804f-43a0-bdce-d09f366b482e@kernel.dk>
Jens Axboe <axboe@kernel.dk> writes:
> On 8/31/26 9:52 AM, Gabriel Krisman Bertazi wrote:
>> Clang CI builds in liburing repo do -Werror,-Wunused-but-set-global when
>> building with clang. commit c5eead26 ("test/iopoll: fix over-eager
>> no_hybrid check") left a lingering variable that was not used, and clang
>> got smart enough to find for it, causing the build to fail for every
>> commit ever since.
>>
>> https://github.com/axboe/liburing/actions/runs/30404555586/job/90427017716
>> https://github.com/axboe/liburing/actions/runs/30404555586/job/90427017742
>
> What's this against? Doesn't apply.
Ah, it was fixed by Ammar in parallel through a github PR:
ca274ec7 ("test: Remove unused global variables found by clang-23")
Thanks for merging the rest.
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2026-08-31 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 15:52 [RESEND PATCH liburing 0/2] couple of fixes to tests Gabriel Krisman Bertazi
2026-08-31 15:52 ` [RESEND PATCH liburing 1/2] test/iowait.t: Skip if system is not quiesced for too long Gabriel Krisman Bertazi
2026-08-31 15:52 ` [RESEND PATCH liburing 2/2] test/iopoll: Fix clang CI build failure Gabriel Krisman Bertazi
2026-08-31 23:00 ` Jens Axboe
2026-08-31 23:18 ` Gabriel Krisman Bertazi [this message]
2026-08-31 23:00 ` (subset) [RESEND PATCH liburing 0/2] couple of fixes to tests Jens Axboe
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=87a4q17ubm.fsf@mailhost.krisman.be \
--to=krisman@suse.de \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.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