Bug#863101: Uscan uses all available memory of the system when run against guitarix
On 22/05/17 01:59, Adrian Bunk wrote: > On Sun, May 21, 2017 at 09:06:21PM +0200, Víctor Cuadrado Juan wrote: >> ... >> --- ~/.devscripts --- >> BTS_INTERACTIVE= yes >> ... > > Remove the space, this is the source of your problems. > > Looking at the manpage, it is actually documented behaviour. Well, that was it. Thanks and sorry for the noise. -- Víctor Cuadrado Juan m...@viccuad.me PGP key ID: 4096R: 0xA2591E231E251F36 Key fingerprint: E3C5 114C 0C5B 4C49 BA03 0991 A259 1E23 1E25 1F36 My signed E-Mails are trustworthy. signature.asc Description: OpenPGP digital signature
Bug#863101: Uscan uses all available memory of the system when run against guitarix
On Sun, May 21, 2017 at 09:06:21PM +0200, Víctor Cuadrado Juan wrote: >... > --- ~/.devscripts --- > BTS_INTERACTIVE= yes >... Remove the space, this is the source of your problems. Looking at the manpage, it is actually documented behaviour. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed
Bug#863101: Uscan uses all available memory of the system when run against guitarix
Hi, On Sun, May 21, 2017 at 11:09:03PM +0200, Víctor Cuadrado Juan wrote: > On 21/05/17 22:05, Adam D. Barratt wrote: > > > > I've been unable to reproduce this using either jessie or sid's uscan > > (running on a jessie host, admittedly). I'd be interested if anyone else > > can reproduce this or if there's anything unusual about the machine. > > Seems that it isn't only present on uscan: while running debsign I get a > segmentation fault. Have you checked hardware failure? Did you reinstall perl to be safe side? > I've carried out heavy tasks on the machine (compiling,etc), and apart > from this everything looks fine. Like compiling kernel in C code? debsign and uscan are perl code. Any of these regex tends to eat more memory but strange > I was able to reproduce it again on my workstation configuration deployed > into a fresh lxc container (using https://github.com/viccuad/salt-configs). > There, uscan consumes all the cpu until it gets killed by zsh, and debsign > the same. Why don't you create a new account with minimal customization and bash as login under a real machine. Let"s not complicate matter with lxc. Do you still suffer? Osamu
Bug#863101: Uscan uses all available memory of the system when run against guitarix
On Sun, 2017-05-21 at 23:09 +0200, Víctor Cuadrado Juan wrote: > On 21/05/17 22:05, Adam D. Barratt wrote: > > > > I've been unable to reproduce this using either jessie or sid's uscan > > (running on a jessie host, admittedly). I'd be interested if anyone else > > can reproduce this or if there's anything unusual about the machine. > > Seems that it isn't only present on uscan: while running debsign I get a > segmentation fault. > > I've carried out heavy tasks on the machine (compiling,etc), and apart from > this > everything looks fine. Then I have to admit to being stumped right now. I honestly find it very difficult to believe that there's a generic issue of this kind affecting debsign or uscan that no-one has yet reported in the more than two months since the last upload. Regards, Adam
Bug#863101: Uscan uses all available memory of the system when run against guitarix
Hi, On Sun, May 21, 2017 at 10:26:28PM +0200, Mattia Rizzolo wrote: > On Sun, May 21, 2017 at 09:05:38PM +0100, Adam D. Barratt wrote: > > Is there any particular reason you're not using something simpler, along > > the lines suggested by the manpage? This gives the expected result for > > me: > > > > version=3 > > http://sf.net/guitarix/ > > guitarix2(?:[_-]v?)?(\d.*)\.(?:tar\.xz|txz|tar\.bz2|tbz2|tar\.gz|tgz) > > btw, recentish uscan has support for subst patterns, which would reduce > all of that regexp to > guitarix2@ANY_VERSION@@ARCHIVE_EXT > which I kind of recommend to everybody… I am happy to hear you like this feature. To be precise, you need tailing @: guitarix2@ANY_VERSION@@ARCHIVE_EXT@ But I intentionally made these to be a bit conservative grep. @ANY_VERSION@ doesn't match -v23 @ARCHIVE_EXT@ doesn't match tgz or tgx So far only one bug report requesting tgz. I may consider adding it after careful regression check in buster. At least ? Actual target file can be matched as above :-) guitarix2-0.35.3.tar.xz Osamu
Bug#863101: Uscan uses all available memory of the system when run against guitarix
On 21/05/17 22:05, Adam D. Barratt wrote: > > I've been unable to reproduce this using either jessie or sid's uscan > (running on a jessie host, admittedly). I'd be interested if anyone else > can reproduce this or if there's anything unusual about the machine. Seems that it isn't only present on uscan: while running debsign I get a segmentation fault. I've carried out heavy tasks on the machine (compiling,etc), and apart from this everything looks fine. I was able to reproduce it again on my workstation configuration deployed into a fresh lxc container (using https://github.com/viccuad/salt-configs). There, uscan consumes all the cpu until it gets killed by zsh, and debsign the same. > On a side note, looking at the watchfile: > > (?:|.*/)guitarix2(?:[_\-]v?|)(\d[^\s/]*)\.(?:tar\.xz|txz|tar\.bz2|tbz2|tar\.gz|tgz) >... Well, that's a slipped leftover from the last maintainer. Thanks for the catch. Using your d/watch I get the same behavior, both in my machine and the lxc workstation. -- Víctor Cuadrado Juan m...@viccuad.me PGP key ID: 4096R: 0xA2591E231E251F36 Key fingerprint: E3C5 114C 0C5B 4C49 BA03 0991 A259 1E23 1E25 1F36 My signed E-Mails are trustworthy. signature.asc Description: OpenPGP digital signature
Bug#863101: Uscan uses all available memory of the system when run against guitarix
On Sun, May 21, 2017 at 09:05:38PM +0100, Adam D. Barratt wrote: > Is there any particular reason you're not using something simpler, along > the lines suggested by the manpage? This gives the expected result for > me: > > version=3 > http://sf.net/guitarix/ > guitarix2(?:[_-]v?)?(\d.*)\.(?:tar\.xz|txz|tar\.bz2|tbz2|tar\.gz|tgz) btw, recentish uscan has support for subst patterns, which would reduce all of that regexp to guitarix2@ANY_VERSION@@ARCHIVE_EXT which I kind of recommend to everybody… -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#863101: Uscan uses all available memory of the system when run against guitarix
Control: tags -1 + moreinfo unreproducible On Sun, 2017-05-21 at 21:06 +0200, Víctor Cuadrado Juan wrote: > When run against guitarix package git repo, at commit 7ff29bd, > for obtaining `guitarix2-0.35.3.tar.xz` that would become the > `guitarix_0.35.3.orig.tar.xz` symlink, `uscan --verbose` uses > all available ram of the system and if lucky it outputs > "Out of memory!". I've been unable to reproduce this using either jessie or sid's uscan (running on a jessie host, admittedly). I'd be interested if anyone else can reproduce this or if there's anything unusual about the machine. On a side note, looking at the watchfile: (?:|.*/)guitarix2(?:[_\-]v?|)(\d[^\s/]*)\.(?:tar\.xz|txz|tar\.bz2|tbz2|tar\.gz|tgz) The parenthesised groups are "either nothing, or zero or more characters followed by a slash", "either nothing, or [one of underscore, backslash or hyphen, possibly followed by v]", "a digit possibly followed by any number of characters that aren't whitespace or a slash", and then an extension. It seems very unlikely to me that those are actually the things you want to be matching - if you're trying to make the matching optional, then "(foo)?" would be far more idiomatic an obvious than "(foo|)" or "(| foo)", and the chances that there'll be a literal backslash in the URL are quite small. Is there any particular reason you're not using something simpler, along the lines suggested by the manpage? This gives the expected result for me: version=3 http://sf.net/guitarix/ guitarix2(?:[_-]v?)?(\d.*)\.(?:tar\.xz|txz|tar\.bz2|tbz2|tar\.gz|tgz) Regards, Adam
Bug#863101: Uscan uses all available memory of the system when run against guitarix
Package: devscripts Version: 2.17.5 Severity: critical -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 When run against guitarix package git repo, at commit 7ff29bd, for obtaining `guitarix2-0.35.3.tar.xz` that would become the `guitarix_0.35.3.orig.tar.xz` symlink, `uscan --verbose` uses all available ram of the system and if lucky it outputs "Out of memory!". I'm tagging it as critical because I have had my computer hard freeze 2 times after executing uscan, needing a power cycle. I have no configuration enabled for uscan in ~/.devscripts. Regards, - -- Víctor Cuadrado Juan m...@viccuad.me PGP key ID: 4096R: 0xA2591E231E251F36 Key fingerprint: E3C5 114C 0C5B 4C49 BA03 0991 A259 1E23 1E25 1F36 My signed E-Mails are trustworthy. - -- Package-specific info: - --- /etc/devscripts.conf --- - --- ~/.devscripts --- BTS_INTERACTIVE= yes DEBCHANGE_MULTIMAINT_MERGE=yes DEBSIGN_KEYID=0xA2591E231E251F36 DEBUILD_DPKG_BUILDPACKAGE_OPTS="-us -uc -I -i" DEBUILD_LINTIAN_OPTS="-i -I" - -- System Information: Debian Release: 9.0 APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-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 Init: systemd (via /run/systemd/system) Versions of packages devscripts depends on: ii dpkg-dev 1.18.23 ii libc62.24-10 ii perl 5.24.1-2 pn python3:any Versions of packages devscripts recommends: ii apt 1.4.1 ii at 3.1.20-3 ii curl7.52.1-5 ii dctrl-tools 2.24-2+b1 ii debian-keyring 2017.01.20 ii dput-ng [dput] 1.12 ii dupload 2.7.0 ii equivs 2.0.9+nmu1 ii fakeroot1.21-3.1 ii file1:5.30-1 ii gnupg 2.1.18-6 ii gnupg2 2.1.18-6 ii libdistro-info-perl 0.14 ii libdpkg-perl1.18.23 ii libencode-locale-perl 1.05-1 ii libgit-wrapper-perl 0.047-1 ii liblist-compare-perl0.53-1 ii liblwp-protocol-https-perl 6.06-2 ii libsoap-lite-perl 1.20-1 ii liburi-perl 1.71-1 ii libwww-perl 6.15-1 ii licensecheck3.0.29-1 ii lintian 2.5.50.3 ii man-db 2.7.6.1-2 ii patch 2.7.5-1+b2 ii patchutils 0.3.4-2 ii python3-debian 0.1.30 ii python3-magic 1:5.30-1 ii sensible-utils 0.0.9 ii strace 4.15-2 ii unzip 6.0-21 ii wdiff 1.2.2-2 ii wget1.18-5 ii xz-utils5.2.2-1.2+b1 Versions of packages devscripts suggests: pn adequate ii autopkgtest 4.4 ii bls-standalone 0.20151231 ii bsd-mailx [mailx]8.1.2-0.20160123cvs-4 ii build-essential 12.3 ii check-all-the-things 2017.01.15.1 pn cvs-buildpackage ii devscripts-el36.3+nmu1 ii diffoscope 78 pn disorderfs ii dose-extra 5.0.1-8 ii duck 0.12 pn faketime ii gnuplot 5.0.5+dfsg1-6 ii gpgv 2.1.18-6 ii how-can-i-help 15 ii libauthen-sasl-perl 2.1600-1 ii libfile-desktopentry-perl0.22-1 pn libnet-smtps-perl ii libterm-size-perl0.207-1+b4 ii libtimedate-perl 2.3000-2 pn libyaml-syck-perl pn mozilla-devscripts ii mutt 1.7.2-1 ii openssh-client [ssh-client] 1:7.4p1-10 pn piuparts pn ratt pn reprotest pn svn-buildpackage ii w3m 0.5.3-34 - -- no debconf information -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEELLKv6mdE0z94m2FAIj8VylqvDngFAlkh5SQACgkQIj8Vylqv Dnj+SQgAm0una6LSAdQiJ33oxUseyd59jfiivgFRo5yFb6WEqD2TWbqr0k8hsyTu BnzAekzDpvImPAzEiuZbaETUXzdgpi21s1Xu/YfEahjLUKc/zHK7cqxXaHE9Lk5p 92pU46FOnRdF53w9O1za4xNQSx9ynR2pgaq5V7OE369PuwEamm3OvGIlSjYjktvN Vdek40WZJXywpxYUKbSwn22tSgyJXcbk4kYRqvs7giX+NIvH/+V6Yo4HpMSge/6j DVib2/oQmsNkOjEu5wuAfy2KTBnR7Ff41s6thSkyBPdLjP9zwKl08T/VoVBYlRUg t0vQu/KOSXhaJkPym4GcKl6mpTW3jA== =Qpp3 -END PGP SIGNATURE-
