/srv/irclogs.ubuntu.com/2015/10/26/#ubuntu-ci-eng.txt

=== balloons is now known as Guest90681
=== chihchun_afk is now known as chihchun
Saviqtrainguards, morning, what need I do about https://requests.ci-train.ubuntu.com/#/ticket/445 ?07:53
Saviqsil mentione binNEW, but not sure why?07:55
pete-woodstrainguards: morning folks, I just tried to do a dual vivid+xenial landing, and I think I just ended up with both going into the overlay PPA07:55
pete-woodsshould I have done something different for the config for the silo?07:55
robruSaviq: looks like you just need a core dev to ack & publish07:58
* Saviq looks around07:58
Saviqseb128, I can has core-dev ACK on https://requests.ci-train.ubuntu.com/#/ticket/445 please?07:59
robrupete-woods: yep, you set the destination to the overlay so that's where the packages went. You'll need a core dev to copy those to xenial now07:59
seb128Saviq, hey, looking, not a trivial one ;-)08:00
pete-woodsrobru: so if I wanted the overlay PPA for vivid, but not for xenial, what should I have done?08:00
robrupete-woods: leave dest ppa field blank because that only controls where the primary series goes. Vivid copies always go to overlay08:01
pete-woodsrobru: right okay, that's good to know, thanks :)08:01
robrupete-woods: you're welcome!08:01
pete-woodsmight I ask a passing core-dev if they could copy my mistaken package from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+packages?field.name_filter=cmake-extras&field.status_filter=published&field.series_filter=xenial08:03
seb128Saviq, the summary is unreadable :-/08:03
pete-woodsinto xenial?08:03
seb128it's like over a full screen of red bold text08:03
seb128wth08:03
robrupete-woods: it may be helpful to think of it this way: in a dual silo, everything is focused on the primary series. Only the primary series gets tracked in migration, only the primary series let's you set the destination, etc etc. The vivid copies of the packages are sort of just bolted on and hard coded to always go to overlay08:03
Saviqseb128, you mean the landing description?08:04
seb128Saviq, yes08:04
seb128https://requests.ci-train.ubuntu.com/#/ticket/44508:04
seb128that page08:04
pete-woodsrobru: yeah, that makes sense now, could have sworn this behaviour has change from the past, though08:04
Saviqseb128, it's a behemoth silo, I tried my best08:04
seb128is there a pointer somewhere to the diff to review?08:04
pete-woodsanywa, I know what to do now08:04
robruseb128: second from top there's a link to the artifacts08:05
seb128would be nice if there one concatenated diff08:06
seb128and if the page was not only red text08:06
robrupete-woods: nope, vivid copies were always hardcoded to go to overlay. The only thing that changed was that wily copies also went to overlay for a time08:06
Saviqseb128, re: not trivial, the -gles reworks are robru's authorship, replacing the need to set changelog and silo in debian/rules08:06
Saviqbut will only work in silo (or when you get the source yourself)08:06
seb128that feels hackish08:06
robruseb128: it is hackish but it has reduced the effort required to maintain gles in real terms and also had slangasek 's approval08:07
seb128then slangasek should publish it :-)08:08
robruSaviq: OK you need to wait 8 hours for Steve to wake up08:08
seb128did he state somewhere in public that he was ok with those?08:08
seb128like in a irc log I can read08:08
robruseb128: it was in emails but I can't remember if it was on a list or not08:09
Saviqrobru, I got the thread you started after that, don't think Steve weighed in in that thread though08:10
pete-woodsseb128: if you're feeling super generous could you push my mistaken upload to the overlay xenial series into xenial for real when you've finished reviewing Saviq's mega request? (https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+packages?field.name_filter=cmake-extras&field.status_filter=published&field.series_filter=xenial)08:11
seb128pete-woods, hey, ok, queuing to have a look next08:11
robruseb128: Saviq ugh yes it was private irc where he approved it08:11
robruseb128: anyway I have no proof of Steve's approval but just realized that this dramatically reduces the amount of maintainance effort on the gles packages as they don't need to point debian/watch at a new ppa every time they do a release.08:13
seb128Saviq, robru, diff for other things is fine, I'm happy to press the publish button if you take responsability to deal with potential issues/discussions following the gles changes08:14
robruseb128: OK08:14
Saviqseb128, ACK08:14
seb128Saviq, there you go ;-)08:16
Saviqthank you08:16
seb128Saviq, nice to see those changes coming btw!08:16
seb128yw08:16
Saviqseb128, indeed, shame it took so long to land...08:17
Saviqfreezes, releases, everything that could delayed it08:17
seb128Saviq, failed :-/08:20
Saviqhuuuh08:21
Saviqaah08:21
Saviqrobru, help ↑08:22
Saviqrobru, the previous release never migrated https://launchpad.net/ubuntu/+source/unity808:22
robruseb128: oh just hit ignore, that's a bug on silos transitioned from wily to xenial08:23
Saviqbut we did rebuild after that landed08:23
Saviqoof08:23
seb128"IGNORE_VERSIONDESTINATION"?08:23
robruseb128: yeah08:23
seb128let's try that08:23
Saviqyou can even see in https://ci-train.ubuntu.com/job/ubuntu-landing-022-2-publish/46/artifact/unity8_packaging_changes.diff that the version was there before :)08:24
robruYeah08:24
robruSaviq: most likely the last release was to wily overlay. For some reason xenial-proposed is a bit backed up08:25
Saviqrobru, yup08:26
Saviqrobru, does train not push to https://code.launchpad.net/~ci-train-bot/unity8/unity8-ubuntu-wily-proposed any more?08:36
Saviqonly to silo branches?08:36
robruSaviq: right. It's the same branch though...08:37
Saviqrobru, ok, I didn't get a silo branch (didn't build when you added that), but I'll manage ;)08:37
robruSaviq: oh awesome08:38
robruSaviq: I can push something manually hang on08:38
Saviqrobru, oh if you can that'd help a bit08:39
robruyeah just a minute to whip something up08:40
robruSaviq: ok I started a mass-push of all branches currently in the train. could take a while until silo 22 shows up: https://code.launchpad.net/~ci-train-bot08:51
Saviqrobru, great, thanks08:51
robruSaviq: you're welcome!08:51
robruoh crap, I hard-coded all the branches to be labelled 'xenial', hopefully that doesn't confuse too many people (any subsequent builds will have correct branch names anyway) ¯\_(ツ)_/¯08:53
robruSaviq: ok 22 is there08:54
Saviqrobru, thankski08:56
robruSaviq: you're welcome08:57
robruSaviq: ah and I've just noticed that train publication is broken, let me fix that...08:57
Saviqrobru, check out this trick you just made possible https://requests.ci-train.ubuntu.com/#/ticket/564 ;)08:59
robruSaviq: oh god what now08:59
Saviqrobru, while I wait for silo 22 to publish, I can use it to seed my new silo ;)09:00
Saviqit == the branch09:00
robruSaviq: how did you do that?09:00
Saviqrobru, https://code.launchpad.net/~ci-train-bot/unity8/unity8-ubuntu-xenial-landing-022/+merge/275672 ;)09:00
Saviqrobru, packages will be in proposed already, so it's just about the trunks09:00
Saviq(or overlay for that matter)09:01
robruSaviq: packages aren't in proposed yet ;-)09:01
Saviqrobru, yeah, note the "will" be ;P09:01
robruSaviq: you can just force-merge the silo to get the same effect but you lose migration tracking that way09:01
Saviqrobru, I'm more interested about conflicts for now09:01
Saviqrobru, yeah, won't do that in case it's blocked in proposed forever09:02
jgdxrvr, let me know if you have questions about that silo 39.09:06
rvrjgdx: Ok09:06
robruSaviq: *whew* ^^ fixed publishing09:17
Saviq:)09:28
sil2100jibel, davmor2, ogra_, popey: hey, if you guys are not travelling, meeting ;)09:31
Saviqrobru, bug in train: http://people.canonical.com/~ubuntu-archive/proposed-migration/xenial+vivid/update_excuses.html#unity8 (note the xenial+vivid)09:39
seb128pete-woods, copied09:39
robruSaviq: heh, yep, just fixed that in trunk but probably won't roll it out until tomorrow09:39
Saviqack :)09:39
pete-woodsseb128: awesome, thanks!09:39
seb128yw!09:40
jibelsil2100, I was in another meeting09:43
sil2100jibel: ok, no worries, we can sync on IRC if needed09:44
=== _morphis is now known as morphis
morphissil2100: when using citrain currently I see:10:07
morphisThe following packages will be REMOVED:10:07
morphis  ubuntu-touch ubuntu-touch-session unity8 unity8-common10:07
morphisis that expected?10:07
morphisit is with silo 13 which just contains an updated ofono package10:08
jibelmorphis, did you install another silo with these packages previously?10:08
morphisjibel: no10:08
morphisit's the most recent rc-proposed image + silo 1310:08
morphisjibel: http://paste.ubuntu.com/12968947/10:09
jibelmorphis, looking10:11
jibelrvr, can you confirm that 'silent mode' switches are out of sync between the indicator and system-settings on latest rc-proposed?10:12
rvrjibel: Checking10:12
rvrjibel: Yes10:14
rvrSilent mode active in indicator, off in System Settings10:14
jibelrvr, k, I'll file a bug10:14
jibelnot sure when it regressed10:14
jibelrvr, any idea of a silo that could have broke it?10:15
rvrHmm10:15
jibelmorphis, no problem *without* citrain10:15
jibelmorphis, trying with citrain now10:16
rvrjibel: Related to indicator-sound, we had silo 55 with mpris controls, but I don't think that touched silent mode switch10:16
jibelmorphis, and I confirm that with citrain it removes unity810:21
jibelsil2100, ^ any idea?10:21
sil2100jibel: sadly, no, I don't have any knowledge or experience of the citrain commandline tool10:23
jibelmorphis, as a workaround for the moment, you can install the silo manually. switch your device rw, add the corresponding entries to sources.list and pin the silo higher than the overlay10:24
morphisjibel: yeah, currently looking at citrain10:25
morphisjibel: http://paste.ubuntu.com/12969030/10:25
morphiswent through fine now10:25
rvrThe following packages will be REMOVED:10:26
rvr  ubuntu-touch ubuntu-touch-session unity8 unity8-common10:26
rvrArgh10:26
morphisjibel: adb shell SUDO_ASKPASS=/tmp/askpass.sh sudo -A apt-get -o Dir::Etc::SourceList=/dev/null update is the faulty line10:26
morphisrvr: edit citrain and drop -o Dir::Etc::SourceList=/dev/null from the apt-get update line10:26
jibelmorphis, yeah but I don't remember the purpose of this line10:28
morphisjibel: looks like that is already fixed10:28
morphisjibel: it only fetches updates from the silos10:28
morphisnot from the archive10:28
sil2100ogra_: hey, you around for some package publishing? :)10:29
morphisjibel: robru already fixed this with https://bazaar.launchpad.net/~phablet-team/phablet-tools/trunk/revision/34510:29
robrumorphis: jibel please don't edit the script just install the latest version from the ppa10:30
robrurvr: ^10:30
rvrrobru: Ok10:31
robruOoh10:31
jibelrobru, I don't use citrain :)10:31
jibelrobru, is the patch released?10:32
robrujibel: the fix is released in xenial only. If you're using anything prior to that you can get it from either phablet-team/tools or sdk ppa10:34
jibelrobru, I'm on xenial10:34
robrujibel: the fix just landed in xenial 4 minutes ago ;-)10:35
jibelrobru, heh :)10:35
robrujibel: i dunno why it was stuck in proposed so long, i published it last week10:36
* rvr is in wily10:39
jgdxrvr, bbl—in two hours ca.10:40
rvrjgdx: Ack10:41
jibelrvr, so silent mode switch in system-settings does nothing10:43
rvrjgdx: ^10:44
rvrjibel: I'm checking in stable10:44
rvrjibel: Oops10:45
rvrjibel: It's also broken in stable10:45
rvrjibel: Silo 4910:46
rvrjibel: sound-silent-mode-handling https://trello.com/c/y5CFR6eY/2349-452-ubuntu-landing-049-ubuntu-system-settings-kenvandine10:46
jibelrvr, how did it pass testing? There is an explicit test for that10:47
rvrjibel: Yes, and I marked it as  passed10:47
rvrjibel: I don't know whether that's the culprit, but seems related10:48
jibelrvr, it looks like the silo you're testing contains the fix https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/fix-sound-ap-regression/+merge/27503810:49
rvrOh, I didn't finish installing the ppa10:50
rvrI will check it then10:50
rvrNo bug attached10:51
rvrjibel: Silo fixes the sync between indicator and System Settings, indeed10:57
rvrseb128: Do you know which silo introduced the sound regression?10:59
rvr-                property variant silentMode: action("silent-mode")10:59
rvr20                 property variant highVolume: action("high-volume")10:59
rvrSo it was the one that I tested11:00
rvrjibel: It was my fault11:00
=== oSoMoN_ is now known as oSoMoN
popeyis silo 22 going to land sometime soon? :) (I have a conf at the weekend, wanted to try and demo it) :D11:16
jgdxjibel, don't know how it wasn't picked up in manual testing, but the automated test failed as well and noone noticed.11:17
jgdxthough, our suite saw many many spurious failures at that time, so it was easy to miss11:20
* jgdx really bbl11:22
jibeljgdx, yeah, there is a test in our regression testsuite and the tester marked it as passed. It's clearly a failure on our side, I'll talk to him.11:23
rvrpopey: ping11:25
popeyrvr, hello11:26
rvrpopey: Do you know when if music app being updated for mpris controls?11:26
rvrs/if/is/11:26
popeyHeh11:27
ahayzenrvr, yes, we are working on it ;-)11:27
ahayzenwaiting for the media-hub and indicator-sound bugs to be fixed first :-)11:27
rvrahayzen: It should land for OTA711:27
ahayzenrvr, it can't too many bugs at the moment in the background-playlists implementation11:27
popeyit needs fixing in the platform _first_11:27
rvrahayzen: Are you waiting for ready-for-testing silos?11:28
ahayzenrvr, i believe Jim has another one WIP, but i would need to check with him if any are ready11:28
ahayzensilo015 looks possible, but i need to link music-app to its new commands to totally test (which i'll do when back from lectures later :-) )11:29
rvrahayzen: Ok, I will test silo 15 after I'm doing with the current one11:30
rvrI'm done11:30
ahayzenrvr, cool, not sure if Jim has any mini-apps to prove that the new command works or is faster11:31
rvrahayzen: popey: Can you coordinate with Jim?11:32
popeyrvr, we are and have been for some time11:32
rvrGreat11:32
ahayzenyup :-)11:32
popeyWe keep getting asked about mpris in music app as if _we_ are the blocker here.11:32
ahayzenhehe11:32
popeyWhich most certainly isn't the case.11:32
rvrpopey: Sorry, I understood that after the indicator sound landed, only music app update was required11:33
popeyYeah, a few people assumed that :)11:33
ahayzenhah11:33
* ahayzen has a list of issues :(11:33
popeyFact is, if we gave you the in-progress branch for music app, you'd reject it from QA perspective.11:33
popeyI don't think mpris should have landed _at_ _all_ until music issues were fixed11:34
popeybut that's just me :)11:34
ahayzenpopey, there is work in the scopes which needed it ;-)11:34
rvrpopey: Yeah, I try to test it and it was a failure11:34
popeyYeah, it's big and invasive.11:34
rvrpopey: The mpris silo had four or five failures11:34
popeyGlad ahayzen and jim are working on it.11:34
popeyerk11:35
popey:)11:35
rvrAh, the scopes too11:35
popeyfun times :)11:35
ahayzen\o/11:36
rvrHmm11:36
rvrsil2100: ping11:42
sil2100rvr: pong11:43
=== _salem is now known as salem_
rvrsil2100: Tomorrow is string freeze. Does it make sense to delay to Wednesday the language export, or to make a new one?11:45
sil2100rvr: I think we can make a new one on Wednesday11:45
sil2100Anyway, another auto-export will happen next week anyway11:46
rvrsil2100: I still wish more frequent exports :(11:47
sil2100For rc-proposed I guess we could have that, since the exports take like 5 minutes anyway11:48
sil2100But for now we can poke manually11:48
jibelsil2100, once a day is probably overkill but at least one on feature freeze day would be good.12:02
sil2100I originally wanted the syncs to happen on Wednesdays, so after FF, but I remember pitti had some concerns12:04
sil2100But those might have been related to time needed for the exports to happen12:04
sil2100(which is minimal here)12:04
jibelsil2100, lets freeze a day earlier ;)12:05
=== xavigarcia is now known as xavigarcia_lunch
Saviqtrainguards, qtmir won't migrate in xenial (bug #1510067), I'm gonna force merge&clean in silo 22 and skip the release to xenial, unless you think I shouldn't?12:22
ubot5bug 1510067 in qtmir (Ubuntu) "qtmir rebuild fails with "assertion fail ../../bfd/elf32-i386.c:5245"" [Undecided,New] https://launchpad.net/bugs/151006712:22
sil2100Saviq: hm, I think +1 on force-merging12:31
sil2100As long as you'll keep track of that it's fine with me12:31
Saviqyeah I will12:32
=== alan_g is now known as alan_g|lunch
=== xavigarcia_lunch is now known as xavigarcia
bfillersil2100: how do I change silo 48 to xenial+vivid? it was pre-existing and using wily+vivid13:03
sil2100bfiller: hey! You need to reconfigure it to xenial+vivid on bileto and then I'll do a binary copy of your wily packages to xenial13:04
sil2100bfiller: was it ready for release?13:04
bfillersil2100: no not yet13:04
bfillersil2100: need to rebuild it first and finish test13:04
sil2100Then I think a reconf to xenial+vivid and a rebuild of all packages would suffice, I'll remove the wily binaries then13:05
bfillersil2100: thanks13:05
jhodappjibel, hey, I had emailed you a few months ago about getting some non-autopilot integration tests running for media playback...have you learned anything more about who I would need to talk to in order to get these tests automated?13:09
bfillersil2100: seems builds are failing, out of disk space: https://ci-train.ubuntu.com/job/ubuntu-landing-048-1-build/72/console13:10
jgdxsil2100, +2 on that, https://ci-train.ubuntu.com/job/ubuntu-landing-047-1-build/43/console13:11
jgdx“mktemp: failed to create directory via template '/tmp/debsign.XXXXXXXX': No space left on device”13:12
sil2100Argh, again13:12
sil2100On it13:12
jgdxthanks!13:12
sil2100hmm, not sure if this will help, could you guys check?13:13
sil2100The instance seems to have some size issues, I already see that there's not too much disk space available in overall13:14
jgdxcheck wat13:14
sil2100The disk that has all the pbuilders is like 10G, which seems really not enough13:14
sil2100jgdx: check if rebuilding now works13:14
jgdxack13:15
jgdx!build 4713:15
jgdx:'(13:15
jgdxokay, in work13:16
jgdxsil2100, failed13:21
jgdxnew error msg but same symptom13:21
sil2100hmmm13:22
bfillersame with me13:22
sil2100uh13:23
jgdxhttp://i.imgur.com/ji1pen2.png13:26
=== Guest90681 is now known as balloons
Trevinhotrainguards, can I do a direct push to lp:unity and lp:unity/wily  just to make a release (bump version numbers, add changelog...). But I don't want to release that on distro (at least, not yet and not in wily)13:44
TrevinhoI mean, I want do do an Upstream only release, with new tarball and such...13:45
Trevinhosil2100: maybe you know ^ ?13:50
sil2100Trevinho: hey!13:50
Trevinhosil2100: hey13:50
sil2100hmmm... why would you want to do an upstream release without releasing it to the archive?13:50
sil2100I mean, well, it poses some problems in the current model13:50
Trevinhosil2100: because I don't want to do an "SRU" for wily13:51
sil2100As normally everyone expects that trunk == release13:51
TrevinhoI just want to close the 7.3.3 gate move all the bugs waiting love there to the 7.4 milestone and release a tarball13:52
Trevinhobut i wanted that to be on the wily branch, not only on the xenial one13:52
TrevinhoAnd if we'll do an SRU to wily later, archive and upstream will sync again13:53
sil2100hm, as said, I would personally prefer only doing releases when an actual release happens, but in the CI Train world we leave branch management to upstreams13:55
sil2100So I guess you can do that, but it would confuse me personally13:55
Trevinhomh, ok... All that I don't want is that to break anything13:55
Trevinhosil2100: I mean, if the changelog in upstream is newer than the one downstream13:56
sil2100Trevinho: you'll get a warning, nothing to worry about13:57
Trevinhook thanks13:57
=== alan_g|lunch is now known as alan_g
=== chihchun is now known as chihchun_afk
pstolowskihello trainguards, i've recurring problem with silo 8 - No space left on device14:09
sil2100pstolowski: hey, yeah, it's a known issue, looking into that in a moment14:10
pstolowskisil2100, ack, thanks14:10
morphissil2100, robru: something seems to be really flawky with the citrain builds: https://ci-train.ubuntu.com/job/ubuntu-landing-052-1-build/64/console14:34
morphistried five attempts but all failed: first because of no space, second cause of package upgrade, after that they fail with some jenkins errors14:35
sil2100Yeah...14:35
sil2100Poking IS/webops14:38
sil2100Since this is something I can't help with, as now jenkins jobs fail running at all14:38
=== sil2100 changed the topic of #ubuntu-ci-eng to: Train trouble? ping trainguards | CI problems? ping cihelp | Train: http://bit.ly/1hGZsfS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: CI Train jenkins has disk-space issues
rvrjgdx: Approving silo 39.14:47
jgdxrvr, thanks.14:47
morphissil2100: ok14:58
sil2100Webops are on it, they're trying to make more space14:59
sil2100For now they freed up some but this might not be enough14:59
sil2100morphis, bfiller, pstolowski: could you guys re-try your builds?15:01
pstolowskiok15:02
sil2100Webops moved the pbuilder stuff to persistent storage, symlinking to the original place, want to see if it didn't break anything15:02
morphissil2100: running again15:02
bfillermterry: mind publishing silo 23?15:16
Saviqcihelp hey, can we please switch unity8-ci job to vivid and xenial? thanks15:16
mterrybfiller, let me look15:16
mterrybfiller, done ^15:21
bfillermterry: ty15:21
sil2100\o/15:24
sil2100mterry: can I ask you for some other publishings? :)15:24
mterrysil2100, sure15:24
sil2100mterry: https://requests.ci-train.ubuntu.com/#/ticket/519 :)15:24
mterrysil2100, why no QA on an SRU?15:25
* mterry is often confused about what needs QA15:25
sil2100mterry: it's a non-touch package, we only do QA sign-off for touch projects15:25
sil2100(non-touch packages)15:25
mterrysil2100, ok15:25
sil2100SRUs get the QA in the SRU queue :)15:26
mterrysil2100, fair...15:26
sil2100morphis, bfiller: the train working fine for you guys?15:28
bfillersil2100: doesn't seem to be working correctly for silo 48.. not seeing anything building on the ppa15:29
jgdxsame for 4715:29
morphissil2100: still building :)15:29
bfillersil2100: stuck on "preparing packages"15:29
bfillersil2100: and silo 23 which mterry published seems to be stuck on status: publishing15:30
dobeyrvr, jibel: can we have pay-ui in the qa review queue before the pay-service silo? this way the pay-ui change can be tested against the current pay-service, and we can get it in the store so that the new pay-service silo will then get tested against the new pay-ui too15:32
rvrdobey: Sure15:32
sil2100bfiller: looks like it moves ;)15:32
dobeyrvr: great, thanks15:32
jgdxsil2100, https://ci-train.ubuntu.com/job/ubuntu-landing-047-1-build/47/console15:34
jgdxis that still the space issue?15:34
fgintherSaviq, We're still in the process of getting builds setup for xenial. I'll add unity8 to the list once it's ready.15:35
Saviqfginther, ack, thanks15:36
sil2100jgdx: try again now, we just recently 'fixed' the space issue15:37
sil2100jgdx: I had to ask webops for help as I didn't have enough power myself15:37
balloonsjosepht, how's the re-deploy of my jenkaas coming? I'm thinking it might be useful to test the backup and restore as well. Can we manually take a backup before doing it though so I don't hate my life in redoing things? :-)15:43
josephtballoons: the MP just landed.  You will now need to request an upgrade of your jenkaas from IS.  I'd discuss with them doing a manual backup as well.  I don't think we have the means to easily backup the master from a job since we don't allow execution of jobs on the master.15:46
josephtfginther, psivaa: have a missed anything? ^15:47
josephtUrsinha: do you want to request the core-apps upgrade or should balloons do it?15:47
sil2100bregma: ping15:49
balloonsjosepht, ok, I'll make doubly sure I have a backup, and then I'd like to do a full redeploy if you don't mind. It needs to be tested15:50
fgintherjosepht, balloons, Correct, we don't have means to do a manual backup ourselves (we can make a backup of all the job configurations if that helps). IS can probably do that if specifically asked15:51
sil2100bregma: hey! So, I want to publish silo 5515:51
balloonsfginther, how would you back up the job configs? That would represent a big portion of what's needed atm anyway, as little real data is in there right now15:52
balloonsonly about a week's worth15:52
fgintherballoons, this is what I use - http://bazaar.launchpad.net/~canonical-ci-engineering/uci-jenkins-utils/trunk/view/head:/jenkins-dump-config.py15:52
sil2100bregma: actually, I see everything is ok, so nvm :)15:52
fgintherballoons, it has a dependency on 'python-jenkins' from https://launchpad.net/~jenkaas-hackers/+archive/ubuntu/tools15:53
ChrisTownsendsil2100: I think if it publishes, then the last two changelog entries that are currently in the archive will be wiped out.15:55
fgintherballoons, I have a script somewhere to push a config.xml file to jenkins as a job configuration. I should get it added to uci-jenkins-utils15:55
ChrisTownsendsil2100: A core dev updated libertine underneath this landing.15:55
sil2100ChrisTownsend: no problem, those were quick-fixes, I checked that those are actually 'fixed' in the landing itself15:55
ChrisTownsendsil2100: Right, I was just meaning the changelog history.15:55
sil2100Yeah, that's ok15:56
ChrisTownsendsil2100: Ok, then I won't worry about it:)  Thanks!15:56
balloonsfginther, this looks great thanks. It will at least keep the job configs. I bet python-jenkins can do other fun things with automating job creation. Have any scripts around restoring jobs, or making a set of jobs from a template15:58
fgintherballoons, I've relied on python-jenkins for most of my scripting in the past. It's not perfect, but it has a simpler API for most tasks (vs using curl for example). And yes, we've done some work around templating, this is basically what lp:cupstream2distro-config is for16:00
fgintherballoons, But I am in now way endorsing lp:cupstream2distro-config as a way to solve any current or future problem :-)16:01
brendandfginther, is cu2d sticking around for the foreseeable?16:01
Saviqrobru, hey, does train only push to lp:~ci-train-bot/ on successful builds?16:11
sil2100Saviq: not sure if that changed or not, but in the past it was pushed only on publish16:12
Saviqsil2100, yeah, that changed16:12
Saviqsil2100, https://code.launchpad.net/~ci-train-bot16:12
sil2100ACK16:12
Saviqjust wondering when (i.e. I predict a build failure, but that's when I could use the branch ;))16:13
bfillersil2100, fginther: anyone know what's up with the calexda-pbuilder instances? they've all been busy for quite a while. trying to build http://s-jenkins.ubuntu-ci:8080/view/click/job/camera-app-click/ and building silo 48 taking forever waiting for builders16:15
fgintherbfiller, There is a large number of builds in progress right now on s-jenkins. All the builders are working right now, just appears to be an unusually high demand16:18
bfillerfginther: ok16:19
jgdxsil2100, okay, thanks.16:21
pstolowskisil2100, no disk space problem in silo 8, but there's something wrong with dependencies17:01
sil2100pstolowski: dependencies?17:01
pstolowskisil2100, http://pastebin.ubuntu.com/12971383/17:04
pstolowskihmm not sure if it actually breaks anything17:05
Trevinhorobru: FYI, here https://ci-train.ubuntu.com/job/ubuntu-landing-011-1-build/306/consoleFull I got this17:40
Trevinho2015-10-26 17:14:20,157 INFO Checking bamf for new commits...17:40
Trevinho2015-10-26 17:14:20,382 INFO bamf has no new commits, skipping.17:40
Trevinho2015-10-26 17:14:20,383 INFO Checking compiz for new commits...17:40
Trevinhoit was a clean build though17:40
rvrjhodapp: Silo 15 approved17:43
jhodapprvr, yay!17:43
jhodappthanks17:43
jhodapprobru, mind publishing silo 15 please?17:44
jhodapprvr, I feel like I asked this of you before but I forget what you said, but do you have publish permission as well?17:45
jhodappcyphermox, ping17:59
=== alan_g is now known as alan_g|EOD
robrujhodapp: if it's all MPs and no packaging changes then you can publish your own18:00
jhodapprobru, unfortunately it's not, includes a qtmultimedia source package change18:01
robruSaviq: it pushes the branches after a successful merge.18:01
jhodapprobru, so if everything is to land in the overlay ppa, then I have permissions...is that accurate?18:01
robrujhodapp: ah, you need a core dev then18:01
jhodappyep18:02
robrujhodapp: nope, train treats overlay just like real archive, requires same permissions18:02
Saviqrobru, oh good, missed it somehow18:02
jhodapprobru, then what's the general rule for which I have permission to publish?18:02
robrujhodapp: if there silo contains only MPs, no manual sources, and no packaging changes18:03
jhodapprobru, ok18:03
jhodappogra_, you're a core dev, care to publish my silo 15 if you're around?18:04
sil2100jhodapp: mterry might be a good choice too!18:05
jhodappsil2100, cool, mterry ^18:05
sil2100He's usually nice enough to publish silos for us ;)18:05
jhodappsil2100, mterry got scared away ;)18:09
sil2100hmmm18:12
sil2100;)18:12
sil2100mterry: pong!18:12
mterrysil2100, hihi18:12
sil2100mterry: hey! Could you publish some silos for us? jhodapp has silo 15 for release :)18:13
jhodappmterry, pretty please :)18:13
mterrysil2100, 15... ok18:13
jhodappthanks18:13
cyphermoxjhodapp: hey18:14
* mterry is reviewing18:14
jhodappcyphermox, yo, I got mterry to do my dirty work of publishing silo 15...so don't need your services anymore18:14
mterrydoh  :)18:14
jhodappthanks mterry18:20
mterryjhodapp, yw!18:21
bfillerpopey: mind review latest camera-app in the store?18:23
popeybfiller, sure thing, will do right now.18:24
bfillerpopey: ty18:25
* sil2100 hugs mterry 18:36
* sil2100 gets back to his system-image18:36
Saviqrobru, so, how about automagically adding -gles twins to silos, without an MP even?18:36
jhodappSaviq, I'm +1 to that idea18:44
robruSaviq: jhodapp yeah I like that idea too just a lot on my plate unfortunately18:45
robruSaviq: jhodapp can one of you guys send me a summary of how the packaging is different between gles and non-gles? Eg if I took your non-gles trunk, copied the dir, what change do I need to make there to make it build against gles instead?18:46
jhodapprobru, I don't know the details to that, Mirv always handles that for me for qtmultimedia18:47
robruhm18:47
robruTrevinho: that's because the previous build recorded the commit id even though it failed.18:48
robruTrevinho: I'll file a bug, not sure how to fix that though18:48
robruTrevinho: https://bugs.launchpad.net/cupstream2distro/+bug/151023018:51
ubot5Launchpad bug 1510230 in CI Train [cu2d] "Commit id tracking suboptimal." [Undecided,Triaged]18:51
Saviqrobru, I don't think that's possible, the changes are significant19:31
Saviqrobru, basically, the -gles branch is a packaging branch almost in its own right19:31
robruSaviq: you don't think it's possible to determine -gles programmatically from trunk?19:31
Saviqrobru, I'm afraid not19:32
Saviqrobru, just getting a diff for qtmir19:32
robruSaviq: then I'm not sure how I could make the train handle it automatically, if you guys need to manually sync packaging changes from one to the other19:33
Saviqrobru, http://pastebin.ubuntu.com/12973106/19:34
Saviqrobru, well, you can just default to lp:qtmir/gles when you see qtmir19:34
Saviqrobru, and if we need to supply MPs, we will19:35
Saviqrobru, as you can see, it's already outdated, which is a pain, but I really don't think how we can create that diff automagically19:35
Saviqbiab19:36
robruSaviq: yeah that's pretty crazy19:36
Saviqrobru, but what I think we could do, is just get -gles trunks regardless if there are MPs against it or not20:21
robruSaviq: I suppose it's possible. Can you file a bug?20:26
Saviqrobru, yup, will do, thanks20:26
robruSaviq: thanks20:35
robruSaviq: how's things otherwise though? train is operating smoothly for you?20:35
Saviqrobru, just having issues with conflicts now, but that's rather bzr's fault than trains20:42
Saviq+'20:42
Saviqrobru, one thing is somewhat confusing: https://requests.ci-train.ubuntu.com/#/ticket/56420:42
robruSaviq: what's confusing?20:42
Saviqrobru, dirty flag has precedence over other states, which means I don't see the build job state here20:43
Saviqrobru, it's build failed, but it only says silo dirty20:43
robruSaviq: right20:43
robruSaviq: the problem is that the silo status is just a free form string so it's getting increasingly hard to show different info there, because eg dirty state is determined at a different time than the build failure, so one clobbers the other20:44
robruSaviq: I guess that'll need to grow a bit more clever so it can have a dirty flag but still preserve the original failure message20:44
robruSaviq: for now if you look at the audit log you can see the failure20:44
Saviqrobru, yeah, I understand, and not complaining, although the dirty flag seems also quite persistent20:45
Saviqrobru, like if I kicked a build, and it failed, it shouldn't go back to dirty20:45
Saviqbut it seems only a successful build clears it today20:46
robruSaviq: yeah that's because we had a problem where maybe one package is marked dirty, if you rebuild only a different package it clears the dirty state even though the other package is still dirty. so I made it more agressive about marking silos dirty20:46
Saviqrobru, sure, I'm dealing with it20:46
robruSaviq: also silos now become dirty just by having a new commit on your MP (it used to be just by publishing a conflicting silo)20:46
Saviqrobru, yeah yeah, I know, but it's not the case here20:47
robruSaviq: yeah I agree it's not great, need to think about it a bit to make it work better20:47
Saviqrobru, it did become dirty due to commits, but now without a successful build (which I'm struggling with due to conflicts) it won't get cleared20:47
robruSaviq: that's odd, it should clear the dirty flag at the beginning of the build20:47
robruSaviq: oh, no, I see20:48
robruSaviq: the build clears the dirty flag but when the build fails, the cron job runs and marks it dirty again20:48
Saviqrobru, could be, yeah20:48
robruSaviq: yeah I'll need to add a new field in the db for recording dirty states, so that the main status can be preserved.20:49
robruSaviq: I just rolled out a small train change (just a code cleanup, shouldn't be any noticeable behavior change), and I'm just going to step out for lunch, if anything explodes I'll be back in 3020:50
robru(I tested it in the staging instance though, should be harmless, but there's always a slight risk...)20:51
robruanyway brb20:51
Saviqrobru, ack20:51
michirobru: I just sent an email, could you have a squiz please? I’m looking for inspiration...21:19
robrumichi: looking21:20
michiTa!21:20
robrumichi: https://launchpadlibrarian.net/222338585/DpkgTerminalLog.txt this seems more instructive. I guess there's a missing dep on something or other? not sure21:24
popeybfiller, something is up with the store, i thought the camera was published, but it's still showing as needing manual review21:25
popeyI don't know why21:25
bfiller_Popey: do I need to do anything?21:25
michilibapt-pkg.so.4.1621:25
michiNever heard of it...21:25
popeybfiller_, i think a store admin needs to look at it. i asked in #u1-internal21:25
michirobru: So, this looks like a problem with click.21:27
michiThanks for your help!21:27
popeyok, bfiller_ got it, it's approved.21:29
bfiller_popey: thanks21:31
robrumichi: more specifically it's an import error which suggests to me that there's a dep missing, not sure what package provides that but shouldn't be too hard to dig it up.21:32
michirobru: Hmmm… We have a dependency on click. But if click needs libapt-pkg, I guess that’s a missing dependency in click.21:33
robrumichi: strange that that would be overlooked or that more people aren't affected21:33
robrumichi: also strange that one bug is from utopic and one from vivid, I thought this might be some new issue in xenial or something21:33
michiSo far, I’ve seen only these two reports21:33
michiBut xenial isn’t involved, as far as I can see.21:34
robrubrb tho, eating21:34
michiI don’t think any xenial build for scopes-api exists yet.21:34
michiHey, take your time! :)21:34
jgdxbfiller_, hey, silo 47 just went to QA.21:38
bfiller_jgdx: cool. did 39 land?21:41
robrumichi: yeah it wouldn't need a xenial build specifically, i was thinking maybe the wily build that got copied to xenial could have been broken by changes in click in xenial. But it's not xenial so that's not the issue anyway ;-)21:42
michirobru: Yes. I’ve added click to the bug. Let’s see what comes up. I’m pretty sure it’s not a scopes-api problem.21:43
michiThanks again!21:43
robrumichi: agreed, definitely an issue in click, you're welcome21:44
brendandSaviq, didn't silo 22 land in xenial?22:15
Saviqbrendand, almost there, there was a toolchain issue that's now solved22:15
brendandSaviq, ah22:15
Saviqbrendand, just waiting to test & migrate22:15
Saviqfor some reason http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#qtmir-gles still says i386: Regression, even though if you click on it it's passed twice already22:16
brendandSaviq, because they're all the same version?22:38
robrubrendand: the passes have newer timestamps though22:40
robruThat is weird22:41
brendandagh it's in perl !22:43
brendandmy eyes22:43
robruWhat is?22:43
brendandrobru, debci22:43
robruHeh.22:44
brendandSaviq, here it says pass too: http://autopkgtest.ubuntu.com/packages/q/qtmir/22:50
brendandexcept on armhf22:50
brendandSaviq,  this is what's stopping unity8 from migrating?22:53
brendandoh actually it's mostly ruby22:58

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