From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: test: 'seen set from rename' potentially racy
Date: Thu, 4 Nov 2021 18:51:49 +0000 [thread overview]
Message-ID: <20211104185149.GA9220@dcvr> (raw)
In-Reply-To: <20211104134327.zrf5jijfz7dsvb7l@meerkat.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> Hello:
>
> I was having some trouble using "make check" on the Fedora build system:
>
> # Failed test 'seen set from rename'
> # at t/lei-watch.t line 61.
> # '/tmp/pi-lei-watch-11080-FYz2/lei-daemon/md2/cur/9bf1002c49eb075df47247b74d69bcd555e23422=99:2,'
> # doesn't match '(?^:S\z)'
> # [
> # '/tmp/pi-lei-watch-11080-FYz2/lei-daemon/md2/cur/9bf1002c49eb075df47247b74d69bcd555e23422=99:2,'
> # ]
>
> This wasn't happening in my own chroot builds, so I'm suspecting that the
> faster system on the Fedora build infra side is causing this failure,
> therefore perhaps some kind of race condition.
Hmm, I thought I fixed it... Does increasing the tick sleep time help?
diff --git a/t/lei-watch.t b/t/lei-watch.t
index 9158571c..8126b707 100644
--- a/t/lei-watch.t
+++ b/t/lei-watch.t
@@ -49,13 +49,13 @@ test_lei(sub {
lei_ok 'ls-watch';
like($lei_out, qr/^\Qmaildir:$md\E$/sm, 'maildir shown');
lei_ok qw(q mid:testmessage@example.com -o), $md, '-I', "$ro_home/t1";
my @f = glob("$md/cur/*:2,");
is(scalar(@f), 1, 'got populated maildir with one result');
rename($f[0], "$f[0]S") or xbail "rename $!"; # set (S)een
- tick($have_fast_inotify ? 0.1 : 2.1); # always needed for 1 CPU systems
+ tick($have_fast_inotify ? 1 : 5); # always needed for 1 CPU systems
lei_ok qw(note-event done); # flushes immediately (instead of 5s)
lei_ok qw(q mid:testmessage@example.com -o), $md2, '-I', "$ro_home/t1";
my @f2 = glob("$md2/*/*");
is(scalar(@f2), 1, 'got one result');
like($f2[0], qr/S\z/, 'seen set from rename') or diag explain(\@f2);
Maybe 1s is too much and 0.2s is enough.
> https://download.copr.fedorainfracloud.org/results/icon/b4/fedora-35-x86_64/02928611-public-inbox/build.log.gz
"prove --state=save -bvw -j3", so 2 cores? Any idea what
CONFIG_HZ is on that system?
> Switching to "make test" seems to help, which is what I've done for now.
OK, so it could be load related. There could probably be a way
to "subscribe" for updates to lei-daemon so sleeping wouldn't be
necessary. I'll see abouit it next week, got some other stuff
to take care of...
next prev parent reply other threads:[~2021-11-04 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 13:43 test: 'seen set from rename' potentially racy Konstantin Ryabitsev
2021-11-04 18:51 ` Eric Wong [this message]
2022-02-13 21:01 ` Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211104185149.GA9220@dcvr \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.org \
--cc=meta@public-inbox.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).