From: Johann Lombardi <johann.lombardi@gmail.com>
To: fio@vger.kernel.org
Subject: Re: pthread_condattr_setclock: Invalid argument
Date: Wed, 17 Mar 2021 14:02:25 +0100 [thread overview]
Message-ID: <20210317130225.GA385833@hub> (raw)
In-Reply-To: <20210316172436.GA380295@hub>
Looking at the logs, it sounds like the pthread_condattr_setclock
configure check now passes on appveyor/msys2 while it used to fail before.
Then pthread_condattr_setclock(CLOCK_MONOTONIC) fails with EINVAL on
this platform. Shall we just force pthread_condattr_setclock to no on
cygwin?
Johann
On Tue, Mar 16, 2021 at 06:24:36PM +0100, Johann Lombardi wrote:
> Hi there,
>
> While rebasing PR #1189 (DFS engine) against latest master, I ran into
> the following CI failure on appveyor/msys2:
>
> make.exe test
> ./fio --minimal --thread --exitall_on_error --runtime=1s --name=nulltest --ioengine=null --rw=randrw --iodepth=2 --norandommap --random_generator=tausworthe64 --size=16T --name=verifyfstest --filename=fiotestfile.tmp --unlink=1 --rw=write --verify=crc32c --verify_state_save=0 --size=16K
> pthread_condattr_setclock: Invalid argument
> pthread_condattr_setclock: Invalid argument
> smalloc: failed adding pool
> Assertion failed: i, file smalloc.c, line 235
> make: *** [Makefile:622: test] Error 3
> Command exited with code 2
>
> https://ci.appveyor.com/project/axboe/fio/builds/38248012/job/kk740eysg1bd1om9
>
> It seems to have been introduced by a recent commit. Any thoughts?
>
> Cheers,
> Johann
prev parent reply other threads:[~2021-03-17 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 17:24 pthread_condattr_setclock: Invalid argument Johann Lombardi
2021-03-17 13:02 ` Johann Lombardi [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=20210317130225.GA385833@hub \
--to=johann.lombardi@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 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.