From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] CI: Remove Tumbleweed
Date: Mon, 8 Nov 2021 11:10:45 +0100 [thread overview]
Message-ID: <YYj3pdugWJExKOt+@pevik> (raw)
In-Reply-To: <YYjmO4H3Dsa3oDt/@yuki>
> Hi!
> > Tumbleweed suffers with common timeouts during installing packages.
> > https://github.com/linux-test-project/ltp/runs/4102121237?check_suite_focus=true
> > 2021-11-04T07:12:04.5788989Z (110/114) Installing: pcre2-devel-10.38-1.1.x86_64 [.........done]
> > 2021-11-04T13:10:22.9205133Z (111/114) Installing: clang13-13.0.0-1.2.x86_64 [.
> > 2021-11-04T13:10:22.9326559Z ##[error]The operation was canceled.
> > 2021-11-04T13:10:22.9383287Z Stop and remove container: 3dab012d9d14480da05fc921cd0c0124_opensusetumbleweed_b0089d
> > While keeping restarting after some time usually helps, it's not useful
> > to have CI with false positives thus removed until problem gets
> > permanently fixed. But keep seccomp workaround introduced in 0aa9ebd30
> > for other distros with newest glibc.
> Thinking about it it tumbleweed may not be suited for CI, quite possibly
> new packages gets uploaded to the repository during our CI build which
> would explain these kind of failures.
I reverted Tumbleweed. Yes, probably some kind of out-of-sync repositories. I'm
investigating the issue. I'd have to be convinced it's working (+ testing in my
repo for some time) to try to investigate it again.
There was also problem with Leap repositories, but that's being fixed,
thus I restart jobs.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2021-11-08 10:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 14:31 [LTP] [PATCH 1/1] CI: Remove Tumbleweed Petr Vorel
2021-11-08 8:56 ` Cyril Hrubis
2021-11-08 10:10 ` 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=YYj3pdugWJExKOt+@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@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 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.