[Piuparts-devel] [Piuparts-reports] detect_network_issues

[Holger Levsen]

Hi,

since a week or so everday the same packages are rescheduled due to "network 
issues", so each day we get a mail like this...

(scroll down for the rest of my mail)

On Samstag, 20. Oktober 2012, piuparts master wrote:
> Network problems on detected!
> (By grep'ing for
>     'Cannot initiate the connection to',
>     'Failed to fetch',
>     'Some index files failed to download',
>     'Hash Sum mismatch',
>     'The following signatures were invalid'
> in failed logs.)
> Test failures due to modified /usr/share/doc/*/changelog.*
> are caused by mirror updates during the test.
> 
> The following logfiles have been deleted:
> 
> ----------------------------------------------------------------------
> 
> removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/dicomscope_3.6.0-9.l
> og' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/ecj_3.5.1-3.log'
> removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/gcj-jre-headless_4:4
> .7.1-1.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/gnustep-back-dbg_0.2
> 0.1-2+b1.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/jta_2.6+dfsg-5.log'
> removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libcharva1-java_1.1.
> 4-5.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libdtdparser-java_1.
> 21a-5.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libgcj-bc_4.7.1-1.lo
> g' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libgdcm-java_2.2.0-1
> 3.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libglpk-java_1.0.18-
> 1.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libhsqldb-java_1.8.0
> .10-11.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libjazzy-java_0.5.2-
> 1.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libjboss-integration
> -java_5.0.3.GA-2.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libjboss-reflect-jav
> a_2.0.3.GA-1.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libjboss-vfs-java_2.
> 0.1.GA-2.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libjempbox-java_1:1.
> 7.0+dfsg-3.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libjeuclid-core-java
> _3.1.9-2.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libjgoodies-animatio
> n-java_1.2.0-5.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libjmathtex-java_0.7
> ~pre-6.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libjmdns-java_3.4.1-
> 2.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libjspeex-java_0.9.7
> -3.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libsaxon-java_1:6.5.
> 5-8.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libsetools-java_3.3.
> 7-3.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libsvn-java_1.6.17df
> sg-4.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libtrang-java_200911
> 11-5.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libvtk-java_5.8.0-13
> +b1.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/libxml-java_1.1.6.df
> sg-3.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/openoffice.org-repor
> t-builder_1:3.4.0~ooo340m1-7.log' removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/pdftk_1.44-6.log'
> removed
> `/org/piuparts.debian.org/master//squeeze2wheezy/fail/xmlbeans_2.5.0-4.log
> '

so I've commited and pushed 6b5d2e898fa5fb982f5a0984cabcc0ff418b83dc to not 
cause changed changelogs to be detected as network issue, ie 
squeeze2wheezy/fail/libdtdparser-java_1.21a-5.log has this

  /usr/share/doc/gcc-4.4-base/changelog.Debian.gz        owned by: gcc-4.4-
base

which is clearly not an network issue.

Not sure how to reliable detect changing changelogs due to mirror pushes and 
thus resulting upgrades during a piuparts test... stopping piuparts during a 
mirror push would be possible, but I'm not sure if it's worth the hassle and 
this would also be rather piatti.d.o specific (ps fax|grep $mirror_process..)


cheers,
	Holger


cheers,
	Holger