/srv/irclogs.ubuntu.com/2014/06/16/#ubuntu-ci-eng.txt

* ogra_ gets coffee08:27
sil2100So tired...08:28
* popey stabs 2fa08:32
* Mirv had some login.ubuntu.com problems earlier and webops were looking at it08:36
popeyyeah, needs a lot of refreshes08:37
ogra_sil2100, if you decide to promote anything during teh evening meeting, just leave a ping around, i'll promote it later then08:56
ogra_brendand, popey, so looking at the console log of the failing filemanager tests i noticed something ...09:05
* popey crosses fingers09:05
ogra_it seems to redefine $HOME suring the tests all the time ... to a tmpdir ...09:05
ogra_but i also see:09:05
ogra_void DirModel::setPath(const QString&) DirModel(0x739038) path or url may not exist or cannot be read: "~"09:05
popeyʘ‿ಠ09:06
ogra_so it seems the test (or the filemanager itself) tries to use ~/09:06
ogra_i'm not sure that expands to $HOME correctly09:06
brendandogra_, i see that too. i'll try and find if the test is doing it09:07
ogra_(i.e. it might read this from PAM instead of the environment, so you get expansion of the variable for what hopme was set to at login time)09:07
ogra_doe it actually use a fake $HOME when you test locally too =09:08
ogra_?09:08
popeyogra_: sil2100 brendand i just ran the filemanager tests on flo with qt53 and it passed09:18
popeyRan 24 tests in 563.684s09:18
popeyOK09:18
popeyso only change was a) make image writable [may have affected tests?] and b) upgrade to qt5.309:19
brendandpopey, i run it with writable image too09:19
popeyk09:19
brendandpopey, do it again :)09:19
* popey reboots09:19
popeyhah09:19
sil2100:O09:21
cjwatson14197 07:00:01      \_ /usr/bin/python /home/ubuntu-archive/cu2d/cupstream2distro//copy2distro --no-filter09:21
cjwatsonI suspect that's probably hung ... killing it09:21
cjwatson(we had an rsync hung from around the same time too, so I guess some network problem)09:22
* ogra_ noticed network issues with the image builders too09:23
popeybrendand: passed second time09:31
popeythats it, land qt 5.3!09:31
* popey runs again09:31
brendandpopey, wow, how lucky is that09:39
sil2100Saviq: I see a new landing for unity8 - but I see it's already assigned in silo 00809:43
sil2100Saviq: any possibility of releasing 008 before that?09:43
Saviqsil2100, unlikely09:45
Saviqsil2100, there's an issue with indicator-session there that makes the whole silo useless09:45
sil2100Saviq: should I free this silo then? Or do you still intend to work on this with bregma in the nearest time?09:46
Saviqsil2100, we will, this week for sure09:46
Saviqsil2100, and the new unity8 landing should be real quick09:46
sil2100Saviq: ok, since you're the lander for both, I do 'override' and just sync up the changes then09:47
Saviqsil2100, thanks09:50
brendandsil2100, did we discuss the address-book-app failures at all?09:51
* ogra_ doesnt think so 09:52
popeybrendand: failed on the 3rd go, hangs forever09:52
ogra_we also missed the changes (though they are minor and mostly not affecting us)09:52
brendandogra_, looks like that was a mistake. there were two failures and it seems they were genuine09:53
brendandogra_, it's not possible to type into the text fields in the contact editor09:53
ogra_oh09:54
ogra_that indeed sounds liek a real bug09:54
ogra_*like09:54
brendandhmmm, wait. well there is a bug there09:55
brendandbut it looks like the AP tests don't catch it because they don't use the keyboard09:56
sil2100brendand: we discussed them last week, I have a bug for those09:57
sil2100brendand: will poke bfiller about those today09:57
brendandok, looks like it was just some momentary strangeness. i'll file a bug if it happens again10:04
sil2100brendand: I tried running those address-book-app AP tests on my device when filling in the bug but they passed twice10:05
ogra_popey, looking at your bootcharts ... your system never goes properly to idle, else the new chart would stop *a lot* earlier10:36
ogra_brendand, so running the filemanagerr test locally with exactly the same args:11:01
ogra_phablet-test-run -A '--timeout-profile=long' -v -o test-out -f subunit -a /var/crash -a /home/phablet/.cache/upstart filemanager11:01
ogra_doesnt print any of these "~" messages11:01
ogra_oh, wait11:01
ogra_i see it in the apps own log11:02
ogra_aha11:03
ogra_                page: FolderListPage {11:03
ogra_                    objectName: "folderPage"11:03
ogra_                    folder: "~"//modelData11:03
ogra_                }11:03
ogra_line 103 hardcodes ~11:04
ogra_(looking at /usr/share/click/preinstalled/com.ubuntu.filemanager/0.3.193/qml/filemanager.qml)11:04
ogra_aha, line 75 has it too11:07
ogra_property var folderTabs: ["~"]11:07
=== MacSlow is now known as MacSlow|lunch
ogra_hmm, and looking at the test code it never exports HOME= but only sets it via initctl11:14
* Mirv wonders if boiko is going to land the address book stuff today11:14
ogra_(it uses the export for desktop tests of the same package)11:14
Mirv(it includes an Qt 5.3 related fix)11:14
Mirvyes, just the one sil2100 is looking at :)11:14
sil2100Mirv: do you know if it also touches our autopilot issues?11:15
Mirvsil2100: no, I don't know, I'm just interested in that crash fix and I haven't looked at the other MR:s11:15
sil2100Damn, the spreadsheet is not auto-updating again...11:16
sil2100It's barfing out on fetching the backend webpage with an 'unexpected error'11:16
sil2100It's something I can do nothing to fix...11:32
sil2100brb11:33
popeyogra_: which? wopr or deep-thought?11:40
ogra_popey, the long boot11:40
ogra_the short one has an awful gap11:40
ogra_it could boot 10sec faster if you would utilize CPU and disk in the middle11:41
ogra_(by shuffling stuff around)11:41
popeyi just wiped my laptop clean ☻11:41
ogra_also none of your systems seems to run ureadahead at all ... it wastes *a lot* if you dont run that11:42
popeyeven on ssd?11:42
popeyi dont recall disabling that11:42
ogra_even SSDs like it if you load everything into RAM at once and can read from there during the further process11:42
davmor2popey: if you open file browser on mako do you very briefly get the flo portrait tablet view?11:43
ogra_SSDs might be fast ... but RAM is still faster :)11:43
davmor2ogra_: Rom is faster :P11:44
ogra_lol11:44
ogra_right11:44
popeydavmor2: kinda, yes11:44
davmor2popey: I'm wondering if autopilot is faster than my finger and can start running on the wrong view11:46
popeydont think so11:46
popeythe ap doesn't appear at all with broken tests11:47
popeyyou just get the unity loading dots11:47
* ogra_ is pretty sure the issues are related to the $HOME setting 11:47
popeyogra_: is it easy to patch the tests to prove that?11:47
ogra_popey, i tried but then it cant find the click anymore11:47
popeyjust replace ~ with /home/phablet ?11:47
popeyin the filemanager tests only11:47
ogra_autopilot/filemanager/tests/__init__.py11:48
popeyyes11:48
ogra_there is a line setting it11:48
popeyi fudged $HOME in there and it failed differently11:48
popeywhich is obviously wrong11:48
popeyneeds to be the tmp home ?11:48
ogra_conditionally based on if the package is click or not11:48
ogra_right11:48
ogra_        if self.test_type == 'click':11:49
ogra_            self.useFixture(toolkit_fixtures.InitctlEnvironmentVariable(11:49
ogra_                            HOME=temp_dir))11:49
ogra_        else:11:49
ogra_            self.useFixture(fixtures.EnvironmentVariable('HOME',11:49
ogra_                                                         newvalue=temp_dir))11:49
ogra_i was trying to make it set it in both places for the click case11:49
ogra_but that ends in  WARNING **: Unable to find keyfile for application 'com.ubuntu.filemanager_filemanager_0.3.193'11:50
ogra_what the app code would need would be reading the env var and putting it in there ... but i'm not sure QMl can do that easily11:51
ogra_("there" being the hardcoded places(11:51
dbarthsil2100: o/ hi, i'm marking silo 14 has verified11:52
sil2100dbarth: o/ Ok, let me check that11:53
dbarthfor reference, this requires 2 updates to pre-installed click packages to fully fix the issue11:53
dbarth1 gmail webapp update (correcting an extra url path)11:53
dbarthand 1 faceook webapp update (to avoid a UX regression on switching to external links)11:53
dbarthboth webapps have been pushed to the store for review11:53
dbarthyou can land silo 14 as soon as you want (it won't break the apps), but you may want to get those 2 other updates in the same image though11:54
ogra_Mirv, see my conversation with popey ... is there any easy way to use $HOME in QML without having a C++ provider that reads it first ?11:54
davmor2sil2100: 83 is looking as good as any I've seen recently11:56
sil2100davmor2: great to hear that :)11:56
davmor2sil2100: however phone still dies with no warnings11:57
ogra_dies ?11:57
ogra_when, how ?11:58
sil2100davmor2: awww... well, we didn't expect this to be fixed, we just *hoped* it has improved with the indicator landing11:58
davmor2ogra_: when there is suddenly no battery left11:58
ogra_oh11:58
sil2100ogra_: I think davmor2 means the no-battery-death11:58
ogra_yeah11:58
ogra_thats expected11:58
ogra_right, we have bogs open for that11:58
ogra_*bugs too11:58
popeyhas anyone else noticed nm clinging onto the furthest access point away?11:58
popeymine is always attached to the farthest one when i boot up11:58
ogra_i thought some other ddeath we dont know about yet11:58
ogra_popey, talk to cyphermox11:59
=== alan_g is now known as alan_g|lunch
davmor2popey: which connection did you setup first it will maybe stay connected to that one as preferred12:00
popeyno idea12:00
popeyfrom the dates in /etc/NetworkManager/system-connections it wasn't the oldest, but newest12:01
Mirvogra_: maybe ask on #ubuntu-app-devel12:11
Mirvthe SDK guys might know12:11
ogra_yeah, will do12:11
Mirvuh, new webbrowser-app, I have to be again trigger-happy in Qt PPA once it has been m&c:d12:19
Mirvsome news from Qt 5.3 land: address-book now passes completely (but the fix should still land for real too). calendar app seems to be duplicate of current image bug, so not really new.12:32
Mirvsil2100: is there a bug tracking the calendar app failures, I don't see it on the landing team mails?12:33
sil2100Mirv: I think we didn't add that yet, it wasn't happening all the time last week12:33
sil2100Mirv: but a bug should be present, one moment12:34
Mirvit seems there are several bugs about it12:34
Mirvnot sure if there's master bug12:34
Mirvbut well, bug #1329821 matches this newest run exactly so I can mark my bug a duplicate of that12:35
ubot5bug 1329821 in Ubuntu Calendar App "test_show_next_years failed on mako #81" [Undecided,New] https://launchpad.net/bugs/132982112:35
sil2100Mirv: sadly there is no bug for this one failure, but I guess there is one root cause of all of them12:35
Mirvyeah probably12:36
Mirvthere's 6 separate bugs at https://bugs.launchpad.net/ubuntu-calendar-app/+bugs?orderby=-importance&memo=75&start=7512:36
Mirvpopey: do you happen to have your qt 5.2 device within reach? I think that blabble would be worth testing there since according to automated testing it doesn't work there either.12:40
popeyblabble works fine on 5.212:44
* sil2100 goes prepare lunch12:44
Mirvpopey: ok, can you update bug #1327667 accordingly? it was just that it had a crash folder also on the stock image testing tarballs of yours.12:44
ubot5bug 1327667 in qtchooser (Ubuntu) "blabble + qt5.3 on flo #73 crash" [Undecided,Incomplete] https://launchpad.net/bugs/132766712:44
=== MacSlow|lunch is now known as MacSlow
Mirvpopey: and to ping bomb you more, maybe test inews again bug #1327680 since I just marked it as Invalid, plus railroad & blackjack which I marked as incomplete earlier since they seemed to work for me bug #132759512:45
ubot5bug 1327680 in Unity 8 "Qt5.3 unity8 greeter crash" [High,Invalid] https://launchpad.net/bugs/132768012:45
ubot5bug 1327595 in media-hub (Ubuntu) "railroad app crashes media-hub in #73" [Undecided,Incomplete] https://launchpad.net/bugs/132759512:45
Mirvelopio: hi! zsombi & co were interested in whether you completed the UITK testing successfully, as it's currently marked as not tested and therefore not getting published?12:48
Mirvelopio: well zoltan is mentioning that he'd consider rebuilding from newest staging and testing again12:50
Mirvelopio: aaand he's doing it (updating the MP with latest staging including your swipe fixes)12:52
Mirvelopio: the Qt 5.3 testing btw showed some swipe failures at http://q-jenkins.ubuntu-ci:8080/job/qt-release-gatekeeper/1/#showFailuresLink - maybe your branch would fix those too?12:52
=== davmor2__ is now known as davmor2
ogra_sil2100, did oyu notice the ubuntu-touch-meta upload ? i think we should have an image build soon so we can see what the language pack switch gained us12:56
sil2100ogra_: oh, right, it was around noon13:00
sil2100Damn missed that one completely13:00
sil2100ogra_: yeah, an image would be good now - I guess there's nothing specific we're waiting for right now13:00
sil2100Just normal landings happening13:00
popeyMirv: 5.3 call?13:00
sil2100So you can kick a new image13:00
=== alan_g|lunch is now known as alan_g
=== Ursinha is now known as Ursinha-afk
ogra_sil2100, image triggered (sorry, had a distracting phone call)13:51
ogra_popey, FYI ... a bootchart should always use all available CPu if possible to boot as fast as possible ... also take a look at the disk how it loads all files very early in the boot due to ureadahead http://people.canonical.com/~ogra/touch-bootcharts/ubuntu-phablet-utopic-83.png13:57
ogra_(the interesting bits in a bootchart are the two graphs at the top ... the rest is mostly just there to confuse you ;) )13:59
imgbot=== trainguard: IMAGE 84 building (started: 20140616 14:00) ===13:59
mhr3sil2100, my latest silo request will probably take a while to land, consider it non-blocking, i'll keep rebuilding the components14:06
mhr3sil2100, will also need a few reconfs14:07
sil2100Ok14:08
Mirvboiko: hi, are you landing the telephony-service/address-book-app today? it'd be nice to have for Qt 5.314:08
sil2100hmm.. unity8 again ;p Grrr14:09
sil2100But since you promise to take care of it, I give you an override14:09
boikoMirv: any specific landing you need? we are landing the first round of new designs today14:10
=== Ursinha-afk is now known as Ursinha
elopiofginther: maybe, it will be useful to have another gatekeeper job like the qt one for the toolkit. What do you say?14:20
fgintherelopio, let me have a conversation with the rest of the team first to see where we are on capacity and usage, etc.14:22
Mirvboiko: landing-001, specifically https://code.launchpad.net/~renatofilho/telephony-service/fix-phonenumber-crash/+merge/22279714:22
Mirvboiko: I've made manual build of that branch to the Qt 5.3 PPA which fixes all address book app issues on 5.3, but getting it landed to archives would help in getting rid of that temporary build14:22
=== alan_g is now known as alan_g|tea
elopiofginther: yes, thanks.14:27
boikoMirv: that's being tested, this will land soon14:28
Mirvboiko: thanks, great14:29
mhr3sil2100, so, where's my silo?14:32
sil2100mhr3: hmmm, one moment, I guess the spreadsheet might have not auto-updated itself14:33
sil2100Let me check14:33
=== alan_g|tea is now known as alan_g
=== Ursinha is now known as Ursinha-afk
=== doanac changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: doanac | CI Train Status: #79 promoted | CI Train Support: US: robru, stgraber - EU: sil2100, Mirv | Known issues: -
imgbot=== trainguard: IMAGE 84 DONE (finished: 20140616 15:15) ===15:14
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/84.changes ===15:14
sil2100o/15:15
ogra_40MB fat lost in the tarball \o/15:25
ogra_(from 508 down to 470MB)15:25
davmor2ogra_: that or it's forgotten libs ;)15:25
ogra_nah, its dropped desktop translations15:26
sil2100I love whenever the image is slimmed down15:35
=== Ursinha-afk is now known as Ursinha
elopioping doanac. It seems that this crash was not traced:15:49
elopiohttp://ci.ubuntu.com/smokeng/utopic/touch/mako/78:20140611.1:20140530/8530/unity8/1241528/15:49
elopiois jenkins configured to do whoopsie-upload-all before storing the artifacts?15:49
doanacelopio: we should upload any .crash files that are generated on the target. I see a link to a crash file: http://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/282/artifact/clientlogs/unity8/_usr_lib_arm-linux-gnueabihf_qt5_bin_qmlscene.32011.crash/*view*/15:50
doanacis that not what you are needing?15:51
elopiodoanac: no. Saviq says that we need to trace that crash on the device that generated it.15:53
Saviqelopio, not exactly the same device, but at least one with the same packages on it15:53
elopio" otherwise the .crash file is missing details"15:53
Saviqyeah, it doesn't even contain the version of the package15:54
Saviqor the symbols that are otherwise available on device15:54
doanacelopio: Saviq: k. I think we may need to update phablet-test-run for this. I believe we call phablet-test-run and just tell it to pull everything under /var/crash15:55
Saviqdoanac, at some point at least it also did whoopsie-upload-all15:55
Saviqdoanac, which would have processed the files and upload them to errors.u.c15:55
doanacSaviq: okay. looking at p-t-r now, there's no reference to whoopsie.15:56
doanaci can take a stab at an MP today. i just need to call "whoopsie-upload-all" after running a test?15:56
Saviqdoanac, afaict, yes, but probably make sure to time it out in case there's network failure or something of the sort15:57
doanacSaviq: ack - good point.15:57
Saviqor well, jenkins would time it out anyway, wouldn't it15:57
doanacyeah, but jenkins has a big timeout. we should make this a little more fine grained15:57
Saviqyup15:57
doanacSaviq: any ideas on what a sensible timeout would be?15:57
Saviqdoanac, I'd say a few minutes15:58
doanack. i'll see what i can do. thanks15:58
Saviqdoanac, just try crashing unity815:58
Saviq(i.e. kill -11 `pidof unity8`)15:58
doanacsmart :)15:58
Saviqand see how long that takes to complete whoopsie-upload-all, multiply by 1015:58
Saviqthere's your number15:58
elopiothanks Saviq and doanac.15:59
elopioSaviq: I'll mark the bug as incomplete waiting for it to happen again after doanac's tracing.15:59
Saviqtx15:59
dbarthhi again16:06
dbarthi updated silo 11 / line 21 to add another bugfix for the same target project16:06
dbarthcan i get a silo reconfig?16:06
dbarthsil2100 ^^ if still in your shift16:07
=== gatox is now known as gatox_lunch
robrudbarth, on it16:08
dbarththanks robru16:08
robrudbarth, you're welcome! Ok, it's done, go ahead with build16:09
dbarthcool16:09
* popey pokes davmor2 with hangout chat16:12
mhr3robru, can i get reconf of 014?16:13
robruyes!16:14
robrumhr3, alright, you are go for build16:18
mhr3robru, ty16:18
robrumhr3, you're welcome16:18
sil2100popey: thanks for the presentation, this design looks really nice16:19
robrumhr3, just to let you know, I *just* pulled the trigger on a unity8 publish job, so you'll have to rebuild unity8 in a couple hours once that fully lands & merges16:19
davmor2popey: so I can't repro that swiping either way which way triggered it for you?16:19
mhr3robru, sure, i know16:19
robruk16:19
popeydavmor2: lock phone, unlock phone16:21
popeysil2100: np16:21
robruslangasek, hey, I lost track of the landing rotation, is it my day today?16:26
slangasekrobru: I was just asking that myself :)16:27
slangasekrobru: was the rotation you, barry, stgraber?16:27
slangasekif so, I think it's stgraber's16:27
robruslangasek, yeah. barry did it friday. makes sense16:27
robruslangasek, we should document this somewhere ;-)16:27
slangasek(and sorry for not calendaring this up)16:27
barryyeah, a calendar would be nice :)16:27
barryhave fun with "every 3 other business days" in gcal :)16:28
robruyeah that sounds like a pain.16:28
robrubarry, on the other hand "every 3 other days" is pretty easy to do.... ;-)16:28
barryrobru: true.  i did that in my own canonical calendar, and then adjusted for business days until the end of june16:29
slangasekbarry: nah, I'll just do a SPREADSHEET16:29
robruslangasek, oh yes please, we need more spreadsheets ;-)16:29
slangasekI knew you'd approve16:29
robruslangasek, make sure you load it with scripts that query and poll other services, so we can push it to gdocs limit and have it go down constantly...16:30
barryslangasek: also make sure it uses some obscure @c.c address for us so we'll have no access and won't be able to make google's corporate login work for unknown reasons16:30
barry(monday is snark day)16:31
sil2100o/16:33
robrubarry, ugh, I just tried making my own calendar, but when I adjust each week, it doesn't adjust the ones after the one I adjusted, making the repeat almost totally useless.16:33
sil2100slangasek: is the rotation thing documented anywhere? Would be nice to know who's currently 'on'16:33
slangaseksil2100: no, that's the current discussion topic :-)16:34
robruslangasek, yeah could we just have like a wiki page for this?16:34
slangasekrobru: that would be fine.  You want to set one up?16:34
robruslangasek, yes! ;-)16:34
slangasekta ;)16:34
slangasekI clearly was overthinking this and should've just gone with a wiki page from the start16:35
=== Ursinha is now known as Ursinha-afk
sil2100slangasek, robru: set it up under citrain/ I guess?16:35
robrusil2100, yep, on it16:35
sil2100Thanks ;)16:35
sil2100Oh! Wait, actually...16:36
sil2100robru: https://wiki.ubuntu.com/citrain/LandingTeam <- maybe a section could be added here?16:36
sil2100Or you think a separate page would be better?16:36
robrusil2100, oh I already started a separate page16:36
slangasekoops, well, too late now, wikis are immutable16:36
sil2100Ok, let's link it to this page later on16:36
sil2100slangasek: :D16:36
robrusil2100, nah I can put it in there16:36
robrusil2100, slangasek : https://wiki.ubuntu.com/citrain/LandingTeam ok here's this week for now16:38
robruwe can expand it as we go16:38
slangasekrobru: thanks :)16:38
robruslangasek, thanks for not making a spreadsheet ;-)16:39
slangaseksil2100: this does kind of leave you with no relief, though, which wasn't quite what I had in mind16:39
slangaseksil2100: does the fact that stgraber+barry start 3h earlier help?16:39
slangasek(earlier than robru)16:39
robruslangasek, well, it was always that way, now it's just codified.16:40
slangasekright16:40
sil2100slangasek: hey, yeah :) Of course it's helpful, good for a beginning!16:40
robruslangasek, I was assuming that at some point some EU Foundations Team members would rotate in for sil210016:40
=== Ursinha-afk is now known as Ursinha
robrubrb, grabbing some breakfast16:49
sil2100ogra_: !16:59
sil2100ogra_: could you promote #83?17:00
* sil2100 noticed that he sent the e-mail by mistake without ogra_ pressing the promotion button yet17:00
ogra_heh, perfect timing to ask in the half time break :)17:00
sil2100:P17:00
sil2100Quick! Everyone is waiting for it already!17:00
sil2100The e-mail is ouuut!17:00
ogra_haha17:00
* sil2100 panics17:00
=== retoaded changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: retoaded | CI Train Status: #79 promoted | CI Train Support: US: robru, stgraber - EU: sil2100, Mirv | Known issues: -
ogra_promotion script running17:00
ogra_=== Image #83 Promoted ===17:01
* ogra_ goes back to the game17:02
sil2100\o/17:03
sil2100;)17:03
sil2100Have fun17:03
=== alan_g is now known as alan_g|EOD
sil2100ogra_: https://plus.google.com/109159869108744115904/posts/SzyTXh8jkzA <- for after the match ;)17:05
popeyyay!17:05
sil2100See you tomorrow o/17:12
robrumhr3, a ha, nice job merging 12 before building 14 ;-)17:18
robrubarry, you got 12 and 1717:23
robruoops17:23
robruI mean, bfiller you got 12 and 1717:23
bfillerrobru: thanks!17:23
robrubfiller, you're welcome!17:24
kgunnrobru: i got something happening i don't quite understand17:32
robrukgunn, what's up?17:32
kgunnrobru: so we built mir & its rdepends...but unity-mir wouldn't install, kept locking for old mir...so i said "i'll show you"...and force rebuild17:32
kgunnon unity-mir only, but then17:33
kgunnhttps://launchpadlibrarian.net/177724734/buildlog_ubuntu-utopic-i386.unity-mir_0.4%2B14.10.20140616.3-0ubuntu1_FAILEDTOBUILD.txt.gz17:33
kgunnit fails to build, looking for platform-api v2 ...but platform-api v2 is in that ppa!17:33
kgunnhttps://launchpad.net/~ci-train-ppa-service/+archive/landing-016/+packages17:33
robruhmmmm17:33
kgunnrobru: maybe it doesn't work how i think it works?...anyway...open to ideas17:34
robrukgunn, yeah that error message is confusing, usually it's caused by some other more distant dep being broken somehow17:34
robrutrying to remember how to troubleshoot that17:35
kgunnrobru: stranger still....it actually built just fine earlier this morning17:35
kgunnwith no complaints17:35
robrukgunn, yeah, could be something landed in between to break it17:35
kgunnrobru: force rebuild all ?17:36
kgunnshould i17:36
robrukgunn hang on17:36
kgunnok17:36
* kgunn is gonna go run/workout, bbiab17:36
* camako will take over from kgunn17:37
robrucamako, yeah, try a full rebuild, but I'm still looking at this17:39
camakorobru, ok will do17:39
elopioOnly three errors on #84 :D17:42
elopiothings are getting easier.17:43
=== gatox_lunch is now known as gatox
robrumhr3, you got 1817:45
mhr3thx17:46
=== greyback is now known as greyback|eod
ogra_elopio, oh, wow !!17:58
=== robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: robru | CI Train Status: #79 promoted | CI Train Support: US: robru, stgraber - EU: sil2100, Mirv | Known issues: -
=== robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: robru | CI Train Status: #84 promoted | CI Train Support: US: robru, stgraber - EU: sil2100, Mirv | Known issues: -
camakorobru, force_build failed.... same issue18:08
camakokgunn ^^18:08
robrubah18:08
elopioping robru. I'm testing silo 006 but with phablet-click-test-setup I get:18:09
elopiopull-lp-source: Error: Failed to download: https://launchpad.net/ubuntu/+archive/primary/+files/ubuntu-ui-toolkit_0.1.47+14.10.20140616-0ubuntu1.dsc: 404 Not Found18:09
elopiowhat's primary? shouldn't it use the path to the silo?18:10
robruelopio: phablet-click-test-setup? what?18:11
elopiorobru: anything. phablet-click-test-setup --click com.ubuntu.calculator;18:11
robruelopio: no, phablet-click-test-setup doesn't know anything about silos, it tries to download the tests from the archive. but they're not in the archive so it's only in the silo.18:11
Mirvelopio: edit phablet-click-test-setup and remove the line regarding basic_packages that tells about ui-toolkit. you can install the -autopilot .deb package from PPA instead.18:12
* Mirv waves good night18:12
Mirv(bug #1280279)18:12
ubot5bug 1280279 in phablet-tools (Ubuntu) "phablet-click-test-setup tries to download unity8 and ui-toolkit from main archives, failing when those are being tested" [Undecided,Confirmed] https://launchpad.net/bugs/128027918:12
robruelopio: I think you need to run phablet-click-test-setup before installing the silo contents. you'll have the older version of the tests but it'll test the new package18:12
Mirvor robru's version, run it before indeed18:12
robrumirv, thanks18:12
elopioMirv: thanks.18:13
robrumirv, elopio, depends if you're testing the tests themselves, or if you're testing the code. mirv's way tests the newest tests, my way runs old tests on new app code18:13
robrucamako: are you sure it's the same error? looks different to me, maybe I'm not looking at the right thing18:14
robrucamako sorry for the delay, infinity fixed it, should be working now18:29
camakorobru, yes it was the same error... Should I kick another rebuil_all?18:33
robrucamako: no18:34
camakorobru, last build failed for mir and unity-mir... So build those two then?18:38
robrucamako: no18:38
camako?18:38
robrucamako: those two failed waiting for platform-api, platform-api failed waiting for something else. platform-api needs to get fixed first18:39
robrucamako: sorry I'm doing like 10 things right now. What I'm being told is that doing a rebuild from CI Train won't fix this because that causes a new upload that will fail in the same way. You have to dig into the PPA and trigger the rebuild from there18:41
robrucamako: https://launchpad.net/~ci-train-ppa-service/+archive/landing-016/+build/6103560 so if you click retry from here, it should work18:41
robrubut wait18:42
robruinfinity-already did unity-mir18:42
camakorobru, in the morning everything built successfully18:43
camakobut we had package installation problems18:43
infinityunity-mir is fine now.  Retrying mir/armhf, but the failure there looked a bit more suspicious.  We'll see how it fares on a second go.18:44
camakoinfinity, do I need to start the build or you started already?18:47
infinitycamako: Retrying the build is saner than reuploading.18:48
infinitycamako: The build is in progress right now.18:48
infinityhttps://launchpad.net/~ci-train-ppa-service/+archive/landing-016/+build/610356018:48
camakoinfinity, thanks...18:48
infinityThe failure on this one was a failure to link, though, which may well be an actual bug, not a package skew issue.  We'll see.18:49
camakook18:49
infinityAnd same failure again.18:50
infinityCMakeFiles/mirprotobuf.dir/google_protobuf_guard.cpp.o: In function `void std::call_once<void (&)()>(std::once_flag&, void (&)())':18:50
infinity/usr/include/c++/4.8/mutex:779: undefined reference to `std::__get_once_mutex()'18:50
infinity/usr/include/c++/4.8/mutex:783: undefined reference to `std::__set_once_functor_lock_ptr(std::unique_lock<std::mutex>*)'18:50
infinity/usr/include/c++/4.8/mutex:790: undefined reference to `std::__set_once_functor_lock_ptr(std::unique_lock<std::mutex>*)'18:50
infinityCMakeFiles/mirprotobuf.dir/google_protobuf_guard.cpp.o: In function `__gthread_mutex_unlock':18:51
infinity/usr/include/arm-linux-gnueabihf/c++/4.8/bits/gthr-default.h:778: undefined reference to `std::__once_functor'18:51
infinitycollect2: error: ld returned 1 exit status18:51
infinitysrc/shared/protobuf/CMakeFiles/mirprotobuf.dir/build.make:153: recipe for target 'lib/libmirprotobuf.so.0' failed18:51
infinitymake[3]: *** [lib/libmirprotobuf.so.0] Error 118:51
* camako hasn't seen this error before... will look into it18:51
camakokgunn, ^^ .... cross compile works... has to do with cross vs native incompatibility... Dunno why built ok earlier tho..19:02
rsalvetirobru: can I get a landing for line 40?19:08
rsalveti*silo19:08
robrursalveti sure19:08
robrursalveti: you got 1919:09
rsalvetirobru: thanks19:09
robrursalveti: you're welcome!19:09
robrubrb, need to reboot19:14
kgunncamako: i'm back, gonna reboot real quick19:17
robrudamn  my system is just glitching out today19:31
slangasekinfinity: so, where'd you get to in this unity-mir investigation?19:37
slangasekI see that g++ 4.9.0-3ubuntu5 (depends: g++-4.8) is used for the build; could it be that g++-4.8 headers are incompatible with new libstdc++?19:39
infinityslangasek: s/unity-mir/mir/ I assume?  After making unity-mir happy (that was just version skew in the PPA), mir was FTBFS on armhf, which I punted to upstream.19:42
infinityslangasek: It's entirely possible the g++ headers are incompatible on ARM, worth looking into.19:43
infinityslangasek: Given that GCC only guarantees backward compatibility at runtime, not compile time, I wouldn't put it past them to have changed removed/mangled something.19:44
infinitys/changed//19:44
slangasekinfinity: right, mir.  Which upstream did you punt this to?19:46
infinityslangasek: camako and kgunn were discussing it above (ish).19:47
slangasekinfinity: so 'mir' upstream19:47
infinityslangasek: Right.19:47
slangasekinfinity: which is how I wound up back here. ;)19:48
infinityWhee!19:48
slangasekfwiw, __get_once_mutex() is bounded by #ifndef _GLIBCXX_HAVE_TLS19:49
slangasekwhich I'm pretty sure we have19:49
infinityslangasek: We certainly should.19:50
infinityslangasek: I'd done no investigation aside from highlighting the problematic lines in the build log.19:51
infinityslangasek: Is this being punted back to us as "your toolchain sucks, yo'?19:51
infinitys/'/"/19:52
slangasekinfinity: nothing so concrete; kgunn had just asked if gcc-4.9 had settled19:52
slangasekand this may well be fallout from that; trying to reproduce the problem now19:52
infinityslangasek: Yeah, has it?  I'd love to switch back. :P19:53
slangasekinfinity: no, you get an orderly transition of the C++11-using packages; talk to tvoss if you want to volunteer to help :)19:53
infinityslangasek: Ahh, so, we'll transition C++-11 libs first, then flip the default compiler again?19:54
slangasekyes19:54
* infinity nods.19:54
infinityThat shouldn't take long, in theory.  Unless spreadsheets slow us down. :P19:54
mhr3robru, ping?20:00
mhr3robru, can you try to just rebuild https://launchpad.net/~ci-train-ppa-service/+archive/landing-018/+build/6103541 pls?20:00
mhr3there's some super weird error20:00
robruchecking20:01
robruinfinity, slangasek hey guys, is this related ^^ looks similar to me20:01
mhr3is the new libstdc++ now built with 4.9?20:03
infinityrobru: That's the same error, yes.20:03
infinitymhr3: Yeah, it is.20:03
mhr3that explains it then20:03
mhr3robru, so i guess no need to rebuild it until there's a proper fix20:04
robrumhr3, yeah20:04
boikorobru: hi, I was looking at the update excuses, and there it says dialer-app was not considered, anything I should do?20:09
boikorobru: this is regarding landing-00120:09
robruboiko, yeah you should ping pitti about that: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/133036020:10
ubot5Ubuntu bug 1330360 in dialer-app (Ubuntu) "mark for language pack use" [Undecided,Fix committed]20:10
robruboiko, or I guess you could just add that one line to your debian/control like pitti wants, and then drop that block-proposed tag from that bug, and then republish20:10
boikorobru: it seems he filled the bug as an example, I don't think he really meant to block dialer-app, /me trying to avoid the trouble of having to republish20:12
boikorobru: as pitti is not around, I think it might be easier if I just add that tag to debian/control20:13
robruboiko, well it won't get through proposed as long as block-proposed is on the bug. so delete that tag and then it'll migrate. but make sure you talk to pitti about it, because you guys are just stepping on each other's toes now, it's not good communication20:13
robruyeah20:13
boikorobru: should I do anything on the silo? other than rebuilding dialer-app when I finish the changes20:13
robruboiko, hmm, nope. silo is fine. you just need to rebuild to get that new line in the package, then I'll re-publish.20:14
boikorobru: ok, should I also mark the change as fixing the bug?20:14
robruboiko, ... yes20:16
robruboiko, no wait20:16
robruboiko, http://bazaar.launchpad.net/+branch/dialer-app/revision/151 pitti pushed to your trunk already20:17
robruboiko, I don't know what the hell is going on. pitti made a "release" here: http://bazaar.launchpad.net/~phablet-team/dialer-app/trunk/revision/152 but that never made it into ubuntu20:18
slangasekrobru, infinity, mhr3: what is this '__once_functor'?  I don't find that in the /usr/include/c++/4.8/functional in the archive20:18
robruslangasek, never heard of it.20:19
robrubut I'm not a C++ guy, no idea20:19
slangasekok; I don't think we should assume this is related to the other mir failure, just yet20:19
slangasekoh, although std::__once_functor does appear in both build failures (it's just not the first failure, on the mir build)20:20
robruslangasek, well in both cases the build only failed on armhf, other arches built fine. so it seems like there's something wrong with just that arch20:20
robruboiko, don't rebuild anything, I'm going to drop that tag and let your package migrate.20:21
boikorobru: ok, thanks!20:21
dobeyrobru: the problem is new libstdc++ which is built against gcc 4.920:22
dobeyrobru: so things trying to link it go boom20:22
dobeyslangasek: ^^20:22
slangasekrobru: yes.  I'm looking now to see if the build failure is reproducible with a cross-build, given that none of the libstdc++s here show those symbols20:23
slangasekdobey: er, I'm well aware of the current state of the toolchains; "go boom" is not what is supposed to happen20:23
kgunnslangasek: mir cross compile was fine20:27
kgunni just tried native compile locally, and it go boom20:27
kgunnon top of devel-proposed20:27
dobeykgunn: because you have libstdc++6 4.9, and gcc 4.8, i guess20:28
dobeythat is what happened in the PPA for unity-scope-click silo anyway20:28
slangasekdobey: yes, and *that's supposed to be supported*; we need to get to the bottom of why this is causing a build failure20:29
dobeyslangasek: the problem is that it has libstdc++6-4.9 and libstdc++4.8-dev, but not libstdc++6-4.820:29
dobeyafaict20:29
kgunnyeah...that'd make sense20:29
slangasekhmm20:30
=== olli_ is now known as olli
dobeyseems libstdc++-4.8-dev depends only on "libstdc++6" which i guess is pulling -4.9 instead of -4.8 for some reason20:31
slangasekthat could be; though I still don't see these symbols in any version of libstdc++20:31
slangasekyes, it only depends on libstdc++6 because that's supposed to work20:31
slangasekthere is no -4.8 version of the library anymore20:31
kgunnslangasek: now's probably not the time to be asking such things...but how come there's no 4.8 version available to downgrade to ?20:34
* kgunn figures there's some special reason20:34
slangasekkgunn: because library transitions are one way20:34
slangasekand the soname didn't change20:34
dobeyslangasek: yay templates20:34
slangasekand it didn't change because the ABI didn't change20:34
slangasekdobey: templates don't generate undefined references20:35
kgunnslangasek: ah got it....ABI didn't change _allegedly_ :)20:35
slangasekkgunn: right ;)  and from everything I'm seeing so far, this failure is not due to an ABI chnage20:35
slangasekchange20:35
dobeyugh, the bzr branch just has gcc tar.xz inside it :(20:36
boikorobru: so, will the migration happen on its own now for dialer-app?20:49
robruboiko, it should as far as I know20:49
boikorobru: ok20:49
robru(which, I should clarify, isn't very far)20:49
boikorobru: :)20:49
boikorobru: update excuses still say it won't migrate because of that bug20:50
boikorobru: but I don't know much about this either20:50
robruinfinity, regarding ^^ 'block-proposed' tag on a bug, is it enough to delete that tag, or does anything else special need to happen?20:50
slangasekrobru: rather than closing the bug?20:56
slangasekremoving the tag will automatically have the effect, but I'd be wary of doing it this way20:56
slangasekas that implies the bug that someone marked as a blocker hasn't been fixed yet20:57
robruslangasek, right, well technically it hasn't.20:57
robru;-)20:57
robrubrb, phone20:58
robruslangasek, sorry21:01
robruslangasek, so the situation is that, pitti did a push to trunk + manual upload (fine) but then blocked his manual upload with this bug, and now that is blocking boiko, who also wants to do a release right now21:02
robruslangasek, it was poorly coordinated, everybody stepping on everybody's feet, so I figured I'd just unblock and let boiko go ahead. the only problem is that translations in dialer-app will regress for an image or two, but it'll sort itself out after a couple days, didn't seem worth blocking to me21:03
robruslangasek, so the bug should stay open, because this translation issue is real, but I didn't want to block boiko's landing21:03
robruslangasek, but https://wiki.ubuntu.com/ProposedMigration doesn't explain how to unblock such a bug, you say removing the tag is enough, but it hasn't migrated yet21:08
=== robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #84 promoted | CI Train Support: US: robru, stgraber - EU: sil2100, Mirv | Known issues: -
infinityrobru: Removing the tag is enough.21:32
infinityrobru: proposed-migration just hasn't run (or completed) since you removed the tag.  Note the datestamp at the top.21:33
robruinfinity, ok, thanks. thought it ran every half hour or so21:34
infinityrobru: It runs whenever proposed changes, which is a bug/misfeature I'm going to fix.21:34
infinityrobru: But it also sometimes runs a long time, if a big transition is confusing it.21:34
robruah21:34
infinityrobru: Not sure if the current delay is the former or the latter, just got back from lunch and I'm multitasking in a meeting.21:34
robruinfinity, ok well this isn't a huge rush if you're busy21:35
robrujust whenever ;-)21:36
* infinity nods.21:36
cjwatsonrobru: live logs are in http://people.canonical.com/~ubuntu-archive/proposed-migration/utopic/ so you can tell the difference between "hasn't run for ages" and "currently in the middle of massive run"21:45
cjwatsonin case that helps21:45
robrucjwatson, it does, thanks21:45
robrucjwatson, err, except that 404s21:45
robruhttp://people.canonical.com/~ubuntu-archive/proposed-migration/log/utopic/21:45
robru;-)21:46
cjwatsonEr right sorry21:46
cjwatsonThat one21:46
cjwatsonLooks like the latest run finished a minute ago21:46
robruboiko_, ah, excellent ^ dialer-app is valid now21:46
cjwatsonAnd migrated click-apparmor and dialer-app21:47
cjwatson34 minutes between starts of last two runs, sassenfrassen, must prod mvo to finish getting ftparchive source caching deployed21:48
boiko_robru: cjwatson: thanks! :)21:51
robruboiko_, you're welcome21:53
slangasekrobru, kgunn: I can't reproduce this mir ftbfs at all on the utopic porter machine23:23
slangasekI'm giving it a retry23:23
slangasek(tested with an up-to-date porter chroot on shedir, using both the mir from the archive and the one from the ppa)23:24
slangasekrobru, kgunn: ah - I believe this was an issue fixed upstream in gcc-4.9 between 4.9.0-6 and 4.9.0-7, and doko hadn't flagged it because it was part of the upstream update rather than anything he knew broke mir specifically23:33
slangasekso it looks like it's fixed as of today, and armhf was the only arch FTBFS because it's the slowest to build23:33
slangasekI can certainly confirm that the latest libstdc++6 does have the symbols in question23:35
infinityslangasek: That doesn't make much sense, as none of the arches built against 4.9.0-7, since it's in proposed.23:36
robruslangasek, so a rebuild should work but it was just slightly out of date earlier today?23:36
infinityslangasek: Unless the bug only existed on armhf in the first place.23:36
robruslangasek, yeah the silos have -proposed disabled23:36
slangasekinfinity: ah; could be arch-specific, to be sure23:37
slangasekrobru: but in that case, see previous conversation with infinity re: -proposed should be enabled23:37
josharensoncjohnston, is there an easy (correct) way to add a canonistack machine to the ci lab vpn?23:37
infinityAnyhow, I have a proper reproduction env here, I'll try a build without proposed, then enable proposed and upgrade the toolchain and try again.23:37
robruslangasek, is that in this channel? I don't see it23:38
infinityrobru: You and I very briefly brought it up on #distro.23:38
robruinfinity, I didn't conclude from that exchange that I was supposed to enable -proposed23:39
robruthought you were just making an observation23:39
infinityrobru: Well, that was more of a general process issue, in that proposed should always be enabled.  There was no indication that it would fix THIS issue.23:39
slangasekrobru: you shouldn't immediately enable it on infinity's say-so ;), but this is an inconsistency with how we do all builds for the archive23:39
slangasekand in this case it turns out the inconsistency he noticed stands a good chance of being the cause of the build failures23:40
robruslangasek, so, to be clear, are you telling me to enable proposed for the silos? Because that's a thing I can do if necessary.23:41
infinityThe uniqeuness in snowflakery of ci-train (and airline) customers needs to be minimized, especially as more and more people are asked to use it.23:41
slangasekrobru: if you could do it for *this* silo, at least temporarily, that should let us unblock23:41
infinityslangasek: I'm verifying that claim right now, BTW.23:42
slangasekrobru: and then we should get buy-in from the rest of the team about making this change more generally/permanently23:42
robruslangasek, can you explain to me why this is just a temporary change and not a permanent one for all silos? I never understood why -proposed wsan't enabled originally or what the implications are23:42
robruok23:42
slangasekrobru: because I don't know who set it up this way initially and don't want to be in a revert war :)23:42
robruslangasek, heh, ok, well 16 now has proposed enabled, should I start a rebuild?23:43
slangasekrobru: yes, please!23:43
infinityrobru: reTRY, not rebuild.23:43
infinity(Assuming rebuild means what I think it means)23:43
robruright, that one23:43
slangasekinfinity: and it looks like gcc-4.9 proposed-migration is merely held up by the lack of gerbil chow for the powerpc buildds23:44
robruslangasek, brb, off to buy some more gerbil chow23:44
infinityslangasek: I could easily move that build to sagari, I hadn't expected there to be any urgency.23:44
slangasekrobru: this also impacted the unity-scope-click build failure, so when you have a chance you probably want to do the same for that silo23:45
slangasekinfinity: it's 14h in already, is it worth it now?23:45
robruoh right23:45
robrubuh, neither mhr3 nor camako are around to ping. ok, time for an email23:46
infinityslangasek: It might be close.  Hard to say.  But the whole build end-to-end is under 2h on sagari.23:46
slangasekhmm, what do you need to ping them for?23:46
infinityTurns out that GCC parallelises REALLY WELL.23:46
robruslangasek, to let them know that their failed builds are being retried23:46
infinityrobru: Can't they just be pleasantly surprised when it all works? :)23:47
infinityI certainly don't tell people every time I retry a build in the distro.23:47
slangasekinfinity: I'd say leave it alone, it's not critical-path if we're already reconfiguring for -proposed23:47
infinityWhich is often.23:47
robruinfinity, well in theory they're just twiddling their thumbs waiting for this...23:47
slangasekrobru: ah, right - I'm with infinity, let them find out in the morning ;)23:47
robruinfinity, well this is quite exceptional from my perspective. usually when builds fail it's because of upstream breakage, not distro breakage23:48
robru"usually when *CI Train* builds fail..."23:48
infinityslangasek: I do believe my test build with upgraded libstdc++ is past the point of anger, so your eyeball guess looks correct.23:48
infinityrobru: Builds fail for a lot of reasons.  The reason I got involved in this at all was a completely different issue, for instance.23:49
robruinfinity, right, and that original issue was also not caused by the upstream ;-)23:49
infinityrobru: And sometimes someone clever comes along and retries a build because they know it'll succeed now, and sometimes it's fundamentally broken and I expect the uploader to fix it, but I never ping in the former case, I just let it happen.23:49
infinityrobru: Up to you, of course, but this process already has too much formality in it.23:50
robruinfinity, well when people ask me to fix something, I consider it polite to let them know that it's been fixed.23:50
robrueven if I didn't fix it myself (thanks guys)23:50
infinityI'm mildly concerned about this silo now being half-proposed and half-not, but if it's not accidentally involved in a transition or anything, it shuld be fine.23:50
robruinfinity, what kind of transition? it's mir 0.3.0 release, which is a fairly major point release for em23:51
infinityrobru: No, I mean if other bits they depend on are transitioning.23:51
infinityrobru: Then armhf would depend on the new -proposed libs, and !armhf wouldn't.23:51
robruinfinity, can we check that? I'm not familiar with what libs mir depends on, let alone what's transitioning in proposed right this second23:52
robruinfinity, are you suggesting that a complete rebuild would be better? ;-)23:52
robrureupload23:53
infinityslangasek: FWIW, the last gcc-4.9 build on an Xserve was 16h5m, so looks like adare has less than 2h to go.23:53
infinityrobru: Nah.  Britney will yell at us if it's broken.23:53
robruinfinity, ok great23:53
infinityrobru: When you copy this silo to -proposed, give me a poke.  There's an ABI bump in libmirserver, and I'll need to apply overrides.23:57
robruinfinity, ok, well I guess that'll be tomorrow, upstreams need to do testing before I'll publish23:58
* infinity nods.23:58

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!