Bug#712485:
On Fri, Feb 09, 2018 at 12:14:40PM +0100, Simon Ruderich wrote: > On Fri, Feb 09, 2018 at 09:07:06AM +, Nico Schlömer wrote: >> Perhaps it's useful to report which are the offending lines in the build >> log. For Trilinos [1], for example, a hidden flags are reported, but I have >> no idea why. Can you help me out? > > Hello, > > Running blhc on the build log lists the offending lines: > > NONVERBOSE BUILD: [ 76%] Building CXX object > packages/nox/src/CMakeFiles/trilinos_nox.dir/NOX_Abstract_Vector.C.o > NONVERBOSE BUILD: [ 97%] Building CXX object > packages/stokhos/test/UnitTest/CMakeFiles/Stokhos_TpetraCrsMatrixMPVectorUnitTest_Serial.dir/Stokhos_TpetraCrsMatrixMPVectorUnitTest_Serial.cpp.o > > I'm not sure if the output can/should be added to the > lintian/build log parser as it can be quite big and I don't know > how the architecture handles custom output. > > CCing Bernhard who I think is managing the build log parser. On Fri, Mar 02, 2018 at 09:42:37AM +0100, Simon Ruderich wrote: > Hi Nico, > > Not sure how I missed this mail, sorry for that. I've just > released blhc 0.08 which contains a --line-numbers option > (suggested by Stefan Pöschel). Ah, didn't miss it just overlooked the mail in my mailbox and then misread your original mail, sorry for the confusion. Still waiting for Bernhard's reply. Regards Simon -- + privacy is necessary + using gnupg http://gnupg.org + public key id: 0x92FEFDB7E44C32F9 signature.asc Description: PGP signature
Bug#712485:
On Fri, Feb 09, 2018 at 09:07:06AM +, Nico Schlömer wrote: > Perhaps it's useful to report which are the offending lines in the build > log. For Trilinos [1], for example, a hidden flags are reported, but I have > no idea why. Can you help me out? Hi Nico, Not sure how I missed this mail, sorry for that. I've just released blhc 0.08 which contains a --line-numbers option (suggested by Stefan Pöschel). Regards Simon -- + privacy is necessary + using gnupg http://gnupg.org + public key id: 0x92FEFDB7E44C32F9 signature.asc Description: PGP signature
Bug#712485:
On Fri, Feb 09, 2018 at 09:07:06AM +, Nico Schlömer wrote: > Perhaps it's useful to report which are the offending lines in the build > log. For Trilinos [1], for example, a hidden flags are reported, but I have > no idea why. Can you help me out? Hello, Running blhc on the build log lists the offending lines: NONVERBOSE BUILD: [ 76%] Building CXX object packages/nox/src/CMakeFiles/trilinos_nox.dir/NOX_Abstract_Vector.C.o NONVERBOSE BUILD: [ 97%] Building CXX object packages/stokhos/test/UnitTest/CMakeFiles/Stokhos_TpetraCrsMatrixMPVectorUnitTest_Serial.dir/Stokhos_TpetraCrsMatrixMPVectorUnitTest_Serial.cpp.o I'm not sure if the output can/should be added to the lintian/build log parser as it can be quite big and I don't know how the architecture handles custom output. CCing Bernhard who I think is managing the build log parser. Regards Simon -- + privacy is necessary + using gnupg http://gnupg.org + public key id: 0x92FEFDB7E44C32F9 signature.asc Description: PGP signature
Bug#712485:
Perhaps it's useful to report which are the offending lines in the build log. For Trilinos [1], for example, a hidden flags are reported, but I have no idea why. Can you help me out? Cheers, Nico [1] https://buildd.debian.org/status/fetch.php?pkg=trilinos&arch=amd64&ver=12.12.1-5&stamp=1517856320&raw=0
Bug#712485: blhc reports false positives for W-compiler-flags-hidden
On Fri, Aug 16, 2013 at 09:38:35AM +0300, Jari wrote: > Simon, could you consider simply adding an exception: > > IF first line contains "building.*libmd" > AND the second line contain "zfsutils" > THEN > Ignore reporting non-verbose-build Hello Jari, I don't think adding package-specific ignores is a good idea. This will soon get overwhelming when we have to add ignores for more packages. In addition many ignores will make blhc even slower. To handle this for many packages we would need a way to pass packages-specific ignores to blhc. I guess dpkg-buildpackage could extract them from the package during the build and display them in the build log, allowing blhc to extract and apply them. Bernhard suggested something similar to make the buildflags available for log parsers (#664058). Bernhard, what do you think would be the best way to handle this for rules to ignore false positives? Btw. I see #664058 was closed, was this already integrated into dpkg-buildpackage to provide these information for the build logs? I checked one of the latest build logs and couldn't find it. Regards Simon -- + privacy is necessary + using gnupg http://gnupg.org + public key id: 0x92FEFDB7E44C32F9 signature.asc Description: Digital signature
Bug#712485: blhc reports false positives for W-compiler-flags-hidden
On 2013-08-14 21:50, Simon Ruderich wrote: | On Sun, Jun 16, 2013 at 02:12:55PM +0200, Arno Töll wrote: | > However, it reports zfsutils to hide compiler flags [3] | | building shared library libmd.so.1 | | This matches the general "non-verbose-build" regex. To prevent | too many false positives blhc then checks the next line if it | contains any commands for libmd.so.1. In zfsutils' case it | doesn't, therefore blhc reports the line as non-verbose. | | I don't know how to handle this case better without causing many | false-negatives. If you have any ideas please tell me. I can't think of any generic solution either based on the build log [3] https://buildd.debian.org/status/fetch.php?pkg=zfsutils&arch=kfreebsd-i386&ver=9.0-3&stamp=1340402716 Simon, could you consider simply adding an exception: IF first line contains "building.*libmd" AND the second line contain "zfsutils" THEN Ignore reporting non-verbose-build Jari signature.asc Description: Digital signature
Bug#712485: blhc reports false positives for W-compiler-flags-hidden
On Sun, Jun 16, 2013 at 02:12:55PM +0200, Arno Töll wrote: > However, it reports zfsutils to hide compiler flags, which it doesn't [3]. > Please > check more careful for false positives. Hello Arno, Sorry for the late reply. Checking for hidden compiler flags is difficult and I haven't found a good solution yet (if there is any). blhc uses a simple heuristic to detect suspicious lines which may indicate hidden compiler flags. Most of the time it works well, but there are (many) false positives. Regarding zfsutils' log, it contains the following line: building shared library libmd.so.1 This matches the general "non-verbose-build" regex. To prevent too many false positives blhc then checks the next line if it contains any commands for libmd.so.1. In zfsutils' case it doesn't, therefore blhc reports the line as non-verbose. I don't know how to handle this case better without causing many false-negatives. If you have any ideas please tell me. Regards Simon -- + privacy is necessary + using gnupg http://gnupg.org + public key id: 0x92FEFDB7E44C32F9 signature.asc Description: Digital signature
Bug#712485: forwarded to upstream
forwarded 712485 Simon Ruderich forwarded 714626 Simon Ruderich forwarded 714628 Simon Ruderich forwarded 714630 Simon Ruderich forwarded 717598 Simon Ruderich forwarded 719656 Simon Ruderich thanks Hi Simon, Could you take a look at these bugs: http://bugs.debian.org/blhc Thanks, Jari -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#712485: blhc reports false positives for W-compiler-flags-hidden
Package: blhc Severity: normal While discussing verbose build logs as a Jessie release goal [1]. The list of affected packages is generated by [2] which in turn uses blhc. However, it reports zfsutils to hide compiler flags, which it doesn't [3]. Please check more careful for false positives. [1] <51bb0006.4080...@debian.org> [2] https://buildd.debian.org/~brlink/bytag/W-compiler-flags-hidden.html [3] https://buildd.debian.org/status/fetch.php?pkg=zfsutils&arch=kfreebsd-i386&ver=9.0-3&stamp=1340402716 -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
