[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#731263: marked as done (qa.debian.org: [collab-qa-tools] cqa-scanlogs is failing to detect a dpkg-gensymbols error)

Your message dated Sat, 28 Dec 2013 03:09:11 +0100
with message-id <CAJg5+Z3afqyNbDzsE+UBKNyUVFSTRXcK2w=Bk9SAhrQKPM-Q8g@mail.gmail.com>
and subject line qa.debian.org: [collab-qa-tools] cqa-scanlogs is failing to detect a dpkg-gensymbols error
has caused the Debian Bug report #731263,
regarding qa.debian.org: [collab-qa-tools] cqa-scanlogs is failing to detect a dpkg-gensymbols error
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
731263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731263
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: qa.debian.org
Severity: normal

Hello,

For example, with this log (not clang specific), the log shows is failed on dpkg-gensymbols
but the error is not detected by cqa-scanlogs.

For example:
http://clang.debian.net/logs/2013-07-14/phonon_4.6.0.0-3_unstable_clang.log

It seems to be from "collab-qa/log-parser-build.rb"
/dh_makeshlibs: dpkg-gensymbols .* returned exit code/,
which is expected only one line, while now, it is on two lines...

Sylvestre



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
Fixed in revision r2934.

Thanks

--- End Message ---
Reply to: