Bug#745877: lintian: Unreasonable performance of detect_privacy_breach for clhep-doc/2.1.3.1-1/all

2014-06-22 Thread Bastien ROUCARIES
On Tue, Jun 17, 2014 at 11:08 PM, Niels Thykier ni...@thykier.net wrote:
 On 2014-06-17 22:18, Bastien ROUCARIES wrote:
 On Tue, Jun 17, 2014 at 9:12 PM, Niels Thykier ni...@thykier.net wrote:
 [...]
 The files-check of libgcj-doc in 2.5.22.1 has a runtime of 1356s -
 that is 22 minutes!  Even with our partial fix in the master branch, it
 is /only/ reduced to 605s or ~10 minutes!

 Ok what do you expect reasonable ?

 Bastien

 [...]

 Honestly, for the given case, I would personally say 5-10 seconds would
 be reasonable (from a user PoV), but I guess I could accept up to 30
 seconds (which would actually be a 5% regression from 2.5.19).
   But I am open for discussing/arguments on this topic.  In particular,
 there is also the alternative of moving this into a separate check that
 is disabled in the default profile.

Niels could you made a release. I have fixed it. The main problem is
now the time of read and is incompressible.

Bastien

 ~Niels




-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Processed: Re: Bug#745877: lintian: Unreasonable performance of detect_privacy_breach for clhep-doc/2.1.3.1-1/all

2014-06-17 Thread Debian Bug Tracking System
Processing control commands:

 severity -1 serious
Bug #745877 [lintian] lintian: Unreasonable performance of 
detect_privacy_breach for clhep-doc/2.1.3.1-1/all
Severity set to 'serious' from 'important'

-- 
745877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745877
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#745877: lintian: Unreasonable performance of detect_privacy_breach for clhep-doc/2.1.3.1-1/all

2014-06-17 Thread Bastien ROUCARIES
On Tue, Jun 17, 2014 at 9:12 PM, Niels Thykier ni...@thykier.net wrote:
 Control: severity -1 serious

 Hi,

 I noticed a similar complaint today - this time about gcc.
  * I believe the performance of this check to be inadequate and a
disservice to Lintian's users.
- With (what remains of) my Lintian maintainer hat, I consider this
  unsuitable for release.
  * I intend to revert / disable the checks within 14 days if they have
not been improved considerable before then.
- My best efforts[1] has been an improvement, but I still find it no
  where near acceptable performance.


 The files-check of libgcj-doc in 2.5.22.1 has a runtime of 1356s -
 that is 22 minutes!  Even with our partial fix in the master branch, it
 is /only/ reduced to 605s or ~10 minutes!

Ok what do you expect reasonable ?

Bastien

 For comparison, I have made this little table to show the impact since
 2.5.19 (the last version without the privacy-breaker tags):

   Wall-time  Relative to 2.5.19
 master 21m 30s   216%
 2.5.22.1   36m 19s   364%
 2.5.19  9m 57s   100%

 ~Niels

 [1] commit 60dcea84c2d5bbc4c2eb98c1361700d6e2c97ca6
 http://anonscm.debian.org/gitweb/?p=lintian/lintian.git;a=commitdiff;h=60dcea84c2d5bbc4c2eb98c1361700d6e2c97ca6



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#745877: lintian: Unreasonable performance of detect_privacy_breach for clhep-doc/2.1.3.1-1/all

2014-06-17 Thread Niels Thykier
On 2014-06-17 22:18, Bastien ROUCARIES wrote:
 On Tue, Jun 17, 2014 at 9:12 PM, Niels Thykier ni...@thykier.net wrote:
 [...]
 The files-check of libgcj-doc in 2.5.22.1 has a runtime of 1356s -
 that is 22 minutes!  Even with our partial fix in the master branch, it
 is /only/ reduced to 605s or ~10 minutes!
 
 Ok what do you expect reasonable ?
 
 Bastien
 
 [...]

Honestly, for the given case, I would personally say 5-10 seconds would
be reasonable (from a user PoV), but I guess I could accept up to 30
seconds (which would actually be a 5% regression from 2.5.19).
  But I am open for discussing/arguments on this topic.  In particular,
there is also the alternative of moving this into a separate check that
is disabled in the default profile.

~Niels


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org