On Fri, Nov 06, 2020 at 09:39:35AM +0100, Agostino Sarubbo wrote: > On venerdì 6 novembre 2020 09:18:50 CET Joonas Niilola wrote: > > Would it be possible for "someone" to figure it out, if you made your > > tinderbox scripts/code public? ;) Hate to say it, but toralf does pretty > > good job here, so it could be better. > > As stated multiple times, toralf said that the way he's filing bugs expect a > copy-paste action for the summary, this is not possible if you want to do > that > in a more automatic way. >
Is this coming from the same individual who would complain when security bugs were not filled out properly in the summary? So, take a dose of your own medicine here. People prefer usable reports that allow them to solve problems. > > > Yes, I do find your tinderbox work useful most of the time. Thanks! > > However the latest, ehh, show with DISTUTILS_USE_SETUPTOOLS has made > > people do *hundreds* of commits that now apparently need a fixing > > anyway, or reverting back, and that doesn't feel nice. Sure maybe the > > eclass could do some fixing too, but maybe this notice wasn't meant to > > be full-tree scanned (at least _yet_). > > This class of bugs comes from a request. Months ago I also asked if I had > report these bugs during the stabilization and I got a positive feedback. > Where was this positive feedback? As you stated on #gentoo-dev today you don't really participate in the ML... so, I presume the positive feedback came on IRC. Most of us don't scan those logs to "prove" such things. Keep it on the ML and people will have record. > > > From my point of view your work is, and has been, appreciated, but you > > could coordinate better with other people. Hate to say it again, but > > toralf does seems to do a better job here too in that regard. Unless > > you're fine with comparing tinderboxers. > > With toralf's logs it's easy to reproduce the whole environment leading > > to a build failure, while with yours it's just build.log, thay may or > > may not be enough to find the build-breaking issue. > > This is something already discussed (maybe privately?) and clearly state by > me. > If you say that with my logs you are unable to reproduce the issue, since I'm > providing emerge --info and build log, you are saying that those info are not > enough. > So, I'd suggest to fix this issue upstream by clearly defining what is needed > in a bug report, because AFAIK atm for a bug report is needed a build log and > emerge --info > +1 to coordinate with others. Keep it here on the ML. This shouldn't be "ago v toralf"... it should be about the impact of your automation efforts on the rest of the community. Right now, it looks like that is mostly negative given the ML feedback. Frankly, if this is anything like your security efforts (re: fuzzing) then I can understand the concerns people have expressed. Please, stop with the "automate everything, open many bugs, and move on" philosophy. It didn't work well in security and it won't work here. Build a quality solution that makes an impact for the distro. -- Cheers, Aaron
signature.asc
Description: PGP signature
