From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] travis: Temporarily disable fedora:lastest
Date: Tue, 10 Mar 2020 17:10:01 +0100 [thread overview]
Message-ID: <20200310161001.GA29541@dell5510> (raw)
In-Reply-To: <7c240f66-a65b-4444-b4a2-7569f52e5496@cn.fujitsu.com>
Hi Xu,
> I also test fedora:32 fedora:33 in my ltp fork[1], they are all pass.
> fedora:31 and fedora:latest are failed.
> @Petr, You often modify travis code, if you have some advise, please let me
> know.
Thank you for taking care.
I hoped it'd get fixed soon, but it haven't so far :(
Generally I'd prefer to use rawhide (which is 33, see [2]), but until it's fixed
let's use 32 (upcomming release).
Please send patch today, or I'll commit it myself tonight.
Kind regards,
Petr
> [1]https://github.com/xuyang0410/ltp/commits/settimeofday_builderror
[2] https://hub.docker.com/_/fedora
next prev parent reply other threads:[~2020-03-10 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 10:02 [LTP] [PATCH] travis: Temporarily disable fedora:lastest Yang Xu
2020-03-10 10:10 ` Yang Xu
2020-03-10 16:10 ` Petr Vorel [this message]
2020-03-10 20:45 ` Petr Vorel
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=20200310161001.GA29541@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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