glibc test tmpfails with SIGPIPE and exit code 1

Bug #1477023 reported by Iain Lane
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
autopkgtest (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

See the 2015-07-21 16:16:20 UTC run

  http://autopkgtest.ubuntu.com/packages/g/glibc/wily/i386/

"∙ Status: tmpfail (Unexpected adt-run exit code 1)"

In rebuild-stderr (artifacts)

"dpkg-buildpackage: error: debian/rules build died from signal 13"

but I don't see what went wrong in rebuild-stdout. It stops rather abruptly.

The i386 instance was left around (not hung) and I deleted it manually.

Revision history for this message
Iain Lane (laney) wrote :

2015-07-21 15:25:46,652 INFO:worker Received request for package glibc on wily/i386
2015-07-21 15:25:46,689 INFO:connectionpool Starting new HTTP connection (1): 10.222.64.12
2015-07-21 15:25:47,709 INFO:worker using nova image ubuntu/ubuntu-wily-daily-i386-server-20150717-disk1.img
2015-07-21 15:25:47,709 INFO:worker Running /home/ubuntu/autopkgtest/run-from-checkout --output-dir /tmp/adt-run.out.xNBx9Y --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest/setup-commands/cloud-vm-setup --apt-pocket=proposed --apt-upgrade glibc --timeout-test=20000 --- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor m1.large --image ubuntu/ubuntu-wily-daily-i386-server-20150717-disk1.img --keyname=testbed-juju-prod-ues-proposed-migration-machine-9 --net-id=net_ues_proposed_migration -e 'http_proxy=http://squid.internal:3128' -e 'https_proxy=http://squid.internal:3128' -e 'no_proxy=127.0.0.1,127.0.1.1,localhost,localdomain,novalocal,internal,archive.ubuntu.com,security.ubuntu.com,ddebs.ubuntu.com,launchpad.net' --mirror=http://ftpmaster.internal/ubuntu
2015-07-21 16:16:20,955 INFO:worker adt-run exited with code 1
2015-07-21 16:16:22,363 INFO:worker Putting results into swift autopkgtest-wily wily/i386/g/glibc/20150721_161622@
2015-07-21 16:16:22,367 INFO:connectionpool Starting new HTTP connection (1): 10.24.0.132
2015-07-21 16:16:22,471 INFO:connectionpool Starting new HTTP connection (1): 10.24.0.138
2015-07-21 16:16:25,348 INFO:connectionpool Starting new HTTP connection (1): 10.24.0.138
2015-07-21 16:16:25,969 INFO:connectionpool Starting new HTTP connection (1): 10.24.0.138
2015-07-21 16:16:26,330 INFO:connectionpool Starting new HTTP connection (1): 10.24.0.138
2015-07-21 16:16:26,449 INFO:worker Acknowledging request glibc

Revision history for this message
Martin Pitt (pitti) wrote : Re: tmpfail in glibc test

signal 13 is SIGPIPE, so not that surprising that the log is incomplete. No immediate idea about this one right now. Medium priority as retries work for now.

summary: - tmpfail in gilbc test
+ tmpfail in glibc test
affects: auto-package-testing → autopkgtest (Ubuntu)
Changed in autopkgtest (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
tags: added: autopkgtest-cloud
summary: - tmpfail in glibc test
+ glibc test tmpfails with SIGPIPE and exit code 1
Revision history for this message
Martin Pitt (pitti) wrote :

I haven't seen this in a long time, but I do remember chasing some "exit code 1" issues a while ago. Let's call this fixed until we run into it again.

Changed in autopkgtest (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.