At the moment, gentoo-repo-qa-bot will post something like > Pull request CI report > > Report generated at: 2020-03-30 00:17 UTC > Newest commit scanned: bd36beb > Status: white_check_mark good > > Issues already there before the PR (double-check them): > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-admin/ansible > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-admin/consul-template > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-admin/puppet > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-admin/rsyslog > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-admin/system-tools-backends > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-editors/atom > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-emulation/bochs > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-emulation/cloud-init > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-emulation/virtualbox-additions > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-emulation/virtualbox-guest-additions > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-emulation/virtualbox-modules > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-i18n/tomoe > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-misc/cbrpager > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-misc/ignuit > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-office/gnucash > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-office/libreoffice-l10n > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-shells/hstr > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-text/glosung > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#app-text/jo > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-cpp/tbb > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-db/etcd > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-db/mongodb > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-db/mysql-workbench > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-db/pgagent > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-dotnet/gnome-keyring-sharp > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-embedded/gnome-avrdude > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-java/swt > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-lang/lisaac > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-lang/qu-prolog > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-lang/rust > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-libs/gjs > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-libs/glib > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-libs/iniparser > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-perl/gnome2-perl > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-perl/gnome2-vfs-perl > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/Numdifftools > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/autobahn > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/backports-functools-lru-cache > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/celery > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/contextlib2 > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/deprecation > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/docker-py > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/ecdsa > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/falcon > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/flask-gravatar > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/flask-htmlmin > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/flask-security > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/fs > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/funcsigs > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/gconf-python > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/genson > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/gnome-vfs-python > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/google-api-python-client > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/google-apitools > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/kafka-python > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/kombu > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/libbonobo-python > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/libgnome-python > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/libgnomecanvas-python > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/linecache2 > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/locustio > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/mock > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/pydot-ng > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/pygtk > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/pymssql > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/pyorbit > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/python-daemon > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/python-xmp-toolkit > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/pyu2f > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/raet > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/reflink > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/rsa > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/schedule > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/testtools > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/ws4py > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-python/zipp > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-util/electron > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-util/jenkins-bin > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#dev-vcs/subversion > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#games-board/gnono > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#games-board/grhino > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#games-board/gtkboard > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#games-board/mt_gtk_client > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#games-board/pioneers > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#games-board/sirius > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#games-board/teg > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#games-puzzle/gtetrinet > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#games-puzzle/skoosh > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#gnome-base/gdm > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#gnome-base/gnome-session > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#gnome-base/libbonobo > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#gnome-base/libbonoboui > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#gnome-base/libgnome > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#gnome-base/libgnome-keyring > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#gnome-base/libgnomeui > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#gnome-extra/cinnamon > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#gnome-extra/gnome-commander > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#mail-client/claws-mail > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#mail-client/mail-notification > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#mail-client/thunderbird > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#mail-mta/nullmailer > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#mate-extra/mate-power-manager > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#media-gfx/darktable > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#media-gfx/inkscape > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#media-libs/cogl > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#media-libs/libgpod > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#media-libs/lilv > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#media-libs/mlt > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#media-libs/pymemphis > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#media-libs/tremor > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#media-sound/grip > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#media-sound/jack-rack > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#media-tv/kodi > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#media-video/unifi-video > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-analyzer/etherape > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-analyzer/ntopng > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-analyzer/wireshark > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-analyzer/zabbix > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-dns/bind > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-dns/unbound > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-ftp/lftp > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-im/teams > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-misc/grdesktop > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-misc/gwget > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-misc/lldpd > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-misc/openssh > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-misc/rabbitmq-server > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-misc/youtube-dl > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-nds/openldap > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-nntp/pan > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-p2p/fms > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-p2p/retroshare > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-proxy/dante > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-proxy/haproxy > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-voip/telepathy-haze > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-vpn/networkmanager-openvpn > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-wireless/kismet > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#net-wireless/urh > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#sci-biology/foldingathome > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#sci-electronics/linsmith > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#sci-libs/ceres-solver > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#sci-libs/eccodes > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#sci-libs/fftw > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#sci-libs/openblas > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#sci-libs/spqr > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#sci-libs/suitesparse > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#sci-libs/tensorflow > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#sci-libs/umfpack > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#sci-physics/clhep > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#sci-physics/geant-data > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#sys-apps/agedu > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#sys-apps/modutils > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#sys-devel/distcc > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#sys-fs/lvm2 > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#sys-kernel/linux-firmware > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#sys-power/nut > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#www-apps/cgit > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#www-apps/jekyll > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#www-apps/netbox > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#www-apps/trac > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#www-client/firefox > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#www-client/seamonkey > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#www-client/seamonkey-bin > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#www-servers/nginx > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#www-servers/tomcat > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#www-servers/tornado > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#x11-misc/xnee > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html#x11-plugins/pidgin-opensteamworks Please change this to just > Pull request CI report > > Report generated at: 2020-03-30 00:17 UTC > Newest commit scanned: bd36beb > Status: white_check_mark good > > Issues already there before the PR (double-check them): > https://qa-reports.gentoo.org/output/gentoo-ci/de5e88d/output.html REASON: Because the links contain the package name, search at Github has actually become broken. You can't search i.e. for "firefox" anymore because package name is getting mentioned in more than 150 currently unrelated opened issues as qa-report link.
The patch for repo-mirror-ci repo should be trivial.
Pushed a fix, it should deploy shortly.
Still happening: > Pull request CI report > Report generated at: 2020-04-21 15:05 UTC > Newest commit scanned: 83d5244 > Status: broken > > New issues caused by PR: > https://qa-reports.gentoo.org/output/gentoo-ci/d37e40e/output.html#dev-perl/JavaScript-SpiderMonkey > https://qa-reports.gentoo.org/output/gentoo-ci/d37e40e/output.html#gnome-extra/cjs > https://qa-reports.gentoo.org/output/gentoo-ci/d37e40e/output.html#media-gfx/freewrl > https://qa-reports.gentoo.org/output/gentoo-ci/d37e40e/output.html#media-libs/avidemux-plugins > https://qa-reports.gentoo.org/output/gentoo-ci/d37e40e/output.html#media-libs/coin > https://qa-reports.gentoo.org/output/gentoo-ci/d37e40e/output.html#media-video/gxine > https://qa-reports.gentoo.org/output/gentoo-ci/d37e40e/output.html#net-misc/plowshare > https://qa-reports.gentoo.org/output/gentoo-ci/d37e40e/output.html#www-client/elinks > https://qa-reports.gentoo.org/output/gentoo-ci/d37e40e/output.html#www-client/netsurf > https://qa-reports.gentoo.org/output/gentoo-ci/d37e40e/output.html#x11-plugins/hexchat-javascript > > There are existing issues already. Please look into the report to make sure none of them affect the packages in question: > https://qa-reports.gentoo.org/output/gentoo-ci/d37e40e/output.html > As said I would expect that CI bot will just post link to https://qa-reports.gentoo.org/output/gentoo-ci/d37e40e/output.html and nothing else.
That would be counter-productive. New issues are important information.
Why? Have you actually understood the original issue? Don't get me wrong but now I am curious what you have changed at all: The problem is that posting package names in issues will make search unusable. I.e. I don't care that PR X broke package Y. It will get fixed before X will get merged. So when I search for Y because I want to list all issues (PRs) affecting that package directly, I only want that those packages will show up and not an unrelated PR which just broke Y but is WIP.
The problem is that if PR X breaks package Y, then we need to tell user that it breaks package Y, and not expect him to figure which of 100 unresolved issues is his. What I have changed is I've removed all the potentially irrelevant data I could. It was considerably problematic because of poor quality of ::gentoo meant that a lot of packages kept repeating everywhere. That is a problem (well, more like a symptom of a deeper problem) and I've did the best to resolve it. I don't see a better solution here. Unless your idea is to ban anyone from ever mentioning your package name because you have a broken workflow and can't stand having to look at a PR once in a while that may actually be relevant to it (well, it is relevant if it breaks it, isn't it?).
(In reply to Michał Górny from comment #6) > The problem is that if PR X breaks package Y, then we need to tell user that > it breaks package Y, and not expect him to figure which of 100 unresolved > issues is his. > > What I have changed is I've removed all the potentially irrelevant data I > could. It was considerably problematic because of poor quality of ::gentoo > meant that a lot of packages kept repeating everywhere. That is a problem > (well, more like a symptom of a deeper problem) and I've did the best to > resolve it. > > I don't see a better solution here. Unless your idea is to ban anyone from > ever mentioning your package name because you have a broken workflow and > can't stand having to look at a PR once in a while that may actually be > relevant to it (well, it is relevant if it breaks it, isn't it?). I don't suppose its possible for the bot to auto-delete these comments periodically? Or alternatively, try figure out how to make data turn up in the "checks" list so it serves as a "maybe blocks merge" reason, and the content also doesn't show up as being "bug content" and doesn't show in searches.
Am I missing the problem? Why not just > Pull request CI report > Report generated at: 2020-04-21 15:05 UTC > Newest commit scanned: 83d5244 > Status: broken > > This PR is causing new issues. Please review the following report: > https://qa-reports.gentoo.org/output/gentoo-ci/d37e40e/output.html > > There are existing issues already. Please look into the report to make sure none of them affect the packages in question: > https://qa-reports.gentoo.org/output/gentoo-ci/d37e40e/output.html The last paragraph regarding "existing issues" is of course optional. The message is clear: It's telling that this PR broke something. It's telling everyone where to find this information. Problem solved.
(In reply to Thomas Deutschmann from comment #8) > Am I missing the problem? Why not just > > > Pull request CI report > > Report generated at: 2020-04-21 15:05 UTC > > Newest commit scanned: 83d5244 > > Status: broken > > > > This PR is causing new issues. Please review the following report: > > https://qa-reports.gentoo.org/output/gentoo-ci/d37e40e/output.html > > > > There are existing issues already. Please look into the report to make sure none of them affect the packages in question: > > https://qa-reports.gentoo.org/output/gentoo-ci/d37e40e/output.html > > The last paragraph regarding "existing issues" is of course optional. > > The message is clear: It's telling that this PR broke something. It's > telling everyone where to find this information. Problem solved. The pages linked however do not have "the information relating to the changes", they only have the information related to "everything", so if your changes broke something, you are now much less likely to find it. There should at *least* be a shortlist of "recently added/fixed" for people to see, at the top of that file, before such a proposed wording makes sense.
Thanks, now I understand. Wondering if we can strip the report so that it will only contain the new problems caused by this PR and remove everything else. If we can already identify new issues, this should be possible.
(In reply to Michał Górny from comment #4) > That would be counter-productive. New issues are important information. Though, yes, I do agree. Its good the "existing" issues are gone. But the "we're mostly sure you broke this" being there is *good*, because it helps you search for things that probably broke something you maintain.
(In reply to Thomas Deutschmann from comment #10) > Thanks, now I understand. > > Wondering if we can strip the report so that it will only contain the new > problems caused by this PR and remove everything else. If we can already > identify new issues, this should be possible. If you look at the copy-pasta'd report you gave of "still doing it" https://bugs.gentoo.org/715436#c3 , you'll see its only listing "you broke this" and the "already broken" section, is as desired, gone. Can you link the PR it happened on so we can verify that there isn't instead some bug with it detecting "new" cases that aren't "new"?
> Can you link the PR it happened on so we can verify that there isn't instead > some bug with it detecting "new" cases that aren't "new"? Scratch that, found it myself: https://github.com/gentoo/gentoo/pull/15454 Looks like each and every mentioned link does relate to the change herein. So I'm happy overall with the change myself, it will improve the problem substantially and we can see how it goes. Though I would like some sort of garbage collection if we can work out how, and if we can have sensible rules about what is no longer relevant.
Old comments are removed as new are added. So obviously once you fix all the issues, there will be no package names to complain of. No, we don't detect 'new issues'. We merely detect 'packages that hadn't had any issues before'.
(In reply to Michał Górny from comment #14) > Old comments are removed as new are added. So obviously once you fix all > the issues, there will be no package names to complain of. I'm not sure if this is an example or not of something going wrong, but this PR has multiple QA-Bot responses, and I don't know if its due to the cleanup logic failing, or the posts there pre-dating the fix: https://github.com/gentoo/gentoo/pull/14224
(In reply to Michał Górny from comment #2) > Pushed a fix, it should deploy shortly. The change has been around for years, seems nothing more is actionable here.
