[02:51] <jbicha> could you retry the gtk+3.0 and gvfs autopkgtests? apparently they were triggered before the i386 gtk+3.0 binary had been fully published
[03:01] <jbicha> and notify-osd, software-properties, evolution-data-server
[08:56] <xnox> Can ubuntu-themes please let through? it's being held by firefox autopkgtest that is failing
[08:56] <xnox> autopkgtest for firefox 23.0~b10+build1-0ubuntu1: FAIL
[08:58] <xnox> Please de-new multi-arched tcl8.6 (following suite of the default tcl8.5) https://launchpad.net/ubuntu/saucy/+queue?queue_state=0&queue_text=tcl
[09:06] <cjwatson> infinity: Retries *ought* to be collected automatically
[09:10] <cjwatson> Hm, gtk+3.0 doesn't seem to have been though
[09:11] <cjwatson> jibel: ^- Do you know why adt-britney still thinks gtk+3.0 is running?
[09:12] <cjwatson> There's a .result file with a pass at the proper version, AFAICS
[09:16] <jibel> cjwatson, I think I fixed gtk+3.0 earlier this morning, the only running I see in excuses are
[09:16] <jibel> autopkgtest for postgresql-9.1 9.1.9-2bzr1: RUNNING (Jenkins: public, private)
[09:16] <jibel> autopkgtest for php5 5.5.1+dfsg-1ubuntu1: RUNNING (Jenkins: public, private)
[09:16] <jibel> for tzdata
[09:16] <jibel> cjwatson, where do you see gtk+3.0 is running?
[09:17] <jibel> s/I think//
[09:22] <cjwatson> $ cat saucy-proposed_amd64_gtk+3.0; echo
[09:22] <cjwatson> {"status": {"i386": "RUNNING", "amd64": "RUNNING", "all": "RUNNING"}
[09:22] <cjwatson> [...]
[09:22] <cjwatson> in ~ubuntu-archive/proposed-migration/autopkgtest/data/adt/saucy-proposed/amd64/
[09:22] <cjwatson> And in excuses, gtk+3.0 is listed as FAIL, which is also wrong but differently
[09:23] <cjwatson> The most recent test at that version passed and that was several hours ago
[09:24] <cjwatson> chrisccoulson: Any chance of either fixing or removing the firefox autopkgtests?
[09:25] <cjwatson> xnox: firefox tests forced for now
[09:26] <xnox> cjwatson: thanks.
[09:37] <seb128> cjwatson, on -devel earlier: <chrisccoulson> seb128, jibel, i can't reproduce it here. and from looking at the log, it doesn't look like it even gets to the point of starting the test harness
[09:41] <infinity> cjwatson: The retry for eglibc doesn't seem to have been picked up, it's still FAIL.
[09:42] <chrisccoulson> seb128, cjwatson, see last comment in #ubuntu-devel ;)
[10:00] <xnox> https://jenkins.qa.ubuntu.com/job/saucy-adt-ubiquity/128/ARCH=i386,label=adt/console is very odd, it failed, but it is testing 2.15.13 adt tests against 2.15.12 installed package.
[10:00] <xnox> which is expected to fail, but obsolete package version is being tested.
[10:00] <xnox> jibel: cjwatson: ^ mirror delays again?!
[10:09] <cjwatson> xnox: not my fault
[10:18] <jibel> xnox, it's my fault. I'm stepping through the workflow to find where it should wait, and where test states get out of sync
[10:30] <ogra_> Setting up python3.3-minimal (3.3.2-3ubuntu1) ...
[10:30] <ogra_>   File "/usr/lib/python3.3/site.py", line 232
[10:30] <ogra_>     if hasattr(os, "getgid") and hasattr(os, "getegidify         # check process gid == effective gid
[10:31] <ogra_> hmfp ...
[10:31] <ogra_> (last ubuntu touch image build ^^^)
[10:32] <ogra_> weird, and there were no changes to python
[10:33] <cjwatson> ogra_: it's obvious panda damage again
[10:33] <cjwatson> just retry
[10:34] <ogra_> yeah, i'm not sure if i shouldnt ask for a reboot first
[10:34] <cjwatson> I wouldn't bother
[10:34] <ogra_> k
[10:34]  * ogra_ retires
[10:34] <cjwatson> I was actually just in the process of catching up on #ubuntu-touch to see if you were already discussing this before telling you
[10:40] <cjwatson> infinity: How goes the Calxeda install, anyway? :)
[10:40] <ogra_> ++
[10:40] <ogra_> :)
[10:41] <infinity> cjwatson: See #is.
[10:43] <cjwatson> Hm, right