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

Bug#935292: lintian: reporing-harness get stuck when lintian deadlocks



Package: lintian
Version: 2.18.0
Severity: important

Spotted on lindsay.d.o:

The reporting framework runs lintian on a timer and can send it
SIGTERM if it gets stuck (usually when the processing time is over).
However, it seems that the reporting framework sometimes just
dies/disappeares after lintian is killed.  Below is the log from where
lintian was manually killed by me on a stuck package - but there are
plenty of examples that suggest it also happens when the
reporting-lintian-harness automatically kills lintian on a timeout.

"""
[2019-08-21T10:26:24]: New lintian log at /srv/lintian.debian.org/logs/lintian.log-bPGtadL
[2019-08-21T10:29:05]:   [lintian] error processing golang-1.11/1.11.13-1 (time: 122.898s)
[2019-08-21T10:29:06]:   [lintian] processed golang-github-mcuadros-go-gin-prometheus/0.1.0+git20190723.c7374e9-2 successfully (time: 1.396s)
[2019-08-21T10:32:37]:   [lintian] processed grass/7.8.0~rc1-1~exp1 successfully (time: 210.685s)
[2019-08-21T10:33:45]:   [lintian] processed grpc/1.23.0-1 successfully (time: 68.446s)
[2019-08-21T10:33:50]:   [lintian] processed guake/3.6.3-1 successfully (time: 5.118s)
[2019-08-21T10:33:56]:   [lintian] processed intel-cmt-cat/3.1.0-2 successfully (time: 5.953s)
[2019-08-21T10:34:03]:   [lintian] processed intel-processor-trace/2.0.1-1 successfully (time: 6.566s)
[2019-08-21T10:34:06]:   [lintian] processed libbpp-qt/2.4.1-2 successfully (time: 3.384s)
[2019-08-21T10:34:13]:   [lintian] processed libbpp-seq-omics/2.4.1-4 successfully (time: 7.356s)
[2019-08-21T10:34:17]:   [lintian] processed libconfig-model-itself-perl/2.018-1 successfully (time: 3.495s)
[2019-08-21T10:34:21]:   [lintian] processed libseqlib/1.1.2+dfsg-4 successfully (time: 3.913s)
[2019-08-21T10:55:19]:   [lintian] processed linux-signed-i386/5.2.9+1 successfully (time: 1258.298s)
[2019-08-21T10:55:42]:   [lintian] processed mandos/1.8.8-1 successfully (time: 22.420s)
[2019-08-21T11:15:26]: Signal SIGTERM acknowledged: disabled timed alarms
"""

After this, the harness.log simply "stops".

The package triggering it in this case was "mgcv" (now blacklisted on
lindsay.d.).  The lintian log looks like the following:

"""
N: Finished processing group mandos/1.8.8-1
N: Starting on group mgcv/1.8-28-2
N: Unpacking packages in group mgcv/1.8-28-2
N: Interrupted.
"""

The last line appeared after I killed lintian.  Please see [1] for the
last bit of the performance log which tells you what tasks lintian
managed to complete on mgcv.


This has probably been a key reason for why the lintian.d.o website
has not been updated in the past few days.

I hope it is helpful in debugging the issue.

Thanks,
~Niels


[1] Note the first line (mandos) is from the previous source just to ensure
that everything from mgcv is present.

"""
mandos/1.8.8-1,total-group-auto-remove,0.310351
binary:r-cran-mgcv/1.8-28-2/i386,coll/unpacked,1.007855
binary:r-cran-mgcv/1.8-28-2/amd64,coll/unpacked,1.168259
binary:r-cran-mgcv/1.8-28-2/i386,coll/file-info,0.524697
source:mgcv/1.8-28-2,coll/unpacked,0.9776
binary:r-cran-mgcv/1.8-28-2/amd64,coll/file-info,0.662295
binary:r-cran-mgcv/1.8-28-2/i386,coll/md5sums,0.216517
binary:r-cran-mgcv/1.8-28-2/amd64,coll/md5sums,0.187911
source:mgcv/1.8-28-2,coll/md5sums,0.230758
binary:r-cran-mgcv/1.8-28-2/i386,coll/objdump-info,0.317088
binary:r-cran-mgcv/1.8-28-2/amd64,coll/objdump-info,0.31345
binary:r-cran-mgcv/1.8-28-2/i386,coll/strings,0.342909
binary:r-cran-mgcv/1.8-28-2/amd64,coll/strings,0.366867
source:mgcv/1.8-28-2,coll/src-orig-index,0.306694
source:mgcv/1.8-28-2,coll/file-info,2.820701
binary:r-cran-mgcv/1.8-28-2/i386,coll/bin-pkg-control,0.569369
binary:r-cran-mgcv/1.8-28-2/i386,coll/override-file,0.083423
binary:r-cran-mgcv/1.8-28-2/amd64,coll/override-file,0.08031
binary:r-cran-mgcv/1.8-28-2/amd64,coll/bin-pkg-control,0.695504
source:mgcv/1.8-28-2,coll/override-file,0.127517
binary:r-cran-mgcv/1.8-28-2/i386,coll/ar-info,0.095013
binary:r-cran-mgcv/1.8-28-2/amd64,coll/ar-info,0.107359
binary:r-cran-mgcv/1.8-28-2/i386,coll/java-info,0.108112
binary:r-cran-mgcv/1.8-28-2/amd64,coll/java-info,0.125803
binary:r-cran-mgcv/1.8-28-2/i386,coll/copyright-file,0.072609
binary:r-cran-mgcv/1.8-28-2/amd64,coll/copyright-file,0.060382
binary:r-cran-mgcv/1.8-28-2/i386,coll/scripts,0.095971
binary:r-cran-mgcv/1.8-28-2/amd64,coll/scripts,0.096182
source:mgcv/1.8-28-2,coll/diffstat,0.065437
binary:r-cran-mgcv/1.8-28-2/i386,coll/changelog-file,0.138974
"""


Reply to: