* [gentoo-dev] CI and be CC'ed in a bug report
@ 2021-05-03 10:07 99% Agostino Sarubbo
0 siblings, 0 replies; 1+ results
From: Agostino Sarubbo @ 2021-05-03 10:07 UTC (permalink / raw
To: gentoo-dev; +Cc: sam, zlogene
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
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2021-05-03 10:07 99% [gentoo-dev] CI and be CC'ed in a bug report Agostino Sarubbo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox