From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>, meta@public-inbox.org
Subject: Re: [PATCH 0/4] test fixes for latest CPAN modules
Date: Fri, 11 May 2018 15:27:47 -0400 [thread overview]
Message-ID: <a396f48f-1e59-cbbc-17fa-53ff9c8c4b2f@linuxfoundation.org> (raw)
In-Reply-To: <20180511192018.6432-1-e@80x24.org>
[-- Attachment #1.1: Type: text/plain, Size: 567 bytes --]
On 05/11/18 15:20, Eric Wong wrote:
> A few test fixes for problems encountered by Konstantin on
> CentOS 7 and some of the latest CPAN modules.
>
> There's still locking problem in in t/v2mirror.t which I
> have not reproduced, yet.
Thanks, Eric!
I can confirm that v2mirror.t is the only test that's still failing now.
If you need help troubleshooting that, I'll be happy to help. Feel free
to jump into #korg on linuxnet (or #kernel.org on freenode).
Best,
--
Konstantin Ryabitsev
Director, IT Infrastructure Security
The Linux Foundation
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2018-05-11 19:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 19:20 [PATCH 0/4] test fixes for latest CPAN modules Eric Wong
2018-05-11 19:20 ` [PATCH 1/4] content_id: workaround quote handling change in Email::* modules Eric Wong
2018-05-11 19:20 ` [PATCH 2/4] convert+compact: fix when running without ~/.public-inbox/config Eric Wong
2018-05-11 19:20 ` [PATCH 3/4] t/v2mda: setup emergency Maildir for test Eric Wong
2018-05-11 19:20 ` [PATCH 4/4] t/search: quiet warning from Encode.pm Eric Wong
2018-05-11 19:27 ` Konstantin Ryabitsev [this message]
2018-05-11 19:38 ` [PATCH 0/4] test fixes for latest CPAN modules Eric Wong
2018-05-11 19:50 ` Konstantin Ryabitsev
2018-05-16 5:12 ` Eric Wong
2018-05-23 21:51 ` Konstantin Ryabitsev
2018-05-24 8:41 ` Eric Wong
2018-05-24 15:15 ` Konstantin Ryabitsev
2018-05-30 11:57 ` Eric Wong
2018-05-30 15:28 ` Konstantin Ryabitsev
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=a396f48f-1e59-cbbc-17fa-53ff9c8c4b2f@linuxfoundation.org \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.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).