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. > 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. > 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 If you want more info, why do not extend the emerge --info into for example emerge --info --extended instead of ask one by one to attach more info?? So the point is that there is no rule but just everyone ask without fixing the problem upstream. While you have a new option for detailed info, every people that run tinderbox or just people that report bugs can use it. If you see an example of toralf bug, I can see: gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-10.2.0 * clang version 11.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/11/bin /usr/lib/llvm/11 11.0.0 Available Python interpreters, in order of preference: [1] python3.7 [2] python3.9 (fallback) [3] python3.8 (fallback) [4] python2.7 (fallback) Available Ruby profiles: [1] ruby25 (with Rubygems) [2] ruby26 (with Rubygems) [3] ruby27 (with Rubygems) * Available Rust versions: [1] rust-bin-1.47.0 * The following VMs are available for generation-2: 1) IcedTea JDK 3.17.0 [icedtea-8] *) AdoptOpenJDK 8.272_p10 [openjdk-bin-8] Available Java Virtual Machines: [1] icedtea-8 [2] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.8.4 Again: why these info are not in emerge --info if are useful for a bugreport? I'm sure you understand the concept Agostino
