Skip Menu |

This queue is for tickets about the Data-StreamDeserializer CPAN distribution.

Report information
The Basics
Id: 78969
Status: open
Priority: 0/
Queue: Data-StreamDeserializer

People
Owner: Nobody in particular
Requestors: ANDK [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.06
Fixed in: (no value)



Subject: Fails at random
Cpantesters have tested UNERA/Data-StreamDeserializer-0.06.tar.gz with a PASS:FAIL ratio of 592:44. No systematic correlations between perl or architecture and test result could be identified. So I just tried to run the test on one perl several times in a row and I found that repeating the testing often enough seems to always produce a fail. From grepping through all results one find reports about positive and negative memory leaks: | http://www.cpantesters.org/cpan/report/22443550 | Check memory leak (-176128 bytes) | | http://www.cpantesters.org/cpan/report/21847014 | Check memory leak (319488 bytes) | | http://www.cpantesters.org/cpan/report/21029434 | Check memory leak (4096 bytes) | | http://www.cpantesters.org/cpan/report/21003860 | Check memory leak (352256 bytes) | | http://www.cpantesters.org/cpan/report/20592169 | Check memory leak (-352256 bytes) | | http://www.cpantesters.org/cpan/report/20251393 | Check memory leak (159744 bytes) | | http://www.cpantesters.org/cpan/report/20071751 | Check memory leak (-163840 bytes) | | http://www.cpantesters.org/cpan/report/20030362 | Check memory leak (-135168 bytes) | | http://www.cpantesters.org/cpan/report/19461842 | Check memory leak (-352256 bytes) | | http://www.cpantesters.org/cpan/report/19054819 | Check memory leak (221184 bytes) | | http://www.cpantesters.org/cpan/report/18975825 | Check memory leak (348160 bytes) | | http://www.cpantesters.org/cpan/report/18302958 | Check memory leak (159744 bytes) | | http://www.cpantesters.org/cpan/report/17360576 | Check memory leak (360448 bytes) | | http://www.cpantesters.org/cpan/report/16993787 | Check memory leak (176128 bytes) | | http://www.cpantesters.org/cpan/report/15492666 | Check memory leak (-319488 bytes) | | http://www.cpantesters.org/cpan/report/15327695 | Check memory leak (-167936 bytes) | | http://www.cpantesters.org/cpan/report/14448326 | Check memory leak (-159744 bytes) | | http://www.cpantesters.org/cpan/report/14382875 | Check memory leak (-4096 bytes) | | http://www.cpantesters.org/cpan/report/13952090 | Check memory leak (159744 bytes) | | http://www.cpantesters.org/cpan/report/12356113 | Check memory leak (-167936 bytes) | | http://www.cpantesters.org/cpan/report/11073411 | Check memory leak (-159744 bytes) | | http://www.cpantesters.org/cpan/report/11042873 | Check memory leak (-159744 bytes) | | http://www.cpantesters.org/cpan/report/11014803 | Check memory leak (159744 bytes) | | http://www.cpantesters.org/cpan/report/10904651 | Check memory leak (-159744 bytes) | From this grep I get the impression the results are purely random. What do you think? Thanks,
In Debian we are currently applying the following patch to Data-StreamDeserializer. We thought you might be interested in it too. Description: skip t/10_memoryleak.t in AUTOMATED_TESTING environment This test fails from time to time, which is probably caused by the complex nature of the perl memory allocator. This patch skips the test in automated environment. Author: Damyan Ivanov <dmn@debian.org> Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721418 Thanks for considering, Damyan Ivanov, Debian Perl Group

Message body is not shown because sender requested not to inline it.