public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Agostino Sarubbo <ago@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: sam@gentoo.org, zlogene <zlogene@gentoo.org>
Subject: [gentoo-dev] CI and be CC'ed in a bug report
Date: Mon, 03 May 2021 12:07:01 +0200	[thread overview]
Message-ID: <1858564.PYKUYFuaPT@spectre> (raw)

Hello,

I've noticed that it's been in vogue lately say "as you were asked many times" 
when there is something to say.

Well, this often (always?) happens without a reference but I don't care.


As asked by sam, CI should CC people that are breaking stuff with their 
commits, see:
https://cutt.ly/Wbx08SQ

However since there are message like this: https://cutt.ly/vbx2qv2 I'm giving 
a public explanation about what is happening:

1) Compilation of package 'A' works as expected
2) A new major change is introduced (gcc/glibc/binutils)
3) The CI system always runs an updated system, then it uses latest ~arch 
versions
4) Someone touches the package by introducing a simple comment in the ebuild
5) Since the ebuild was touched, the CI tries to compile it
6) Package 'A' fails to compile because of GCC-11 and not because of the 
comment added into the ebuild.

This happens mostly when the entire tree has not been 'tinderboxed' with the 
new major change.

So Mikle, I have nothing to fix.


For the record, if you want to request a change, you should send at least an 
email or open a ticket.

Send a message somewhere (mostly IRC) and say "as you were asked many times" 
just seems to be unproductive (or unprofessional, it depends on the point of 
view)

As a side note, as written before and reminder:
who does not want to receive email/reports from tinderbox and ci may request 
to be in the exclusion list.


Agostino




                 reply	other threads:[~2021-05-03 10:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1858564.PYKUYFuaPT@spectre \
    --to=ago@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=sam@gentoo.org \
    --cc=zlogene@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