From: repomirrorci@gentoo.org
To: <gentoo-automated-testing@lists.gentoo.org>
Cc: <graaff@gentoo.org>
Subject: [gentoo-automated-testing] BROKEN: repository is slightly less broken!
Date: Sat, 27 Aug 2022 08:03:19 +0000 (UTC) [thread overview]
Message-ID: <20220827080319.BAA8221817B@jacamar.gentoo.org> (raw)
Looks like some of the breakage has been fixed but not all!
Issues fixed since last run (6):
dev-ruby/faraday_middleware
dev-ruby/http
dev-ruby/rubygems
sys-libs/libselinux
virtual/ruby-ssl
virtual/rubygems
Warnings fixed since last run (3):
sys-libs/libselinux
virtual/ruby-ssl
virtual/rubygems
Changes since last check:
https://gitweb.gentoo.org/repo/gentoo.git/log/?qt=range&q=cbc84b26cf7..c288d42797f
Previous issues still unfixed: 8
Previous warnings still unfixed: 289
Current report:
https://qa-reports.gentoo.org/output/gentoo-ci
--
Gentoo repository CI
https://wiki.gentoo.org/wiki/Project:Repository_mirror_and_CI
next reply other threads:[~2022-08-27 23:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 8:03 repomirrorci [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-26 19:09 [gentoo-automated-testing] BROKEN: repository is slightly less broken! repomirrorci
2025-01-09 4:00 repomirrorci
2024-11-19 21:55 repomirrorci
2024-11-18 0:10 repomirrorci
2024-09-05 13:12 repomirrorci
2024-04-25 17:00 repomirrorci
2024-03-03 18:44 repomirrorci
2024-01-07 9:57 repomirrorci
2023-09-23 7:18 repomirrorci
2023-09-11 15:40 repomirrorci
2023-04-07 7:48 repomirrorci
2022-08-27 8:18 repomirrorci
2022-07-21 15:39 repomirrorci
2022-05-13 13:06 repomirrorci
2022-05-13 12:56 repomirrorci
2022-01-21 16:35 repomirrorci
2021-07-06 20:49 repomirrorci
2021-01-31 22:29 repomirrorci
2021-01-06 18:00 repomirrorci
2020-12-31 8:10 repomirrorci
2020-12-22 23:46 repomirrorci
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=20220827080319.BAA8221817B@jacamar.gentoo.org \
--to=repomirrorci@gentoo.org \
--cc=gentoo-automated-testing@lists.gentoo.org \
--cc=graaff@gentoo.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