public inbox for gentoo-automated-testing@lists.gentoo.org
 help / color / mirror / Atom feed
From: repomirrorci@gentoo.org
To: <gentoo-automated-testing@lists.gentoo.org>
Cc: <tupone@gentoo.org>
Subject: [gentoo-automated-testing] BROKEN: new breakage found
Date: Mon, 21 Apr 2025 20:15:40 +0000 (UTC)	[thread overview]
Message-ID: <20250421201540.3F8F7218B78@jacamar.gentoo.org> (raw)

Nononononono!

New issues (2):
https://qa-reports.gentoo.org/output/gentoo-ci/515d095/output.html;pkg=dev-ml:findlib
https://qa-reports.gentoo.org/output/gentoo-ci/515d095/output.html;pkg=dev-ml:labltk


New warnings (2):
https://qa-reports.gentoo.org/output/gentoo-ci/515d095/output.html;pkg=dev-ml:findlib
https://qa-reports.gentoo.org/output/gentoo-ci/515d095/output.html;pkg=dev-ml:labltk


Introduced by commits:
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=016b49eb4a5c


Changes since last check:
https://gitweb.gentoo.org/repo/gentoo.git/log/?qt=range&q=bb56d72edbde..016b49eb4a5c


Previous issues still unfixed: 1
Previous warnings still unfixed: 304

Current report:
https://qa-reports.gentoo.org/output/gentoo-ci


--
Gentoo repository CI
https://wiki.gentoo.org/wiki/Project:Repository_mirror_and_CI


             reply	other threads:[~2025-04-21 20:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-21 20:15 repomirrorci [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-26 18:40 [gentoo-automated-testing] BROKEN: new breakage found repomirrorci
2025-01-09  3:30 repomirrorci
2024-11-19 21:29 repomirrorci
2024-04-25 16:44 repomirrorci
2024-03-03 18:21 repomirrorci
2022-07-21 15:18 repomirrorci
2022-02-12 10:41 repomirrorci
2022-01-21 16:09 repomirrorci
2021-07-06 20:28 repomirrorci
2021-04-07 22:41 repomirrorci
2021-03-05 22:51 repomirrorci
2021-01-06 17:12 repomirrorci
2021-01-05 22:20 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=20250421201540.3F8F7218B78@jacamar.gentoo.org \
    --to=repomirrorci@gentoo.org \
    --cc=gentoo-automated-testing@lists.gentoo.org \
    --cc=tupone@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