From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] Travis fix
Date: Tue, 15 Dec 2020 11:01:54 +0100 [thread overview]
Message-ID: <X9iJkj3ZDWj2NaWi@pevik> (raw)
In-Reply-To: <X9iGKllfr8qYi/yX@pevik>
> Hi,
> you may noticed that our Travis CI testing currently fails on Ubuntu eoan.
> This is because Travis has outdated docker image, which still expect
> eoan-security being on ttp://security.ubuntu.com/ubuntu.
> I'm testing other releases, groovy should be probably best option (LTS => used
> by many people and has security repository so we don't have to bother fixing apt
> repository).
OK, 20.04 LTS focal in Travis is still fails on debconf issue [3]
("debconf: unable to initialize frontend: Dialog") which expect user input.
20.10 groovy is not LTS, but it looks stable. Let's move to it (we'll need to
switch to something else in 7 months, or we can move to another distro).
Kind regards,
Petr
[3] https://travis-ci.org/github/pevik/ltp/jobs/749784860
[4] https://travis-ci.org/github/pevik/ltp/jobs/749784861
> I suppose I fix it during today.
> Travis got pretty slow last few weeks. Maybe it's related to the move from
> travis-ci.org to travis-ci.com. Maybe we should think about other CI if problem
> persists for months. It looks like GitHub Actions supports docker [1].
> Also Gitlab pipelines support it [2], but moving from GitHub would affect more
> things than just CI.
> Kind regards,
> Petr
> [1] https://docs.github.com/en/free-pro-team@latest/actions/creating-actions/creating-a-docker-container-action
> [2] https://docs.gitlab.com/ee/ci/docker/using_docker_images.html
prev parent reply other threads:[~2020-12-15 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 9:47 [LTP] Travis fix Petr Vorel
2020-12-15 10:01 ` Petr Vorel [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=X9iJkj3ZDWj2NaWi@pevik \
--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