/srv/irclogs.ubuntu.com/2016/05/06/#ubuntu-ci-eng.txt

=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== fginther` is now known as fginther
dbarthhey Mirv08:13
dbarthmardy and I are wondering how to land https://requests.ci-train.ubuntu.com/#/ticket/121908:13
dbarththis silo has been put aside because of oxide not being available on certain platforms (same old problem)08:14
dbarththe silo is precisely about moving X11/OA to a supported webview08:14
Mirvdbarth: I don't see any missing platforms compared to before, only one armhf autopkgtest failure on ubuntu-system-settings-online-accounts which I just pushed the retry button for08:16
Mirvon this page https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-021/excuses.html08:17
dbarthoh, i thought that was those which were blocking08:17
dbarththere is a regression marker indeed; mardy wdyt ?^^08:18
Mirvbetter to file an internal bug to try to fix the flaky test, if it's something that now passes on second run.08:18
dbarthok08:20
sil2100bzoltan_: hey! So, any changes in UITK that would warrant a new framework for OTA-11?08:30
sil2100At least from the UITK point of view08:31
bzoltan_sil2100: i am digging up the api changes right now08:34
sil2100bzoltan_: thanks :)08:35
jgdxSaviq, hey, what's the story on the failing autopkg unity8 tests?09:00
Saviqjgdx, there is one flaky one that we  know of09:00
sil2100oSoMoN, chrisccoulson: hey guys!09:00
Saviqjgdx, got a log?09:00
jgdxSaviq, https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-ci-train-ppa-service-landing-008/xenial/amd64/u/unity8/20160428_132659@/log.gz for silo 809:01
sil2100oSoMoN, chrisccoulson: we're working on an arm64 xenial touch initiative right now, trying to get all the seeded packages to build on arm64 xenial09:01
sil2100oSoMoN, chrisccoulson: we finally got libhybris 'enabled' for arm64 and did a few no-change rebuilds of its reverse-deps09:01
Saviqjgdx, yeah, that's the one - another run should make it better and I'll ask my guys to look into this asap09:02
jgdxSaviq, I'm unable to start a run and so are <other people i've asked>09:02
sil2100oSoMoN, chrisccoulson: sadly, oxide-qt (which was dep-waiting on hybris) seems to fail to build on the configure step for arm64: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+build/969422309:02
jgdxI just want to rerun the failing tests, not the whole thing09:02
Saviqseb128, could you please recycle https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-008/excuses.html for jgdx09:03
Saviqjgdx, you need a core-dev for that09:03
seb128Saviq, "recycle"?09:03
seb128I can click buttons09:03
Saviqseb128,  ♻09:03
seb128just tell me which ones09:03
seb128lol09:03
Saviqwell what! ;)09:04
seb128oh09:04
seb128k09:04
seb128it's a retry :p09:04
Saviqno it's not09:04
seb128"Test request submitted."09:04
Saviqhttps://duckduckgo.com/?q=%E2%99%BB09:04
Saviqseb128, thanks :)09:04
seb128yw!09:04
oSoMoNchrisccoulson, does chromium build on arm64?09:09
chrisccoulsonoSoMoN, on android, I believe so09:23
sil2100oSoMoN, chrisccoulson: would be nice if we were able to make it building, otherwise our "big plan" might be endangered09:32
sil2100tvoss, morphis: hey guys! So, after libhybris got available for xenial arm64 I did a no-change rebuild of platform-api aaand... suddenly all archs failed because of a test failure09:33
sil2100tvoss, morphis: could you take a look in a free moment? Could it be related to the hybris stub linker change? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+sourcepub/6391641/+listing-archive-extra09:34
morphissil2100: can you retry with https://requests.ci-train.ubuntu.com/#/ticket/1370 ?09:36
sil2100morphis: hm, let me push the platform-api no-change rebuild to that silo, we'll see if it still fails09:39
sil2100(if you're ok with that)09:39
morphissil2100: yes, I am ok with that09:46
bzoltan_sil2100:  so... I have the scientifical and official answer to you :)09:47
sil2100bzoltan_: \o/ what's the answer then?09:48
bzoltan_sil2100:  I also explain the whol thing, so you will understand why I am pushing our method to all API providers09:48
bzoltan_sil2100:  we have a components.api in the root of the UITK project. We have an automatic process to check all the APIs on each new revision... whenever a new API is introduced or an API is changed this file represents the changes09:49
bzoltan_sil2100:  so... simple bzr diff -r1289..1306 (OTA10..OTA11) on components api shows all the relevnat changes.09:49
bzoltan_sil2100:  http://pastebin.ubuntu.com/16253921/ so we have 4 (four) new properties... if we do not bump the framework version and a poor app developer uses these properties in an app... and that app is installed on a device what is not upgraded to OTA11, then the app might see problems.09:51
bzoltan_sil2100:  this is a rock solid and acidproof way to track APIs and see if we need to bump the  framework version...09:51
sil2100bzoltan_: nice to know, yeah, +1 on a framework bump in that case09:52
sil2100Let me prepare the new framework in a bit09:52
bzoltan_sil2100:  shame that so little change forces us to bump09:53
morphissil2100: it failed again10:02
morphisthat is interesting10:02
morphissil2100: but it doesn't seem to be because of hybris10:03
sil2100hm, yeah10:20
sil2100tvoss: ^10:21
sil2100Strange, it's been a while when we last rebuilt platform-api, maybe the dependency changes now make it fail to build in overall10:21
sil2100tvoss: could you take a look at the papi build failure I mentioned above? Looks like some test is constantly failing now10:22
=== alan_g is now known as alan_g|lunch
=== _salem is now known as salem_
=== chihchun is now known as chihchun_afk
=== alan_g|lunch is now known as alan_g
tedgrvr: So ChrisTownsend is going to put liblibertine in that silo.13:47
rvrtedg: Which one?13:47
tedgrvr: His silo is blocked on translation issues, so he is going to use that one for hte lib stuff associated with the UAL changes13:47
tedgrvr: 1513:47
rvrtedg: Ah, ok13:48
rvrI will block it then13:48
tedgrvr: Thanks, it should just be 15 minutes or so.13:48
robruI'm gonna create a new library called Ertine just to confuse people.13:48
ChrisTownsendrobru: No, don't do it!  The world will explode!13:49
* tedg tried to convince them to call the lib that, but no, they're too conservative over there on the libertine project13:49
rvrconservatine13:49
bregmaever since the ido scandal13:50
cjwatsonI remember some code once that put some of its library code in a directory called "arry" just so that it could build with options -Larry -Wall.14:10
sil2100;)14:11
tedgHaha, nice.14:12
robrucjwatson: was it perl? it was perl, wasn't it?14:18
cjwatsonrobru: don't recall, possible14:19
cjwatsonif it was it's not in perl itself any more14:20
robruheh, you checked14:23
ChrisTownsendrvr: Hey, just an update...waiting on britney to run on silo 15 now.14:34
rvrChrisTownsend: Ping me when ready!14:34
ChrisTownsendrvr: Sure thing!14:34
ChrisTownsendrvr: silo 15 is good to go!15:45
rvrChrisTownsend: Just installed it ;D15:47
ChrisTownsendrvr: Thanks!15:47
rvrChrisTownsend: I still don't see the gedit icon in the Launcher16:01
ChrisTownsendrvr: Well, ok, here's the deal.  If you are using the Libertine Scope, then no you won't because 1) the Puritine click has not been updated yet to include the humanity-icon-theme package and 2) you will need the blocked libertine-scope from silo 50.16:02
ChrisTownsendrvr: If you launch gedit from the App Scope, it should be fine.16:03
rvrChrisTownsend: Ahh.. so it needs a new gedit click16:03
rvrChrisTownsend: I'm launching it from the App scope16:03
ChrisTownsendrvr: Hmm...16:04
bregmarvr, it needs a new Puritine click16:04
rvrbregma: Is it available? Or how can I test the fix?16:05
ChrisTownsendbregma: Not if he's launching it from the App scope.  That uses the libertine-demo package.16:05
ChrisTownsendtedg: So does u-a-l now ignore the icons that we use for the libertine demo stuff when launching from the App scope?16:06
tedgChrisTownsend: No, it shouldn't. It should show the ones from the demo.16:07
tedgChrisTownsend: Not sure what the precedence would be there.16:07
ChrisTownsendtedg: I mean in the Launcher.  If I now launch gedit from the App scope, the gedit icon is now missing in the Launcher/Switcher.16:07
tedgWe need to unseed the demo package16:07
tedgChrisTownsend: Yes, that makes sense.16:07
ChrisTownsendtedg: Not until we can land libertine-scope.16:08
ChrisTownsendtedg: Ugh, that's kind of a regression I would think.16:08
tedgChrisTownsend: It only looks in the container if it is in the container.16:08
tedgChrisTownsend: It won't be once you add the theme to puritine?16:08
ChrisTownsendtedg: Oh, ok.16:08
ChrisTownsendtedg: Right16:08
ChrisTownsendrvr: So I'm in the process of creating a new Puritine click, but armhf builders are slammed and I keep waiting for it to build.16:09
rvrChrisTownsend: Ack16:09
ChrisTownsendrvr: Sorry about the confusion on that.  I thought the App scope icons would still work as before.16:09
rvrChrisTownsend: The gedit icon in the App scope is fine. But the gedit icon in the Launcher is missing as before.16:10
rvrI can't reproduce it easily, but I got a bad window flickering in gedit's top left side16:11
cjwatsonChrisTownsend: LP builders?16:12
ChrisTownsendcjwatson: Yes16:13
cjwatsonChrisTownsend: poked, should clear up soon16:13
ChrisTownsendcjwatson: Thanks!16:14
ChrisTownsendrvr: Window flickering should be independent of this landing.16:14
cjwatson(I'm assuming you mean the virtual builders, as the non-virtual builders have no queue)16:14
ChrisTownsendcjwatson: It's this PPA: https://launchpad.net/~libertine-team/+archive/ubuntu/devel/+packages16:17
cjwatsonChrisTownsend: scored up16:18
ChrisTownsendcjwatson: Thanks again!16:19
cjwatsonand rebalanced the builder pool a bit to help it catch up there16:20
ChrisTownsendcjwatson: Also, after that first PPA builds and publishes it's arm packages, I will need to build arm packages in this ppa: https://launchpad.net/~libertine-team/+archive/ubuntu/puritine-devel16:20
ChrisTownsendcjwatson: Any way to give it a higher priority?16:20
ChrisTownsendcjwatson: Well, you said non-virtual has no queue, so it should be ok.16:21
cjwatsonChrisTownsend: yeah, that won't need intervention16:21
ChrisTownsendcjwatson: Ok, thanks16:21
cjwatsonwe rarely need score hacks nowadays, it's just in the odd exceptional case, and I prefer not to apply them unnecessarily16:22
ChrisTownsendcjwatson: I understand and thanks for helping out my build.16:22
rvrdavmor3: The attack of the clone!16:38
rvrChrisTownsend: How's the click generation going?16:38
davmor3rvr I wish my laptop just lost connection randomly and can't see the ap at all now16:39
ChrisTownsendrvr: The libertine tools that I use to generate it in a PPA just completed and published.  I will now start the build, but it takes some time as it's a ~550MB package.16:39
ChrisTownsendrvr: Generating a Puritine click is all automated in a Jenkins job.  If you want to watch: https://jenkins.canonical.com/libertine/job/puritine-build-click/87/console16:42
rvrChrisTownsend: Thanks16:42
ChrisTownsendrvr: So it has to build a puritine Debian package first in a PPA: https://launchpad.net/~libertine-team/+archive/ubuntu/puritine-devel16:43
ChrisTownsendrvr: And when that finishes, the job will download and extract the deb and then generate a click from it.16:43
ChrisTownsendrvr: And we only care about armhf, which of course is the slowest:)16:44
ChrisTownsendrvr: Here is the current puritine armhf debian build: https://launchpad.net/~libertine-team/+archive/ubuntu/puritine-devel/+build/970063316:44
ChrisTownsendrvr: BTW, if you are installing this click on a frieza, it will probably be better to uninstall the current Puritine click on it, then run 'initctl --session start puritine-click', then install the new one via 'pkcon install-local --allow-untrusted com.ubuntu.puritine_0.8_armhf.click', then rerun the initctl command again.16:47
rvrChrisTownsend:16:48
rvrChrisTownsend: Yes, I'm testing in frieza16:48
ChrisTownsendrvr: Ok.16:49
tedgbregma: How does the unity8-desktop-mir-session package get released?16:58
tedgbregma: Would like to get the policykit-unity8 package in there.16:59
=== alan_g is now known as alan_g|EOW
tedgbregma: Added a task to bug 139661117:04
ubot5bug 1396611 in Canonical System Image "Cannot install click packages on ISO installs of Ubuntu" [High,Confirmed] https://launchpad.net/bugs/139661117:04
davmor2jhodapp: get ready for it17:16
jhodappdavmor2, :)17:16
jhodappdavmor2, woohoo!17:16
jhodappsil2100, can I get some help publish silo 51 please?17:18
jhodappor kenvandine ^17:19
kenvandinejhodapp, looking17:20
jhodappthanks17:21
rvrChrisTownsend: Seems it finished18:23
ChrisTownsendrvr: Indeed it has.  Here is a link to the click: https://jenkins.canonical.com/libertine/job/puritine-build-click/lastSuccessfulBuild/artifact/com.ubuntu.puritine_0.8_armhf.click18:24
ChrisTownsendrvr: Note that I have not tested that at all, so...18:24
rvrChrisTownsend: I must leave now, will check later. Downloading...18:32
ChrisTownsendrvr: Ok, thanks and thanks for being patient:)18:32
rvrChrisTownsend: No problem :)18:39
ChrisTownsendtrainguard: I have a package I want in Xenial overlay and Yakkety, but not in Vivid overlay.  What's the best way to handle that?19:10
ChrisTownsendErr, trainguards ^^^^19:10
robruChrisTownsend: just do a yakkety-only silo and then when it's ready to publish wecan just copy the package to xenial-overlay manually19:11
ChrisTownsendrobru: Ok, cool, thanks19:11
robruChrisTownsend: yw19:11
dobeypoor vivid19:14
slangasekrobru: is that a binary copy?19:29
robruslangasek: that was my intention, yes, since it's still early in yakkety19:30
slangasekrobru: for SRUs we allow copies the other direction (devel-1 -> devel), but never allow binary copies from devel to an SRU; even early in the cycle there can be binary incompatibilities19:31
slangasekand while a binary compatibility would be caught in devel-proposed, there's nothing to catch it when copying the other way19:31
robruslangasek: alright I'll source copy then19:31
robruslangasek: or should we tell him to target xenial?19:32
dobeyyou'd need to rebuild with a different version number, no?19:32
robrudobey: nah19:33
dobeydifferent binary contents with same version number == bad though19:33
robrudobey: actually overlay is full of xenial packages that'll we'll copy to yakkety soon19:33
dobeyyes, but see what slangasek just said about that :)19:33
robrudobey: i don't see an issue there?19:34
dobeyrobru: a binary copy from x -> y isn't (generally) a problem, but a source copy would mean different contents, so the version should be bumped in those cases.19:35
dobeyrobru: likewise, copying a source from y -> x would be a rebuild, and should have a different (lower) version number19:35
robrudobey: yeah. We're doing binary copies from x to y soon19:35
robruChrisTownsend: sorry, you should target xenial then we'll copy it to yakkety after19:36
ChrisTownsendrobru: Ack19:36
dobeyrobru: any idea when we'll be able to do y+x+v landings? :)19:36
robrudobey: early next week19:37
robrudobey: everything is ready to go, just waiting for go ahead from Pat19:37
dobeyyay19:37
ChrisTownsendrobru: I accidentally built previously for both vivid and xenial, but I don't vivid.  So I just abandon the silo and start over?19:39
jgdxrdf landings19:45
slangasekrobru: targetting xenial and copying forward to yakkety would be ok, yes19:46
slangasekrobru: and when is the mass-copy to yakkety planned to happen?19:47
robruslangasek: not sure, sil will do it next week sometime19:47
robruChrisTownsend: that will work, yes. Abandon and reassign the same request19:48
ChrisTownsendrobru: Ok, thanks19:48
robruChrisTownsend: you're welcome19:48
sil2100Yeah, we'll do it 'somewhen' next week, no fully decided week19:56
sil2100s/week/date19:56
sil2100Since we want to do it after we snapshot OTA-11 and have the first candidate image ready, which is not yet sadly19:57
sil2100Possibly somewhere mid-next-week we would be doing the batch copy and triple landing switch from robru19:57
ChrisTownsendrvr: Whenever you get back and test, I had to reboot my frieza after installing silo 15 in order for the gedit icon to show in the Launcher.20:19
=== salem_ is now known as _salem

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