/srv/irclogs.ubuntu.com/2013/07/23/#ubuntu-unity.txt

duflusmspillaz, ping01:19
duflusmspillaz, nevermind. See email01:26
=== _salem is now known as salem_
=== salem_ is now known as _salem
=== Malinux- is now known as Malinux
sil2100didrocks: morning! Still waiting for some stacks to move on and finish (apps waiting on friends etc.), but could you ACK webcreds in the meantime? I guess the change from using rm to -X is ok? http://10.97.0.1:8080/view/cu2d/view/Head/view/WebCreds/job/cu2d-webcred-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_gnome-control-center-signon_0.1.7~+13.10.20130723-0ubuntu1.diff07:30
didrockssil2100: I know, I had to relaunch everything07:30
didrockssil2100: you didn't finish to debug yesterday when you saw lightdm not starting?07:30
didrockssil2100: hum, -X .la, should be -X.la, can you check that the binary is shipping the right files? (not sure what the space is doing)07:31
didrockssil2100: also, we remove the other rm debian/*/usr/lib/*.la07:32
sil2100didrocks: I couldn't access the test machines, and since you said that lightdm is ok, I thought that there is no problem - I relunched the unity testing so that mhr3 could see what was going on07:33
sil2100didrocks: did it start crashing?07:33
sil2100didrocks: could it be that https://bugs.launchpad.net/lightdm/+bug/1203711 started happening?07:33
ubot5Launchpad bug 1203711 in lightdm (Ubuntu) "uninitialised list pointer in configuration directory handling" [High,Fix released]07:33
didrockssil2100: ligthdm was ok with last night version07:34
didrockssil2100: but then, the iso was refrshed07:35
didrockswith the "bad" lightdm version07:35
didrockswhich has been fixed afterward in distro07:35
sil2100didrocks: right, and probably it got refreshed without the latest fix...07:35
didrockssil2100: I wonder why you can't access btw, everyone can07:35
sil2100Right, which was still in -proposed probably ;/07:35
didrocksand it's the same account07:35
didrockssil2100: no, the fix was even not uploaded07:35
sil2100didrocks: I know, I'm trying today07:35
didrockssil2100: so, I fixed and blacklisted yesterday's chroot07:36
sil2100didrocks: it wasn't? I saw a -proposed version with the fix in the +source07:36
didrockssil2100: yeah, but at the time the image was recreated, it was not even uploaded yet ;)07:36
didrocksand so, that's why I relaunched all the -check after relaunching it07:36
didrocks(and we loose several hours)07:36
didrocksI hope we can still make it in today's image07:36
didrockssil2100: I'm stopping unity7, -check07:37
didrockssil2100: we'll get to it later on, I need to give the machine to tvoss_ to debug Mir07:37
sil2100didrocks: geh, the same problem with logging into the machines! I guess maybe my ssh-agent is making some problems, maybe I'm forwarding my keys and this is making problems07:37
sil2100didrocks: ok07:37
didrockssil2100: all the rest run, I think it's just a question of manual publishing07:37
sil2100didrocks: fine with me07:37
didrockssil2100: hum, let's see together in a few, ok?07:37
didrocksbut yeah07:37
didrocksI think you are forwarding your keys07:38
didrockswhen you ssh to the intel machine07:38
didrockstry with -vvvv07:38
didrocksto see if it access a forwarded ssh key07:38
didrocksit should just ask for a password normally07:38
didrocks(once on magners)07:38
didrockssil2100: ATI machine off FYI07:39
didrocks(the jenkins part)07:39
Saviqdidrocks, http://ubuntuone.com/0DJgwKFpgQoN0LNKfK7qMF :007:56
didrocksSaviq: downloading ;)07:57
didrocks(better to be good, no teaser, nothing, just waiting for the download :p)07:57
Saviqdidrocks, yeah, it's kinda big ;)07:57
CimiI have issues overriding a module..08:05
Cimicimi@carina-vm:~/Development/unity/unity8.wallpaper/builddir$ pastebinit ../tests/mocks/GSettings/qmldir08:05
Cimihttp://paste.ubuntu.com/5903298/08:05
CimiSaviq, is that correct? ^08:06
SaviqCimi, « QML2_IMPORT_PATH=../tests/mocks qmlplugindump GSettings 1.0 » ?08:06
Cimiand this is the cmakelists add_qml_test(. Shell IMPORT_PATHS ${CMAKE_BINARY_DIR}/plugins ${CMAKE_BINARY_DIR}/tests/mocks ${qmltest_DEFAULT_IMPORT_PATHS}08:06
Cimi                     ENVIRONMENT "LD_LIBRARY_PATH=${CMAKE_BINARY_DIR}/tests/mocks/LightDM/single")08:06
CimiSaviq, http://paste.ubuntu.com/5903308/08:07
didrocksSaviq: I'm still at the start of the video, seeing autopilot running… ;)08:08
CimiSaviq, in GSettings dir I only have GSettings.qml and that qmldir08:08
SaviqCimi, yeah, that's correct08:09
SaviqCimi, looks fine, push to a branch please?08:10
Cimiok08:10
Cimilp:~unity-team/unity8/unity8.background_gsettings_tests08:13
CimiSaviq, ^08:13
SaviqCimi, your import paths don't include the source dir, so it's not looking in there08:20
SaviqCimi, either you need to copy to ${CMAKE_BINARY_DIR}/...08:20
SaviqCimi, or add ${CMAKE_SOURCE_DIR}/tests/mocks to the paths08:20
CimiSaviq, I added08:21
CimiSaviq, look ^^08:21
SaviqCimi, well, it's not there in the branch you've sent me08:21
Cimiadd_qml_test(. Shell IMPORT_PATHS ${CMAKE_BINARY_DIR}/plugins ${CMAKE_BINARY_DIR}/tests/mocks ${qmltest_DEFAULT_IMPORT_PATHS}08:21
tsdgeos:/08:21
CimiSaviq, yous ure?08:22
tsdgeosi've used gerry's instructions to get a unity-mir usable phone08:22
SaviqCimi, yeah, and where's SOURCE in there?08:22
tsdgeosand now the phone gets stuck at the "Google" step08:22
tsdgeoswhere's gerryyyyyyyyyy08:22
SaviqCimi, and why do you have tests/mocks twice?08:22
seb128Saviq, speaking about gsettings, did you see https://code.launchpad.net/~larsu/gsettings-qt/add-cpp-library/+merge/175901 ?08:23
Saviqseb128, yeah, never got to it yet, though08:23
seb128Saviq, ok, as long as it's on your list somewhere... ;-)08:23
* seb128 wants that to land so it can send a patch for the phone-app to read the ringtone from gsettings08:23
SaviqCimi, but anyway - just export the plugin to the binary dir08:23
seb128then teach system setting to change the value08:23
CimiSaviq, I'm using source?08:23
SaviqCimi, see the QMenuModel mock08:24
Ciminow08:24
Cimior I copy cmakelists of mock08:24
Cimias you guys prefer08:24
CimiSaviq, ^08:24
SaviqCimi, see QMenuModel's CMakeLists.txt08:25
SaviqCimi, and do the same08:25
Cimiok08:25
tsdgeosSaviq: any idea who do i ask about unity-mir stuff if gerry/ricmm are not around?08:28
CimiSaviq, new issue08:29
CimiSaviq, so maybe it works08:30
CimiSaviq, problem is that the property I need is schema.id08:30
CimiSaviq, and if you see GSettings.qml08:30
CimiI cannot set id because it complains...08:30
Saviqtsdgeos, probably no one in this timezone08:30
SaviqCimi, ugh, right, with 'id' I don't think you'll be able to go with QML-only08:31
Cimi*happiness*08:31
SaviqCimi, QML will prevent you from doing that, I'm afraid08:31
Cimiok, will fallback to c++08:31
larsuCimi: you have a schmema with a key named 'id'?08:34
Cimilarsu, ?08:34
Cimilarsu, I'm mocking gsettings module08:34
Cimilarsu, for tests08:34
larsuCimi: ah, I thought you were _using_ GSettings, sorry :)08:35
Saviqtsdgeos, while you're waiting, you could do wear your Qt hat and review https://code.launchpad.net/~larsu/gsettings-qt/add-cpp-library/+merge/175901 :)08:37
seb128Saviq, is there a way to do "text: "%s something" % string" in qml?08:37
Saviqseb128, "%1 something".arg(strin)08:37
Saviqg08:37
tsdgeosSaviq: actually i just realized the phone is not "stuck"08:37
Saviqtsdgeos, yeah, I imagine the shell just didn't start08:38
tsdgeosi.e. yes it's stuck in the "google" screen08:38
tsdgeosbut i can adb shell08:38
Saviqtsdgeos, ↑ see who just joined? ;)08:38
larsuseb128: javascript doesn't have that afaik08:38
tsdgeosbut still don't know what are the next steps08:38
larsuseb128: but you can use "abc" + x + "def"08:38
tsdgeosso i need greybackkkkkkkkkkkkkkkkkkk08:38
Saviqlarsu, QString().arg() is there in QML's JS08:38
Saviqlarsu, as "string" is QString08:38
larsuSaviq: javascript strings are QStrings?08:38
larsuSaviq: ah, neat08:38
seb128larsu, I can't use the "a" + "b", that's not gettext friendly08:38
Saviqyup08:38
larsuseb128: listen to Saviq!08:38
seb128in some locales the order is reverses08:39
seb128reversed08:39
larsuright, there's always that08:39
Saviqyeah, concatenation == EVIL08:39
larsuanyway, why are you guys mocking GSettings? Are you mocking all of your deps?08:41
Saviqlarsu, because we need to test how we react to a changed setting08:42
Saviqlarsu, so yes, we're mocking stuff like that08:42
larsuSaviq: you can do that with GSettings as well (use the memory backend)08:42
larsuI'm doing that in GSetting's tests08:42
tsdgeoslarsu: you are not deleting the QGSettings you create in componentComplete, no?08:42
Saviqlarsu, that's for integration, yes08:42
Saviqlarsu, but we're doing kind-a-unit tests08:43
Saviqlarsu, each component tested in isolation08:43
larsuSaviq: fair enough. Just seems a bit excessive to me :)08:43
Saviqlarsu, btw, wrong indent on patch line 37708:43
larsutsdgeos: I'm not? /me checks08:43
larsutsdgeos: I'm creating it with 'this' as parent - I thought QObject deletes children for me?!08:44
larsuSaviq: oops, thanks08:44
tsdgeoslarsu: right-y08:44
tsdgeoslarsu: also there's a few "this->" that will make C++ purists a bit icky :D08:46
larsutsdgeos: how big of an issue is that? (It's all over the rest of the code base as well, I'd rather keep it consistent tbh)08:48
tsdgeosit's not an issue08:48
tsdgeosit's jus stylistic08:48
tsdgeos+t08:48
larsuwell, I'm maintaining it for now ;)08:49
larsuSaviq: fixed the whitespace08:49
sil2100bregma, Trevinho: hi guys, we still have the unity powerpc FTBFS, Brandon tried to find the cause, had some hypothesis but couldn't test it properly in the end - could you guys take a look at that as well? I can forward Brandon's e-mail if anything09:17
sil2100bregma, Trevinho: it's a failing unit test09:17
sil2100https://launchpad.net/~ubuntu-unity/+archive/daily-build/+build/479845909:17
=== jono is now known as Guest19501
Saviq$3.3M09:20
tsdgeossil2100: do you know that if the fact mouse wheel does not work anymore in the volume indicator is on purpose or a bug?09:20
tsdgeosSaviq: in case you haven't seen it http://ubuntu-edge.info/ is cool09:21
sil2100tsdgeos: I would personally guess that is a bug09:21
sil2100tsdgeos: could you fill in a bug for that? We probably don't have an AP test for that, where we probably should!09:21
Saviqtsdgeos, yeah, I did09:21
tsdgeossil2100: against which project?09:21
sil2100tsdgeos: indicator-sound would make sense09:23
sil2100tsdgeos: but I would guess it might be related to some other package as well09:24
tsdgeoswell let's file it there09:24
tsdgeosand see if anyone reads it :D09:24
sil2100tsdgeos: I'll poke the indicator guys about that as well - what version of indicator-sound do you have?09:25
tsdgeosii  indicator-sound                                 12.10.2+13.10.20130722-0ubuntu1                 amd64        System sound indicator.09:25
sil2100I have the previous version and scrolling doesn't work as well! Strange09:26
sil2100Maybe something in the core indicators changed09:27
seb128sil2100, tsdgeos: it's a bug, I pointed it to larsu on the merge request for the port to gmenu09:31
seb128not sure we got a bug report for it though09:31
tsdgeosseb128: well i just created one09:32
seb128tsdgeos, thanks09:32
Saviqlarsu, btw, no tests for QGSettings? ;)09:34
larsuSaviq: no exhaustive tests, but the qml module uses QGSettings now, too. So functional tests are there :)09:36
Saviqlarsu, k09:36
Saviqlarsu, only thing I was thinking - schemas have descriptions sometimes, right?09:36
Saviqlarsu, do you think it would ever be useful to expose those?09:36
Saviqseb128, ↑ question for you, too09:37
larsuSaviq: yes, as soon as someone asks for them (I already expose some of the metadata through the the choices() method)09:37
seb128Saviq, I've never seen those exposed anywhere in a "normal UI" (only in the config editor in GNOME)09:38
Saviqseb128, yeah, that's what I thought09:38
Saviqlarsu, ok, so looks good from my PoV09:38
larsuSaviq: thanks for having a look09:39
Saviqtsdgeos, you're doing a full code review of qgsettings? or did, already?09:39
tsdgeosSaviq: i had a look at the patch, the patch looks ok, did not have a full look at the code itself, want me to?09:40
Saviqtsdgeos, yeah, I meant the MR09:40
* tsdgeos is trying to get the unity-mir thing to start09:40
Saviqtsdgeos, did you catch greyback in the end?09:40
tsdgeosyes09:41
Saviqk09:41
greybackSaviq: yep, I'm here09:41
greybacktsdgeos: luck?09:41
tsdgeosgreyback: on it09:41
greybackok09:41
tsdgeoslarsu: in GSettingsSchemaQml::choices would it make sense to switch the ifs?09:46
tsdgeosi.e. first check for if (parent->priv->settings == NULL) and then for if (!parent->contains(key))09:47
tsdgeosit's what the old code did, no?09:47
larsutsdgeos: if parent->priv->settings is NULL, contains() always returns false09:49
tsdgeosseb128: larsu: https://bugs.launchpad.net/bugs/1204036 fwiw09:49
ubot5Launchpad bug 1204036 in The Sound Menu "Mouse wheel stopped working on Saucy" [Undecided,Triaged]09:49
seb128tsdgeos, thanks09:49
larsutsdgeos: because the variantmap is only populated when the settings object is created09:49
larsutsdgeos: just responded, thanks for filing it09:49
tsdgeoslarsu: sure, just saying that since this was "porting" maybe it made sense to keep the old order of the ifs, and probably checking for  parent->priv->settings is 0.00000001% faster than contains :D09:50
tsdgeosfeel free to ignore09:50
larsutsdgeos: ya, fair enough. I'll switch 'em09:51
tsdgeoshttp://paste.ubuntu.com/5903563/ :/09:55
tsdgeoswhat is this bt? http://paste.ubuntu.com/5903565/09:56
* tsdgeos looks at qconf_types_to_qvariant and cries10:03
tsdgeosin how many places we have copypasted code like that10:03
tsdgeos:-/10:04
tsdgeos3? 4?10:04
tsdgeoscan someone from unity-api land finally create a lib for it10:05
tsdgeosplease please please10:05
larsutsdgeos: everyone should copy that one. It's the most comprehensive, most sane, and written by desrt10:05
larsutsdgeos: no, a library is overkill. Copying is good enough.10:05
tsdgeoslarsu: i disagree, there will be bugs and improvements to make, copying code is just horrible maintaiince wise10:10
larsutsdgeos: not really, it's just two files that aren't used in many places. I'd be fine with a bzr submodule kind of thing though10:18
larsubut then the places that do need this kind of functionality probably have very different needs10:18
larsuqvariant <-> gvariant is just not a good mapping, despite the name10:18
tsdgeoslarsu: well, dee-qt has something similar and not sure what else i was reviewing a few months ago had a copy of the dee-qt code10:19
tsdgeosand now this has a indepently written thing that does the same10:19
larsutsdgeos: well, this is copied from qconf, not newly written10:19
tsdgeossure10:19
larsu(and qconf is dead now)10:19
tsdgeosi'm just saying that there's at least 3 or 4 copies of similar code floating around10:20
tsdgeosi rememer adding code in one of them to support arrays or something and then stumbling upon a different one and wondering why my code had been removed10:20
tsdgeosunless i realized it was a different file10:20
larsuI understand that. I'm saying it's not that big of a deal :) Also, I'm not opposed to putting it in a shared bzr submodule10:21
larsubut *please* don't make this a lib10:21
tsdgeoswhat's the problem with a lib?10:23
mhr3+1 for lib10:25
larsuI think the overhead of maintaing a library for these couple of functions (and source/binary compatibility) is not worth it10:25
larsulet me ask the other way around: what's the problem with a submodule?10:25
mhr3larsu, it will get copied around without a reference to the original, ie won't be updated10:26
mhr3so not much of a difference to current copying10:27
larsumhr3: submodules point to a bzr repo, no? All you need to do is to bump the revision number every now and then10:27
mhr3ehm, can bzr even do such thing?10:28
larsuI don't know, I assumed so...10:28
* larsu should check this out before making bold claims10:28
mhr3:)10:28
larsumhr3: I guess you're right: https://bugs.launchpad.net/bzr/+bug/26777010:31
ubot5Launchpad bug 267770 in Bazaar "Bazaar does not support nested branches" [Wishlist,Confirmed]10:31
larsuI take everything back and advocate copying files around again!10:31
* larsu hides10:31
tsdgeosgreyback: aloha10:34
tsdgeosgreyback: http://paste.ubuntu.com/5903563/10:34
larsutsdgeos: in any case, this shouldn't affect this merge, that code was in there before. If you feel strongly about it, please file a bug (or write that library ;) )10:34
tsdgeoslarsu: sure, i'm not blocking this merge anyhow10:34
tsdgeosit was just a "let's shout and see if someone agrees/it sticks"10:35
greybacktsdgeos: if you do an "apt-get upgrade", does it want to update any package with "platform-api" in the name?10:35
larsuSaviq: tsdgeos is fine with it, you too? Can you approve it please?10:35
greybacktsdgeos: crash is due to Mir API change, the platform-api package you're using was not updated to this new API, hence crash10:35
tsdgeosgreyback: but but but i just flashed this phone 3 hours ago10:36
greybacktsdgeos: welcome to my world :)10:37
tsdgeosit's a grey world!10:37
* tsdgeos upgrades and sees if that helps10:38
tsdgeosyeeeee10:39
tsdgeosdid not crash10:39
greybacktsdgeos: see unity on screen?10:39
tsdgeostook a good while10:39
tsdgeosbut yeeeeeeeeeeees10:39
greybackit's blocking on HUD10:39
greybackdunno why, it's annoying though10:39
greybacktsdgeos: so be nice, it's pretty crappy as yet. Any app-related animations are all broken, and input doesn't get to apps yet. All on my todo list10:40
* tsdgeos does the evil face/grin10:41
tsdgeosnow really, what you need me to do? :-)10:41
greybacktsdgeos: unity-mir. src/modules/Unity/ApplicationManager/application_manager.cpp - I want you to add the dbus api to that10:42
greybackthe API: http://studio.sketchpad.cc/EEd2PSjTRn10:42
tsdgeosgreyback: oka, there's a blueprint i should get myself assigned?10:43
greybacktsdgeos: yes https://blueprints.launchpad.net/unity8/+spec/unity-mir10:44
tsdgeosBOOM firefox BOOM10:45
tsdgeosgreyback: ok, snatched that blueprint item from you10:48
greybacktsdgeos: magic, thanks.10:48
greybacktsdgeos: instead of always starting up unity8 to test, this might be handy: lp:~gerboland/+junk/qml-demo-shell/10:50
tsdgeosok10:51
sil2100greyback: hi! Since enabling autolanding might take a moment due to the requirement for modified platform-api and qtubuntu, could you maybe take a look at the packaging changes branch I made? I would merge in manually then ;)10:58
sil2100greyback: https://code.launchpad.net/~sil2100/unity-mir/packaging_cleanup/+merge/17623910:58
greybacksil2100: certainly10:58
sil2100greyback: (since I'll need Francis to do anything concrete)10:58
=== MacSlow is now known as MacSlow|lunch
sil2100eeeg11:08
sil2100eeh11:08
sil2100mhr3: hi!11:09
sil2100mhr3: you know what's pissing me off today? Guess11:09
mhr3sil2100, environmental issues?11:09
mhr3sil2100, harvesting wood in jungles?11:10
mhr3sil2100, hunger?11:10
sil2100mhr3: ;D11:10
sil2100mhr3: sadly, it's something much worse than that11:10
mhr3:-O11:10
mhr3much worse?11:11
mhr3is our planet dieing?11:11
sil2100mhr3: WORSE! Unity ati testing11:11
sil2100http://10.97.0.1:8080/job/autopilot-saucy-daily_release/575/label=autopilot-ati/console11:11
sil2100mhr3: intel had 13 failures, ONLY 13!11:11
sil2100mhr3: but ati? It seems to be stuck AGAIN11:11
mhr3sil2100, when was X/mesa last updated?11:12
mhr3sil2100, i think compiz is crashing regularly there11:14
sil2100hm, I guess there was some X update some weeks ago11:14
mhr3that's why the tests take ages11:14
sil2100I'll try logging in11:14
mhr3trying as well11:15
mhr3sil2100, it seems like the container is dead11:16
sil2100mhr3: compiz seems to run at least 30 minutes11:16
mhr3jibel, could you check the ati machine? i can't attach to it11:16
sil2100I ssh'ed to it11:16
sil2100But hm11:16
sil2100Right11:16
mhr3you did?11:16
mhr3jibel, did you just kill it, or did the kernel do it? :)11:21
mhr3dmesg says kernel did11:24
nic-doffaytsdgeos, similar question to yesterday. Any idea where the logic is contained for when you swipe left or right between scopes?11:32
tsdgeosnic-doffay: is there any logic besides calling "showHeader"?11:35
nic-doffaytsdgeos, I see the GenericScopeView has showHeader when onMovementStarted is called...11:36
nic-doffayIs that the movement for the left/right swipe?11:36
tsdgeosyeah11:36
tsdgeosall the dashes do11:36
tsdgeos./Dash/DashVideos.qml:38:    onMovementStarted: categoryView.showHeader()11:37
tsdgeos./Dash/DashMusic.qml:37:    onMovementStarted: categoryView.showHeader()11:37
tsdgeosetc11:37
Trevinhosil2100: I've seen that test failing there... I'll check asap if we don't have a better solution before11:39
Trevinhosil2100: the problem is testing it... Do we have a fast way (other than building a VM)?11:39
sil2100Trevinho: hmmm, not sure, maybe we could somehow enable powerpc in some PPA and get it building there, but I guess that wouldn't be faster ;/11:40
Trevinhosil2100: no it doesn't seem at all11:41
seb128sil2100, Trevinho: just turn off the buggy test on ppc to unblock?11:42
Trevinhoseb128: it's probably easier to disable it for everybody... but that's a final possibility11:42
seb128well, don't block on ppc for weeks11:43
seb128do you need access to a porter box? try asking infinity, he might be able to help11:43
seb128he gave access to charles recently to debug an indicator test11:43
Trevinhoseb128: ah, that would be cool11:43
sil2100seb128: we're not blocking on ppc for weeks, we're blocking on different issues in unity for weeks! I'm starting to wonder what's wrong with unity and ati11:45
didrockssil2100: are the integration tests ok?11:46
didrocksapart from that powerpc issue?11:47
mhr3sil2100, got my msg?11:47
mhr3xchat really doesn't like switching network11:47
greybacksil2100: unity-mir packaging changes approved, thank you11:50
sil2100greyback: thanks!11:51
sil2100greyback: saaadly, it seems we'll have to wait with enabling autolanding as well11:52
sil2100jibel: ping11:52
greybacksil2100: boo :(11:53
mhr3sil2100, the second testing is still in progress so will pastebin the previous results once it finishes11:54
sil2100mhr3: ACK11:54
mhr3meanwhile.. lunch11:55
sil2100didrocks: sooo, mhr3 did some research and we think we're encountering the same recordmydesktop issue as before (which caused jibel to disable it) - but this time only on ati11:55
sil2100didrocks: mhr3 ran unity AP tests on his ati machine in his office and there was all fine, ~17 failures he had - he's re running it11:56
sil2100didrocks: we had 13 failures on intel11:56
mhr3sil2100, 16! :)11:56
sil2100didrocks: so what we would propose is to fix the powerpc FTBFS and manually publish unity FINALLY if the last test run is ok11:56
sil2100didrocks: in the meantime trying to resolve with jibel what's going on here11:56
sil2100(filling in a bug)11:57
sil2100jibel, didrocks, mhr3: https://bugs.launchpad.net/otto/+bug/120408012:05
ubot5Launchpad bug 1204080 in Otto "Unity autopilot test container timing out/dying on ati" [Undecided,New]12:05
sil2100I would also add the unity project to that12:05
sil2100(just in case)12:05
didrockssil2100: ok, keep me posted about your progress with jibel12:05
sil2100didrocks: would you be ok with the manual publishing for now?12:06
didrockssil2100: if it pass on intel with few tests failing, yes12:07
=== _salem is now known as salem_
Saviqmzanetti, need your opinion12:12
mzanettiSaviq: shoot12:13
Saviqmzanetti, https://code.launchpad.net/~diegosarmentero/unity8/app-preview/+merge/17441912:13
Saviqmzanetti, lines 1486 and down12:13
Saviqmzanetti, on the one hand it's not testing much12:13
Saviqmzanetti, but on the other it does test that the values are where you expect them to be12:13
* mzanetti reads12:14
Saviqmzanetti, the other thing - line 125612:14
Saviqmzanetti, should we a) test under LANG=C or b) use i18n in tests?12:14
mzanettiSaviq: for the first one I need a bit more time to run the test and understand how it works12:17
jibelsil2100, pong12:17
mzanettiSaviq: for the second one: good question. I'd probably go for LANG=C and have a separate test suite for i18n12:17
sil2100jibel: hi!12:18
sil2100jibel: did you look at that bug I filled? I know it's probably not too detailed, but we're not sure what's going on12:19
sil2100Trevinho: hi! Did you disable that test or maybe fix it?12:19
jibelsil2100, yes, I think you're right, I'll increase the memory limit to 6G. We'll se if it improves the situation12:20
sil2100Trevinho: maybe I could just quickly disable that test in overall? Since we'd like to get it released12:20
sil2100But damn, again waiting for everyting to rebuild, shit ;/12:20
jibelsil2100, done on ATI12:21
jibelyou can re-run the tests if you wish12:21
sil2100jibel: ok, thanks! Would prefer to have one more fix in before doing that12:22
sil2100Ok, I'm a bit irritated now12:25
=== MacSlow|lunch is now known as MacSlow
sil2100Trevinho, mhr3, didrocks, anyone: https://code.launchpad.net/~sil2100/unity/disable_failing_test/+merge/17637012:30
sil2100Since it'll take forever to get this merged, as armhf is building forever12:30
sil2100Then another 2 hour wait for it to build in the PPA12:30
sil2100This is so irritating12:31
Trevinhosil2100: approved12:31
sil2100Trevinho: thanks! Sorry for the quick hack, but I'm getting desperate12:33
Trevinhosil2100: yeah, i guess12:33
mzanettiSaviq: hmm... I think the reviews test would be more useful with different review texts/users12:37
mzanettiSaviq: so it would also check the ordering12:37
tvoss_Saviq, ping12:39
Saviqtvoss_, pong12:41
Saviqmzanetti, yeah, of course12:41
Saviqmzanetti, and ideally data-driven, too12:41
tvoss_Saviq, hey there :) x-check: no zeitgeist on the phone, correct?12:41
mzanettiSaviq: yes, I agree12:41
Saviqtvoss_, not yet, but I assumed we'll need/have it12:42
Saviqtvoss_, otherwise everyone and their dog will have to maintain a "Recent" log at varying performance quality12:42
tvoss_Saviq, we need it, but it's quite massive in terms of resource usage12:42
tvoss_Saviq, fair point, but zeitgeist is what? python iirc12:43
Saviqtvoss_, is it?12:43
Saviqtvoss_, vala, it seems12:43
tvoss_Saviq, ack, still bad, but better than python :)12:44
Saviqtvoss_, and then, if everyone kept their own event log, would that actually be better for resources than zg?12:45
tvoss_Saviq, no, but I still wonder how much sense Zeitgeist make in a content-siloed world12:45
thostr_Saviq: tvoss_: for music or media in general we might be able to use mediascanner as well12:45
Saviqtvoss_, doesn't matter, IMO12:46
Saviqtvoss_, it's just an event log12:46
Saviqtvoss_, what you put in there is your decision12:46
tvoss_Saviq, okay12:46
Saviqtvoss_, granted, we need to silo data *inside* zg so that apps can't look at each other's data12:46
tvoss_Saviq, how does a scope use it then?12:46
Saviqtvoss_, scope reads the events it's interested in, matches to $data_source, DONE12:47
Saviqtvoss_, obviously there's a question of sharing that data between $apps12:48
tvoss_Saviq, okay, so we would need security to look at it?12:48
Saviqtvoss_, probably12:49
mzanettiSaviq: I'd be ok with the autopilot-refactor merge now. What about the get_grid_units() runtime error? shall we leave it as is (no problem for me)?12:49
Saviqmzanetti, I think yes12:49
mzanettiSaviq: ok. I'll approve12:49
Saviqtvoss_, OTOH we can just say that's a shared data repository12:50
Saviqtvoss_, and you should only put data that you really need there12:50
tvoss_Saviq, I think we should talk to the security guys12:50
Saviqtvoss_, and data that doesn't pose any security issues if others get access to it12:50
Saviqasac, didrocks - we're approving the first set of unity8 integration tests, what's the next step?12:53
mhr3sil2100, something bad happened with the second run12:53
asacSaviq: nice... so we wanted to wait until we hit all green12:53
asacbefore adding more12:53
mhr3autopilot itself crashed... pretty weird12:54
asacbut if yhou say your stuff is green, we could give it a one time try next run and see12:54
asacmost likely :)12:54
asacSaviq: so what shall we run?12:54
asaccan you give me the phablet-test-run command ?12:54
Saviqwell, it's still in Approved, not merged yet ;)12:55
=== jhodapp is now known as jhodapp|afk
Saviqasac, but it's going to be `phablet-test-run -i -n -p unity8-autopilot unity8`12:56
asacSaviq: is that stuff already in the image?12:56
asaci thought we haltetd propagating new unity stuff for now12:57
Saviqasac, yeah, it is not12:57
Saviqasac, as I said - only Approved now12:57
asaci guess we should try to turn it on12:57
asacbut be prepared to back it out12:57
asacyou think thtas easy?12:57
asachow would you go about backing out?12:57
asacafter landing new unity and stuff goes fully red12:57
Saviqasac, we could remove from ppa:ubuntu-unity/next12:58
Saviqasac, but would need to make sure that the previous version is still there12:58
asacSaviq: thats not backing out i feel12:59
asacthats more like "lets test more before we land"12:59
Saviqasac, what you mean by "backing out"?13:00
Saviqasac, how do we do a test-run then?13:00
didrocksSaviq: in some hangouts, but will get to you after that13:00
Saviqasac, without releasing into the ppa or the image, for that matter?13:00
Saviqdidrocks, cheers13:00
asacSaviq: a real backout i mean13:01
asace.g. we test and test and feel its ready13:01
asacwe finally land13:01
asacand stuff explodes13:01
asacwhat do we do?13:01
asaconly thing that brings us back to green in a guaranteed timeframe is to backout :)13:01
asacso having a backout plan would be nice to hav for all major stuff13:01
mhr3sil2100, i'll just run it again13:01
asacnot sure if thats possible right now13:02
asacbut wanted to check13:02
asacif you would have an idea13:02
Saviqasac, well, because we've stopped unity8 landing in the ppa13:02
mhr3sil2100, meanwhile here's results from the first run http://paste.ubuntu.com/5904030/13:02
Saviqasac, there's a few commits in there already that are not yet in the image13:02
asacright and those never passed our tests13:02
asacso we dont know what happens13:03
asacwhat we know is that its best to know how to get back to today in case the next push to ppa breaks it13:03
asacaka backout13:03
Saviqasac, well, yeah, that's why I said we need the current packages held13:03
Saviqasac, or we can revert everything between the last release13:04
asacyou cannot go back13:04
asacyou would have to reupload a revert revisionj13:04
asacits a limitation of archive/ppas etc.13:04
Saviqasac, well, yeah, that's what we can do13:05
Saviqasac, OTOH truth is that because we've not tested any unity8 to this point, what's the difference between reverting and just disabling the tests again...13:06
Saviqasac, assuming manual testing would pass13:06
Saviqasac, or, well, we fix it if it breaks13:07
asacSaviq: its about establishing a culture of no breakage on dashboard and learning how to get back to green in a guaranteed timeframe ... etc.13:11
nic-doffaytsdgeos, sorry having some hardware issues here.13:11
nic-doffayWhat triggers those onMovements thought tsdgeos ?13:12
nic-doffay*though13:12
asacthere will always be reasons not to stay green, but all those reasons must stand back for the higher goal of convincing folks that we can deliver features safely, all the time13:12
tsdgeosnic-doffay: meeting,13:13
nic-doffaytsdgeos, k no worries13:13
kgunnMacSlow: https://blueprints.launchpad.net/ubuntu/+spec/client-1303-unity-ui-phone13:28
kgunn...i took the liberty some time ago to put your name by it :)13:28
kgunnalso..you can always use launchpad.net/~macslow/+upcomingwork13:29
mzanettimterry: remember the bug that om26er reported about the greeter not locking?13:29
mzanettimterry: I just flashed my phone and now I have it too13:29
om26erits like happening every 2hours for me13:29
MacSlowkgunn, doh... forgot about that :)13:29
mterrymzanetti, stop it!  :)13:30
mzanettimterry: yeah... just wanted to ask if you've already seen/fixed it as I've been away for a week13:30
mterrymzanetti, nope, I haven't seen it/fixed it.  :-/13:30
mterrymzanetti, how was your time off, btw?13:30
mzanettimterry: awesome! it was a really great akademy. and the QCS was really nice too.13:31
mzanettimterry: the 40°C killed me at times... but good thing is you get 2 new t-shirts a day at such conferences so I managed to get through :D13:32
mterrymzanetti, heh, I need to go to a conference again.  My t-shirt supply is wearing out.  Darn lack of UDS's...13:32
mzanettimterry: good point.. I'm a bit sad that there are no saucy shirts around13:33
mterrymzanetti, we usually sell some from the store.  I wonder if we will have saucy-specific shirts by release time, or if all shirts are going to be unversioned now13:33
greybackSaviq: standup?13:33
sil2100mhr3: thanks!13:37
sil2100SHIIIT13:38
sil2100fginther: arrrghh, having problems with the armhf merger!13:38
mterryHas the meeting not started?13:38
sil2100fginther: https://jenkins.qa.ubuntu.com/job/unity-saucy-armhf-autolanding/139/console13:38
mterryOr am I having mumble problems?13:38
sil2100fginther: again the ERROR:pbuilderjenkins:Error during build execution problem13:38
sil2100fginther: does it need fixing or re-approving is enough?13:38
sil2100fginther: (hello btw.)13:38
* sil2100 is a bit nervous because of the unity stalling13:39
sil2100fginther: could we anyway merge it in without waiting for armhf to build correctly?13:39
sil2100fginther: this is a change that only disables a test, so it doesn't change anything in the code besides that, so it makes no sense for us to wait 2 hours for armhf13:40
fginthersil2100, hello! Will look in a second13:40
mzanettimterry: can you hear us?13:40
greybackmterry: we don't hear you13:40
mterryshoot.   Skip me and I'll reconnect13:41
sil2100fginther: many thanks! I'd like to get this merged and released ASAP ;)13:42
fginthersil2100, This "W: Failed to fetch bzip2:/var/lib/apt/lists/partial/ports.ubuntu.com_ubuntu-ports_dists_saucy_universe_binary-armhf_Packages  Hash Sum mismatch" is an error communicating with the archive. Please just re-approve.13:44
sil2100fginther: can we somehow force a skip of armhf for this merge btw.?13:46
* sil2100 has 3vil requests13:46
fginthersil2100, hmmm, give me a minute13:46
fginthersil2100, you still there?13:51
sil2100fginther: yes! Had a phone call13:52
=== jhodapp|afk is now known as jhodapp
Saviqtsdgeos, do you know what "[aacid] plugins/HudClient/volumepeakdetector.cpp: TODO" means in https://blueprints.launchpad.net/ubuntu/+spec/client-1303-unity-hud-2-ui ?13:54
tsdgeosSaviq: testing it13:54
Saviqtsdgeos, ah13:55
tsdgeosit's hard to test, need to feed it fake data via pulse or something and then verify the values are good13:55
tsdgeosmaybe the test part got lost when it moved from somewhere else13:55
tsdgeosisn't that dupe?13:56
tsdgeosi have13:56
tsdgeos add tests for volumepeakdetector13:56
tsdgeosiin https://blueprints.launchpad.net/ubuntu/+spec/client-1303-unity-hud-2-ui13:56
tsdgeosor you just renamed it?13:56
kgunnSaviq: so all the new hud work items are really tweaks right? no new functionality per se13:56
Saviqkgunn, yeah13:57
Saviqkgunn, just low hanging fruit13:57
Saviqkgunn, the only bigger thing is the preview13:57
Saviqkgunn, but as you've seen I put it in non-milestoned WI13:58
=== dandrader is now known as dandrader|afk
Saviqtedg, greyback, hangout?14:00
Saviqtedg, why U not on irc.c.c?14:00
tedgSaviq, yes, just a sec... finishing a call.14:00
tedgSaviq, I am, "ted"14:01
Saviqsneaky!14:01
SaviqI type "ted" and press <Tab>, nothing happens!14:01
tedgSaviq, I started the chat14:02
Saviqgreyback, ping14:03
Saviq?14:03
greybackSaviq: coming..14:03
greybackSaviq: tedg I can't find a link anywhere, please paste it to me14:04
sil2100mhr3: restarted the unity stack, let's keep our fingers crossed - this time the tests might even pass as jibel increated the memory limit14:05
kenvandinejibel, can you please add views in jenkins for the thin-client and click-package stacks under head?14:05
mhr3sil2100, the 3rd round of testing finished here, 17failures this time14:05
jibelsil2100, if really tests hit the limit again, we'll have to disable rmd for unity and find a real solution other than pushing the wall14:06
sil2100jibel: ACK14:07
sil2100mhr3: awesome14:07
mhr3sil2100, http://paste.ubuntu.com/5904195/14:07
sil2100mhr3: I guess if we get some problems during this run we'll publish anyway14:07
sil2100mhr3: since we anyway have to wait until everything builds before publishing, so maybe it'll manage to finish the AP tests as well14:08
sil2100mhr3: if not, we'll use your results and publish manually muhaha :E14:08
mhr3sil2100, are you taking care of opening bugs for these / or pinging Trevinho/bschafer?14:08
sil2100mhr3: for what issues you mean?14:12
mhr3sil2100, in the pastebin14:12
sil2100mhr3: I'll poke the guys once we have a release, yes :D14:13
mhr3sil2100, k, thx14:13
jibelkenvandine, done on private jenkins, CCed you on RT to do the same on public instance.14:14
kenvandinejibel, thanks!14:14
=== dandrader|afk is now known as dandrader
tsdgeosSaviq: i duplicated my "inprogress" tasks to a done (code) and a inprogress (get code into qt)14:15
tsdgeoss/tasks/blueprint items14:15
mhr3tedg, ping? i was told hud uses the appmanager api, how it that exposed? do you need to link with mir or unity has a dbus interface or...?14:15
sil2100tsdgeos: btw. did you fill in that bug for the scroll-not-working for indicator-sound?14:17
tsdgeossil2100: yes14:17
sil2100tsdgeos: can you give me the link? Maybe tedg will know more what's up?14:18
tsdgeossil2100: larsu said "was known"14:18
tsdgeosport to gmenumodel or something14:19
sil2100Ah, cool!14:19
sil2100tsdgeos, larsu: I wonder if we could have an AP test for the mouswheel scroll on indicator-sound14:19
larsusil2100: sure we could14:20
larsuit would fail right now though :P14:20
Saviqtsdgeos, cheers14:20
sil2100:D14:21
Saviqdidrocks, free?14:21
tedgmhr3, Not yet, greyback is working on the Application API, I think it'll just be a DBus interface.14:21
mzanettikgunn: ping14:22
mhr3tedg, ah14:22
mhr3greyback, can you keep me in the loop about that14:22
greybackmhr3: ApplicationManager will have a dbus API. What do you need?14:22
didrocksSaviq: in another hangout, I'll ping you back as soon as it's finished14:22
mhr3greyback, apparently we need a scope to expose the info back to shell :P14:22
greybackmhr3: http://studio.sketchpad.cc/EEd2PSjTRn is the proposed API14:22
greybackmhr3: for an apps scope?14:22
mhr3yes14:23
greybackmhr3: ok, let me know if that API is ok. jamesh had a look and approved14:23
mhr3greyback, ok cool14:23
sil2100mhr3: unity AP tests are running on jenkins, so far so good!14:38
mhr3sil2100, we have a nice saying for this14:39
mhr3something along the lines of "don't say hop before jumping over"14:40
didrocksSaviq: I'm "free the fish" ;)14:40
sil2100Right, in Poland we have the same thing ;)14:40
didrockssil2100: mhr3: did you get any interesting fix?14:40
didrocksor it's just a "let's try"14:40
sil2100didrocks: well, in a way, yes14:40
didrockson the interesting fix? ;)14:40
Saviqdidrocks, so, we now have a set of AP tests to run14:41
Saviqdidrocks, how do we try them out?14:41
sil2100didrocks: we disabled the failing powerpc test to unblock FTBFS, and jibel bumped the memory limit14:41
didrocksSaviq: we can add them to daily release and test them14:41
didrocksSaviq: what I need is the autopilot package name (unity8-autopilot)14:41
didrocksSaviq: and a command to run (unity8_autopilot?)14:41
Saviqdidrocks, yeah, but will we break *everything* in case of failure?14:42
Saviqdidrocks, autopilot run unity814:42
didrockssil2100: ah, let's cross fingers14:42
mhr3sil2100, bumped the mem limit? wasn't it about disabling rmd?14:42
didrocksSaviq: yeah, so just "unity8" ;)14:42
didrocksSaviq: what do you mean, by breaking "everything"14:42
sil2100didrocks: soooo, we might have a proper test result - if not, we publish anyway since mhr3 made manual tests, 2 test runs on ati and the results are: 16 failures and 17 failures14:42
sil2100So it's all in my tolerance threshold ;p14:42
Saviqdidrocks, at worst it will be limited to our stack, right?14:42
sil2100While intel had 1314:42
didrockssil2100: the results are a little bit higher than what it was14:42
Saviqdidrocks, which will go into manual publishing and we'll just not push unity8?14:42
didrockssil2100: so please, ensure it will go down then :)14:42
didrocksSaviq: yeah, if tests doesn't pass, nothing will publish14:43
didrocksSaviq: it will not push unity814:43
didrockswe can force the publication just in case14:43
didrocksbut it will block first14:43
Saviqdidrocks, yup14:43
Saviqdidrocks, ok, let's flip the switch, then :)14:43
didrockssil2100: time for that? ^14:43
didrocksSaviq: do we need to do anything special, we are in an unity7 session though14:44
didrocksso, do we need to kill anything and run unity814:44
sil2100!14:44
didrocksor do running the autopilot tests do that?14:44
sil2100Publication of unity8 ;p?14:44
didrockssil2100: having first tests running I guess :)14:44
didrocksso listing binaries from the stack14:44
didrockstest package14:44
didrocksand test to run :)14:45
sil2100didrocks: should I stop unity testing then?14:45
Saviqdidrocks, no, we should be able to just start unity8 in a window currently14:45
didrockssil2100: no no, we can let that run and prepare the unity8 config menawhile :)14:46
didrocksSaviq: so, the AP tests do that14:46
didrockswe just need to "run autopilot unity8"14:46
didrocks(in the unity7 desktop session)14:46
Saviqdidrocks, yup14:46
didrocksSaviq: excellent14:48
didrockssil2100: so having time for that configuration change? I can review it, shouldn't be a big deal I guess :) ^14:48
sil2100didrocks: sure ;)14:49
didrockssil2100: Saviq: let's keep next at the target until we land successfully once, right?14:49
sil2100I'll have to check the branch and such14:50
didrocksthen, we can look to dive into distro :)14:50
sil2100I mean, tests and such14:50
sil2100;p14:50
didrocksyep ;)14:50
Saviqdidrocks, well, MIR for unity8 is still away for some time ;)14:50
didrockssil2100: should be unity8-autopilot package and "unity8" as the autopilot command14:50
didrocksSaviq: right, people are still ok to go to next?14:51
sil2100I see the test_suite: indeed14:51
Saviqdidrocks, for the time being, yes14:51
didrocksok :)14:51
Saviqdidrocks, but we're pushing to change that asap14:51
didrockssil2100: really? :p14:51
didrockssil2100: I probably mislead with an IRC discussion ;)14:51
didrocksSaviq: ack!14:51
sil2100didrocks: brb in 5 minutes just! Need to jump outside to pick something up in front of my flat ;p14:55
sil2100https://code.launchpad.net/~sil2100/cupstream2distro-config/add_check_to_unity8/+merge/176407 <- work in progress, will have to check dependencies of dependencies15:02
didrocksbregma: http://10.97.0.1:8080/view/cu2d/view/Head/view/Unity/job/cu2d-unity-head-2.2check/15:10
mhr3bregma, too many crashes in the AP testing, the question is whether it's caused by recordmydesktop, or there's a regression in unity/nux15:20
mhr3bregma, could you look at it pls?15:20
mhr3bregma, i wouldn't be too surprised if unity was doing overzealous free-ing in some cases after all the mem fixes15:21
mhr3but then again it might be X/drivers/recordmydesktop, fwiw i didn't see it crash on my machine and i'm running from daily build ppa15:22
bregmathe oom-killer doesn't usually imply overzealous frees15:23
sil2100mhr3: HA!15:59
sil2100Just opened it as well!15:59
sil2100Still it's above our threshold, but at least it works - once armhf finished building I do a manual publish!15:59
sil2100mhr3: \o/15:59
sil2100\o\15:59
sil2100/o/15:59
mhr3sil2100, compiz still got killed a few times, that will be resonsible for a few failures16:00
sil2100Bummer16:00
mhr3sil2100, interesting difference http://imgur.com/TAzZVam16:03
mhr3you can pretty much see the crashes :)16:04
sil2100;D16:04
mhr3eh, yea... you could if screenshotting worked16:04
mhr3so once again16:10
mhr3http://imgur.com/xSLXaL516:10
mhr3sil2100, ^ now you can see them :)16:10
sil2100I wonder what causes those failures16:11
mhr3i don't want to know :P16:11
sil2100Let's leave it to the unity guys ;p16:11
davmor2sil2100: is playing stickman goalie16:12
mhr3sil2100, so is publishing to s underway? can we expect new stack tomorrow?16:18
sil2100mhr3: we just going to finish our desktop meeting and I'm on it16:18
mhr3finally some good news16:20
sil2100mhr3: let's browse through again through those failing AP tests and check if any of them are blockers or not16:29
sil2100mhr3: and let me fill a bug for compiz crashes, at least a non-detailed one16:29
sil2100mhr3: too bad the machines are not logging to /var/crash ;/16:30
mhr3sil2100, we still don't know whether they're "real" or recordmydesktop+lxc16:30
sil2100No apport dumps ;/16:30
sil2100mhr3: oh oh, I see one test left gedit open, so this might cause some failures as well16:34
mhr3sil2100, see, and there were still just 17failures :)16:35
mhr3sil2100, so perhaps not everything is dark and gloom16:35
mhr3sil2100, so do you want to go over all of them?16:36
mhr3hangout?16:36
sil2100mhr3: I guess it's not needed16:39
sil2100mhr3: I see that we have 16 threshold, so we're below that - we of course broke the other threshold, the number of regressions ;p16:40
sil2100But well, let's just take a blind eye on that16:40
mhr3there's a limit on number of regressions?16:40
sil2100Yes, if there's too many regressions in relation to previous successfull runs, it notes a run as failed if there's a too big difference (over 6 new failures)16:42
sil2100But, pssst, let's just say it's ok today16:42
sil2100I browsed through the vids and those seem mostly issues with AP16:42
sil2100WHAT THE FUCK16:43
sil2100armhf FTBFS16:43
sil2100Trevinho: damn you for all those unit tests! DAMN YOU!16:43
sil2100:D16:43
sil2100https://launchpadlibrarian.net/145690384/buildlog_ubuntu-saucy-armhf.unity_7.0.2%2B13.10.20130723.1-0ubuntu1_FAILEDTOBUILD.txt.gz16:43
sil2100I'm trying a re-run16:43
Trevinhosil2100: oh... :P16:44
sil2100But THIS, this just pissed me off! We were soo close to release ;/ Now again we need to wait another 2 freaking hours for armhf to finish16:44
Trevinhosil2100: oh, that ramonly fails on slow hardware16:44
sil2100Trevinho: noooo~!16:44
Trevinhosil2100: in case we can increase the timeout for that, but it's already pretty high16:44
Trevinhosil2100: but it actually wasn't failing for looooong time on CI or Autolanders16:45
sil2100didrocks: what would happen if I published unity without a armhf binary in the daily-build PPA? Is there a binary copy made?16:45
sil2100Trevinho: indeed! I didn't see it failing on the previous run as well16:45
sil2100It seems unity is cursed16:45
sil2100Something doesn't want it released16:45
didrockssil2100: it will try to rebuild on armhf in proposed16:45
didrockssil2100: if it fails as well, it will be blocked on proposed16:46
sil2100didrocks: so, can I just proceed with the publish step without armhf built? Since the problem seems to be a 'slow machine' random thing16:46
didrockssil2100: yes you can, but ensure it won't stay stuck in proposed16:46
didrocksand it's really a random thing16:46
didrocksthat will get fixed16:46
Trevinhosil2100: however I know that tests can be annoying, but if we want quality checks we need them, This also made us to improve some other components such as libunity and libdee... So, I know it can be disappointing, but we have to. On the other side we must prevent any false-negative result...16:47
=== dandrader_ is now known as dandrader
mhr3Trevinho, unless there's a threading race :P16:47
Trevinhomhr3: yeah :)16:47
sil2100Trevinho: we know we know ;) I'm just mad because it was hindering my release! :P16:47
didrockssil2100: but if it's getting stuck, and we only deliver half of the thing, we need to ensure there is no ABI break that were not spotted16:47
didrockssil2100: so warning to ensure you don't break a bunch of our users :)16:48
=== dandrader is now known as dandrader|lunch
Trevinhosil2100: in the mean time, it's fine if you set the timeout for that test to 30 seconds... It pass here in just less than one... but arm seems so slow16:48
* sil2100 is very desperate16:48
mhr3Trevinho, hm... arm isn't that slow, there'll be a rare threading issue16:50
Trevinhomhr3: probably....16:51
sil2100didrocks: ekhm ;) I know it's late, but maybe you could do some packaging ACKs?16:53
sil2100didrocks: it's rather safe as mhr3 is using daily-build unity for some time now16:54
didrockssil2100: right, but let's imaging armhf can't be build in distro as well16:54
didrocksso, it will get stuck in -proposed16:54
didrocksthe rest will migrate to the release pocket16:54
didrocksand it's not a tested experienced16:54
mhr3sil2100, it scares that you point it out, shouldn't that be the case for anyone who does unity changes?16:55
sil2100mhr3: I guess it should! ;)16:55
sil2100didrocks: right, but this test never failed before, and between this run and the previous one there were no changes in trunk actually16:56
Saviqgreyback, btw, didn't read properly but we're not having "2 independent scenegraphs" - that's the whole problem ;)16:56
Saviqgreyback, we have "2 interdependent scenegraphs"16:56
didrockssil2100: if you stay to ensure it's not blocked in proposed, I'm fine16:56
didrocksso that we don't wake up with thousands of broken laptop :)16:56
didrocksor play it safe and so, the rebuild should pass? ;)16:57
sil2100didrocks: ok, so let's do it like this - could you check the changes, ACK them and I'll wait for the armhf bits to finish building in the PPA16:57
didrocksok16:57
didrocksseems safer to me16:57
sil2100If it passes, then we'll have a safer release ;p16:57
sil2100And I'll publish then16:57
didrocksindeed ;)16:57
sil2100didrocks: http://10.97.0.1:8080/view/cu2d/view/Head/view/Unity/job/cu2d-unity-head-3.0publish/108/artifact/packaging_changes_libunity_7.0.9+13.10.20130723-0ubuntu1.diff <- libunity ABI break, oh noes16:57
greybackSaviq: well depends on how you define dependency. The scene graphs don't need each other. But the QML engine will be controlling both of them16:58
didrockssil2100: hum, still libunity916:58
didrockssil2100: is that a real ABI break, what will be impacted?16:58
Saviqgreyback, yeah, that could be16:58
sil2100mhr3: ^16:58
sil2100didrocks: I see a lot of symbols removed, so hm16:59
didrockssil2100: like, this is an example, if libunity pass in the release pocket, will old unity still work16:59
mhr3sil2100, it's hiding all unity_internal_*16:59
didrocks(and old scopes)16:59
didrocksmhr3: not only apparently?16:59
sil2100Ok, so it's safe?16:59
didrocks- unity_dee_result_set_construct@Base 7.0.0daily13.05.31ubuntu.unity.next16:59
sil2100mhr3: - unity_dee_result_set_construct@16:59
didrocks-> not really internal :p16:59
Saviqdandrader|lunch, hey, when's your EOD today?16:59
mhr3didrocks, and moving to internal what should have been :)16:59
sil2100Is that internal ?16:59
sil2100Ah16:59
sil2100hmmm16:59
didrocksmhr3: but it doesn't shift any struct?16:59
mhr3no16:59
didrocksok ;)16:59
didrockssil2100: so +117:00
sil2100didrocks: http://10.97.0.1:8080/view/cu2d/view/Head/view/Unity/job/cu2d-unity-head-3.0publish/108/artifact/packaging_changes_nux_4.0.2+13.10.20130723-0ubuntu1.diff <- nux ABI break ;p17:00
didrockswhat a surprised… :p17:00
didrockssurprise*17:00
sil2100didrocks: http://10.97.0.1:8080/view/cu2d/view/Head/view/Unity/job/cu2d-unity-head-3.0publish/108/artifact/packaging_changes_unity-lens-friends_0.1.3+13.10.20130723-0ubuntu1.diff <- version bump17:00
didrockssil2100: +1 on nux17:00
didrockssil2100: fine on lens-friends17:01
sil2100didrocks: http://10.97.0.1:8080/view/cu2d/view/Head/view/Unity/job/cu2d-unity-head-3.0publish/108/artifact/packaging_changes_unity_7.0.2+13.10.20130723.1-0ubuntu1.diff <- ok, this one is big, still didn't finish checking it ;/ But I guess it's also related to the nux and libunity bumps17:01
didrocksurgh wrap and sort :/17:02
didrocksthat really sucks :/17:02
sil2100Yes, it makes the diff unreadable ;/17:02
sil2100xserver-xorg-video-dummy dep was added17:03
didrockssil2100: ok, sounds legit (and in main)17:03
didrockssil2100: anything else to +1?17:05
sil2100didrocks: that's all :)17:05
* sil2100 waits for armhf17:05
didrocksok, great! :)17:05
didrocksgood luck ;)17:05
sil2100didrocks: thanks!17:05
sil2100:)17:05
didrocksyw, thank to you!17:05
sil2100bschaefer, bregma, Trevinho, andyrock: hi guys! https://bugs.launchpad.net/unity/+bug/1204188 <- could you take a look in some free time?17:10
ubot5Launchpad bug 1204188 in Unity "New Unity autopilot failures in the unity stack" [Medium,New]17:10
sil2100So that we can get the number of failures down \o/17:10
sil2100Thanks!17:10
bregmasil2100, already working on it, but don;t get your hopes too high :)17:10
bschaefersomeone mentioned free time?!17:10
bregmabschaefer, yes, we're shipping you a new lot but it's being held at the border17:11
bschaeferbregma, haha, i need my fix17:11
bschaefersil2100, cool, Ill try to take a look at some point ....17:11
sil2100Thanks guys, could you assign someone etc. to that bug? So that we can get it 'formalized' ;p17:11
bregmasil2100, it's more likely there are at least 17 individual bugs that need to be addressed17:12
sil2100bregma: right, I just filled in one so that it's documented in any way, that distro knows why we might be delaying some things17:14
bregmasil2100, we'll take care of it17:14
Trevinhosil2100: mh, not sure they really depend on us or on the indicator team17:18
Trevinhosil2100: the latests indicators stack seems a litlte unstable here yet..17:18
dandrader|lunchSaviq,  around 22:00 UTC I guess17:33
sil2100Trevinho: uuuh, well, then I'll have to harrass them to put more AP tests!17:36
sil2100Trevinho: or, maybe, it would be a good idea to refresh the list of tests ran on indicators? Let me note that down17:37
Trevinhosil2100: I mean, we changed nothing on that side, so... it seems more likely to be an indicators issue, but this statement is not based on real local testing here... just an impression17:38
Saviqdandrader|lunch, wanted to drop on you a potential Hud issue, but it seems it's not our fault in the end ;)17:42
bschaefersil2100, hey, soo i've this ibus 1.5 fix, and you poked around the ibus AP tests quite a bit18:13
bschaefermind doing a review?18:13
bschaefer(if you have any freetime...)18:13
bschaeferhttps://code.launchpad.net/~brandontschaefer/unity/lp.1203106-fix18:13
=== dandrader|lunch is now known as dandrader
TitusJhi everbody!19:43
=== dandrader is now known as dandrader|afk
=== dandrader|afk is now known as dandrader
marlinchttps://plus.google.com/102031545913933941769/posts/7rE4eq5GBiW22:20
=== salem_ is now known as _salem

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