From: Fio Test Bot <fiotestbot@gmail.com>
To: fio@vger.kernel.org
Subject: Re: [PATCH 00/11] verify pattern interval
Date: Thu, 8 May 2025 20:54:16 -0400 [thread overview]
Message-ID: <41222b13-43d1-4d5a-8803-66fbd265e575@gmail.com> (raw)
In-Reply-To: <174673377441.2581.14259152939735507019@fv-az1694-607>
On 5/8/25 3:49 PM, fiotestbot@gmail.com wrote:
>
> The result of fio's continuous integration tests was: failure
>
> For more details see https://github.com/fiotestbot/fio/actions/runs/14914258938
Hoisted by my own petard.
There was one test failure with t/jobs/t0010:
https://github.com/axboe/fio/blob/master/t/jobs/t0010-b7aae4ba.fio
This job is a simple io_submit_mode=offload test:
# Expected result: fio runs and completes the job
# Buggy result: fio segfaults
#
[test]
ioengine=null
size=10g
io_submit_mode=offload
iodepth=16
My changes do not touch this code. I looked at Actions runs in the main
repository and found no similar failures in the 90 days of available
logs. I did find two failures in Actions logs on my fork:
https://github.com/vincentkfu/fio/actions/runs/14414832872/job/40429681779
https://github.com/vincentkfu/fio/actions/runs/13680647374/job/38251879040
I re-ran the test suite on the failed platform for my patch series and
it passed:
https://github.com/fiotestbot/fio/actions/runs/14914258938
So I am comfortable that my patches are not responsible for this failure.
Vincent
next prev parent reply other threads:[~2025-05-09 0:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 18:58 [PATCH 00/11] verify pattern interval Vincent Fu
2025-05-08 18:58 ` [PATCH 01/11] verify: add verify mode for a pattern with header Vincent Fu
2025-05-08 18:58 ` [PATCH 02/11] verify: fix verify_offset when used with pattern_hdr Vincent Fu
2025-05-08 18:58 ` [PATCH 03/11] verify: make verify_pattern=%o thread safe Vincent Fu
2025-05-08 18:58 ` [PATCH 04/11] verify: omit verify type mismatch error message for pattern verify Vincent Fu
2025-05-08 18:58 ` [PATCH 05/11] t/fiotestcommon: lengthen timeout for longer tests Vincent Fu
2025-05-08 18:58 ` [PATCH 06/11] ci: for nightly verify tests use all checksum methods Vincent Fu
2025-05-08 18:58 ` [PATCH 07/11] ci: don't skip verify tests when triggered manually Vincent Fu
2025-05-08 18:58 ` [PATCH 08/11] verify: add verify_pattern_interval option Vincent Fu
2025-05-08 18:58 ` [PATCH 09/11] t/verify: test cases for running pattern and pattern_hdr Vincent Fu
2025-05-08 18:58 ` [PATCH 10/11] t/verify: Windows --output work-around Vincent Fu
2025-05-08 18:58 ` [PATCH 11/11] t/verify: add tests to exercise verify_pattern_interval Vincent Fu
2025-05-08 19:49 ` [PATCH 00/11] verify pattern interval fiotestbot
2025-05-09 0:54 ` Fio Test Bot [this message]
2025-05-16 18:08 ` Fio Test Bot
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=41222b13-43d1-4d5a-8803-66fbd265e575@gmail.com \
--to=fiotestbot@gmail.com \
--cc=fio@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