[00:37] cjwatson: Hrm, did someone fix something, eglibc triggered a LOT more than 19 tests this time. === Ursinha-afk is now known as Ursinha === Noskcaj10 is now known as Noskcaj === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [09:10] infinity: Not I [11:00] jibel: Is there a way for mortals to retry autopkgtest runs? [11:02] infinity, yes there is, you will need a VPN Access to the QA Lab, then go to http://10.98.0.1:8080/view/Saucy/view/AutoPkgTest/ , select the job you want to restart and click on "Build" [11:02] (if jenkins UI can be considered for mere mortals) [11:03] Yeah, I'm not sure that internal Canonical VPNs count as "mere mortal" access for a community project. :P [11:03] But I'll get access to that sometime. [11:04] jibel: For now, can you retry eglibc/i386? That failure is probably a timing issue with kvm being crap. [11:04] (And certainly isn't due to any changes in the source) [11:05] infinity, eglibc restarted [11:05] jibel: And the chromium-browser failures look suspiciously more infrastructure related than packaging related. Though, it's hard to tell. [11:09] I'll look at chromium, qengho sent me an email about it last night. [12:27] what's the minimum delay between: dput ftp-master and package appearing in launchpad.net/debian/+source/package (and thus available for syncing)? or shall I be naughty and dput the same .dsc into ubuntu as well [12:30] xnox: The source has to be published in Debian, the mirror pulse has to occur to ftp.uk, then LP's mirror has to update and finally we have to scan it and import new sources. [12:30] So, it's like six hours or something [12:32] StevenK: ok, my current strategy is to write down a post-it note for the next day. I need to think of something better. I wonder if syncpackage can accept md5sum of the dsc to sync, and thus I could just cron it. [12:37] xnox: You can probably check for existance via the API every hour or something [12:37] You know the details [12:37] StevenK: sure. thanks. At least I know the ballpark delay now. [12:38] xnox: Six hours might be the median delay, I'm not sure. [12:38] I think it's near the upper limit. [12:38] (Now. Things used to be misaligned so it was worse.) [12:39] I remember sitting down with bigjools a while ago and changing the times so they were after dinstall not an hour beforehand. === rtg is now known as Guest10102 === doko_ is now known as doko === bdmurray_ is now known as bdmurray [15:29] https://code.launchpad.net/~cjwatson/launchpad/series-alias/+merge/178103 that was rather harder than I expected [15:33] cjwatson: You keep picking the "easy" tasks that take hundreds of lines to solve... [15:34] Yes, quite [16:05] infinity, eglibc is back to green [16:10] jibel: \o/ [16:27] 6 hours on the dot since debian accept email to http://pad.lv/d/abi-compliance-checker i wonder if I had impeccable timing =) [16:52] \o/ [16:53] xnox: isn't it? :) [17:01] bah ... someone synces debootstrap [17:03] *synced [17:05] What's wrong with that? [17:06] I did. [17:06] (And then the auto-syncer did.) [17:28] cjwatson, that my chromebook uses raring and i have to pull it manually :) ... [17:28] no worries ... i'm just pointlessly moaning :) [17:28] saucy chroot? [17:28] Or upgrade to saucy, surely it just works :) [17:29] yeah [17:29] but then i lose my hacked up graphics driver config ... getting unity to run in the chromebook isnt easy [17:30] i just wget'd and installed it [22:02] cjwatson: Does something magical need to happen for a retried test to be noticed by britney, or should I just force past it (the retry was successful). In this case, eglibc. [23:23] SRU team, can you look at bug 1207493? [23:23] Launchpad bug 1207493 in xubuntu-docs (Ubuntu) "Documentation does not match shipped system version (11.10 shipped with 12.04)" [High,New] https://launchpad.net/bugs/1207493