/srv/irclogs.ubuntu.com/2014/01/08/#ubuntu-ci-eng.txt

=== vila changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: vila | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
Mirvok, now everything should be properly compiled, I can start device testing + try to get also unity8 stack cu2d tests to run09:01
didrocksMirv: excellent! :)09:08
didrocksstill not sil2100. I'm starting to be worry09:08
* didrocks sent a mup sms09:10
didrockspopey: joining?09:31
popeyis that the time!09:31
popeysorry09:31
didrocksit definitively is :)09:31
popeybug 1262607 really is quite annoying09:37
ubot5bug 1262607 in friends (Ubuntu) "Social notifications only appear after mediaplayer is opened" [Undecided,In progress] https://launchpad.net/bugs/126260709:37
Mirvok finally I have the right bugs bookmarked..09:46
ogra_didrocks, do we know if the proposed Mir branch will have the fix for bug 1258056 ? else i have to postpone the nested Mir migration for the session stuff10:54
ubot5bug 1258056 in Mir "nested mir on android fails on galaxy nexus" [High,Fix released] https://launchpad.net/bugs/125805610:54
didrocksogra_: I know there are something for nested Mir10:54
ogra_ah, great10:55
ogra_it is really annoying that these bugs have no distro task at all so one can see if it landed in the archive or not10:55
didrocksogra_: I just bzr branch lp:mir, bzr merge that associated branch and:10:56
didrocksNothing to do.10:56
didrocksso it will be there10:56
ogra_great10:56
didrocksogra_: if it landed in the archive and is associated to a branch, it should have a distro task10:56
didrockscu2d opens it to track10:56
didrocksso it's not in yet :)10:56
ogra_took 30min of my workday to dig through several different branches where a simple bug task would just have told me10:56
didrockswell, talk to upstream ;)10:57
ogra_yeah, i guess i should10:57
psivaaogra_: didrocks: reverting apport and whoopsie-preferences did not help make the mako connected tests pass.11:05
psivaabut i am having trouble reverting lxc-android-config11:05
ogra_what is the issue ?11:05
psivaagetting 'unable to make backup link of `./lib/udev/rules.d/70-android.rules' before installing new version: Invalid cross-device link' when installing the previous version of that11:05
ogra_aww11:06
ogra_yeah, that wont work then, dpkg uses hardlinks ... hardlinks dont work across partition boundaries iirc11:06
ogra_you should be able to manually hack the files it changed though11:06
psivaaogra_: http://pastebin.ubuntu.com/6714223/ for more info..11:06
ogra_without reverting the package11:06
psivaaok, i'll try that then. thanks11:07
ogra_http://launchpadlibrarian.net/161740340/lxc-android-config_0.125_0.126.diff.gz11:08
ogra_/etc/system-image/writable-paths11:08
cjwatsonhard links> yes, this is another reason why attempting to make individual files writable is fundamentally doomed11:13
cjwatsonthis *has* to be done at the directory level only11:13
=== vrruiz_ is now known as rvr
=== Ursinha is now known as Ursinha-afk
psivaaogra_: didrocks: reverting lxc-android-config does not help either.. i am now installing on a different mako to see if there is any improvement11:47
didrockspsivaa: yeah, and meanwhile I would suggest as well trying to flash the failing mako with the previous image as well11:48
ogra_well, apport was only a straw ... since the changelogs didnt show anything else that could be at fault11:48
ogra_was there an android change ?11:48
ogra_iirc the last upload didnt make it out of proposed (at least when i looked last night)11:48
didrocksogra_: the android change AFAIK was in 11711:49
ogra_i thought it was still sitting in proposed11:49
didrocks116:20140107:20131223.211:49
didrocks117:20140107.1:20140107.111:49
didrocks         ^ it's the last bug, right?11:50
didrocksbit*11:50
didrocks:20140107.111:50
ogra_https://launchpad.net/ubuntu/trusty/+source/android/20131202-2236-0ubuntu711:50
ogra_sigh11:50
ogra_i wish these numbers would be connected in any way11:50
ogra_but yeah, looks like it has the new android11:50
didrocksok, so it's not part of what failed on 11711:51
MirvSaviq: didrocks: it currently looks like I'm getting a crash with Unity8 with the new Mir 0.1.3 repeatedly when running phablet-test-run -n unity8. backtraced it https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/126706511:52
ubot5Error: ubuntu bug 1267065 not found11:52
didrockskgunn: as well, FYI ^11:52
didrocksMirv: ok, concentrate on the other landings then11:52
SaviqMirv, can you attach your unity8.log please?11:53
Mirvdidrocks: I mostly concentrate on Qt but I try to get powerd also on the side11:53
didrocksMirv: would be nice to have powerd released today11:53
MirvSaviq: isn't the upstart log there automatically already?11:53
MirvSaviq: the threadstack trace mentions Mir in there11:54
Mirvdidrocks: ok, I'll update on it later11:54
didrocksthx!11:54
SaviqMirv, it is, sorry11:54
SaviqMirv, did you keep your screen on?11:55
Saviq  what():  could not activate surface with eglMakeCurrent11:55
Saviqgreyback, that's↑happening when display is off, right?11:55
greybackSaviq: yes. I think if screen off, you start unity8, then try to turn on screen, that happens too11:56
SaviqMirv, it's best if you go "powerd-cli display on bright" when running the test suites11:57
* Saviq tries11:57
MirvSaviq: just screen on & unlocked + phablet-test-run -n unity8. of course eventually the screen is black, I guess after the crash and when the rest of the tests then fail.11:57
SaviqMirv, yeah, but that crash is a result, not the cause11:57
* Saviq tests11:58
=== vila changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
SaviqMirv, basically what happens: unity8 gets stopped, but takes a long time to exit (that's something we still need to investigate - either it's a crash and apport collects data or it's just unity8 taking a long time to exit)12:02
SaviqMirv, long enough that screen suspends12:02
SaviqMirv, subsequent tests crash due to screen being off - and that's the .crash file you got12:03
=== ev changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cprov | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
MirvSaviq: I guess a crash is something that shouldn't happen anyhow, but yes thanks for the powerd-cli tip I'll add it to my testing plan. currently testing powerd from a clean slate + trying to get that %=!"$ qtdeclarative snapshot problem understood.12:20
SaviqMirv, of course, unity8/mir should start fine with screen off, that's a known bug12:20
Saviqand it has a nice round number - bug #123500012:21
ubot5bug 1236525 in unity-mir "duplicate for #1235000 unity8 killed/crash then restart can result in mir unable "could not unblank display"" [Medium,Triaged] https://launchpad.net/bugs/123652512:21
SaviqMirv, yeah, 25 unity8 tests passed with screen on12:39
Saviqand no crash12:39
* kgunn is doing morning house duties but reading scrollback on mir testing12:42
=== alan_g is now known as alan_g|afk
Mirvdidrocks: packaging ack http://q-jenkins.ubuntu-ci:8080/view/cu2d/view/Head/view/Platform/job/cu2d-platform-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_powerd_0.13+14.04.20140108.1-0ubuntu1.diff12:50
MirvSaviq: I didn't need that last year, but yes I could retest after reflashing, I just fear I don't have time to run all tests today anymore but I should be able to upgrade Mir again and run unity8 at least12:51
MirvSaviq: that = powerd-cli12:52
didrocksMirv: +112:52
Mirvthanks12:54
=== alan_g|afk is now known as alan_g|lunch
SaviqMirv, that's because we (upstart) killed unity8 after 5s before - no time for screen to suspend12:57
SaviqMirv, i.e. bug #126037912:57
ubot5bug 1260379 in Unity 8 "A unity8.override file should be shipped to allow apport completion during test runs" [High,Fix released] https://launchpad.net/bugs/126037912:57
SaviqMirv, but also bug #126287912:57
ubot5bug 1262879 in Ubuntu CI Services "There should only be one, documented, way to run tests on devices" [Undecided,Confirmed] https://launchpad.net/bugs/126287912:57
SaviqMirv, i.e. smoke testing keeps the screen on throughout the whole suite12:58
xnoxSaviq: one can raise kill timouts on per job basis.12:59
xnox(or via .override file during tests)13:00
Saviqxnox, that is per-job13:00
Saviqxnox, https://code.launchpad.net/~nicolas-doffay/unity8/upstart-kill-fix/+merge/19893113:00
xnoxcool =)13:01
xnoxSaviq: why not simply adjust the stock unity8.conf, if you are changing that by default anyway.13:01
xnoxSaviq: since that .override will not be used btw in the default testing, since a different .override is dropped in the user directory. And upstart only applies "one best .override" on top of "one best .conf"13:03
Saviqxnox, we don't want people actually *using* the phone to have to wait 30s13:03
Saviqxnox, what "different .override"?13:04
xnoxSaviq: but that's  what you did anyway =)13:06
xnoxSaviq: so user-session jobs are loaded from: ~/.config/upstart/ , $XDG_CONFIG_DIRS/upstart, /usr/share/upstart/session/. Whichever first one is found.13:06
xnoxSaviq: then a second pass is searched in all the same locations for $name.override, and is applied on top.13:07
xnoxSaviq: so a default install, at the moment, will have /usr/share/upstart/session/unity8.conf and /usr/share/upstart/session/unity8.override, which are merged together in memory and then the job is started with _all_ those parameters.13:08
xnoxSaviq: so your change did make 30s timeout across the board, always.13:08
Saviqxnox, we only install it with the unity8-autopilot package13:09
xnoxSaviq: if you look into lp:ubuntu-test-cases/touch however, it drops an unity8 overrides to start unity in testability mode. Since, as far as I remember, it uses .override file and thus overrides the global one you created.13:09
xnoxSaviq: and unity8-autopilot is not on the default image?13:09
Saviqxnox, nope13:09
Saviqxnox, I didn't know about the other override, that should include the kill timeout change, too, then13:11
Saviqlet me mention bug #1262879 again...13:11
ubot5bug 1262879 in Ubuntu CI Services "There should only be one, documented, way to run tests on devices" [Undecided,Confirmed] https://launchpad.net/bugs/126287913:11
xnoxSaviq: let me first find for sure where it is.13:11
xnoxSaviq: utils/target/unlock_screen.py:    os.system('echo "exec unity8 -testability" > ~/.config/upstart/unity8.override')13:12
xnoxSaviq: in lp:ubuntu-test-cases/touch13:13
xnoxSaviq: I think it's best for lp:unity8 to add "exec unity8 -testability" to unity8.override (now that you are shipping an override file) and drop unity8.override from any/all test-harnesses.13:13
=== Ursinha-afk is now known as Ursinha
xnoxSaviq: is -testability actually at all needed / supported these days?13:14
xnoxSaviq: i get a lot of:13:15
xnox/usr/bin/system-settings: invalid option -- 't'13:15
xnox/usr/bin/system-settings: invalid option -- 'e'13:15
xnox/usr/bin/system-settings: invalid option -- 's'13:15
xnox/usr/bin/system-settings: invalid option -- 't'13:15
xnox/usr/bin/system-settings: invalid option -- 'a'13:15
xnox/usr/bin/system-settings: invalid option -- 'b'13:15
xnox/usr/bin/system-settings: invalid option -- 'i'13:15
xnox/usr/bin/system-settings: invalid option -- 'l'13:15
xnox/usr/bin/system-settings: invalid option -- 'i'13:15
xnox/usr/bin/system-settings: invalid option -- 't'13:15
xnox/usr/bin/system-settings: invalid option -- 'y'13:15
xnoxand then "Testability driver loaded"13:15
ogra_xnox, pastebinit !13:15
ogra_(and thats normal)13:15
xnoxogra_: why is that normal to specify option, which doesn't exist?13:15
ogra_i mean the output is13:16
xnoxogra_: no that is not normal, to self-induce invalid  / obsolete options. Just wait for qmlscene or any app use one of those single letter options and explode.13:17
ogra_xnox, it is in all test logs since day one like that13:17
ogra_which makes it a "normal" output for me since it does not affect anything13:17
ogra_(i agree it is crap, but it shouldnt cause any issues, all test logs have it since forever)13:18
Saviqxnox, the preferred way is to export QT_LOAD_TESTABILITY=113:19
Mirvdidrocks: Saviq: kgunn: ok I've resumed Mir 0.1.3 testing with Saviq's tip and everything seems ok so far. I look if I get the remaining tests done and/or update the chart for others to continue from where I left off.13:33
SaviqMirv, thanks!13:33
didrocksexcellent!13:35
balloonscprov, can you look at why this is failing to autoland? https://code.launchpad.net/~andrew-hayzen/ubuntu-ui-toolkit/fix-swipe-delete-001/+merge/199906. We had to re-run yesterday before it would work, but I'm not sure why13:41
cprovballoons: will do13:41
=== alan_g|lunch is now known as alan_g
cjohnstonballoons: it has failing tests13:49
cprovballoons: testing are failling13:49
fginthermorning13:49
balloonscjohnston, cprov I see that, but tim was thinking something wasn't right.. And nothing has changed since yesterday. Anyways, I'll send it back to him, thanks13:50
Mirvdidrocks: in case all fine, could you pre-ack packaging changes? http://www.multiurl.com/l/gHX (couldn't find better for clickable links)13:52
MirvI see dialer-app and messaging-app are also broken in image 118, which is "good" in the sense that the failures I saw were not from Mir13:52
Mirv(image 118 test results)13:53
timpcprov: hello13:56
timpcprov: I understand you were talking to balloons about https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/4469/testReport/junit/ubuntuuitoolkit.tests.test_emulators/TabsTestCase/test_swith_to_tab_by_index_out_of_range/ ?13:56
cprovballoons: we found a problem in the testing env, apparently qmlscene crashed13:56
timpepaste, I mean this one: https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/4469/13:56
balloonscprov, :-p13:56
balloonsgl13:56
cprovhi timp13:56
ogra_cprov, !!!13:56
timpcprov: ah. I guessed something like that :) all tests failed on a missing dbus13:56
* ogra_ hugs cprov 13:57
cprovogra_: hey hey, good to see you again!13:57
ogra_yeah, same :)13:57
cprovtimp, balloons: bear with me while the experts look at a solution.13:57
timpcprov: sure, thanks13:58
cprovtimp: do you remember a similar problem in the past ? related, possibly, to a Mir regression ?14:07
timpcprov: I remember that we had this problem a lot in the past14:08
timplet me think if I remember what caused it; may be mir-related14:08
cprovtimp: right, fginther is investigating it14:08
timpcprov: perhaps the screen was not activated?14:08
timpkalikiana_: ^ do you remember what was causing this kind of failures for us? https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/4469/testReport/junit/ubuntuuitoolkit.tests.test_emulators/TabsTestCase/test_swith_to_tab_by_index_out_of_range/14:09
fginthercprov, timp here's the bug I was thinking of: https://bugs.launchpad.net/qtubuntu/+bug/124366514:09
ubot5Ubuntu bug 1243665 in qtubuntu "qmlscene crashed with SIGABRT in QMessageLogger::fatal()" [Critical,Confirmed]14:09
timpelopio_: ^ perhaps you worked on these kind of failures? https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/4469/testReport/junit/ubuntuuitoolkit.tests.test_emulators/TabsTestCase/test_swith_to_tab_by_index_out_of_range/14:09
psivaadidrocks: ogra_: "base-passwd from 3.5.29 to 3.5.30" appears to be the reason for the mako connected test failures14:10
timpfginther: I'm not sure. I saw the failures a lot and if I recall correctly they were happening at random. But I didn't investigate it further. I guess that was kalikiana_ or elopio_ , or someone in the CI team14:11
cjwatsonpsivaa: *perks up*14:11
cjwatsonpsivaa: log?14:11
fginthertimp, my IRC logs show that I was discussing this with kalikiana_ last month14:11
kalikiana_timp: yes I think this is the qubuntu bug. the error is in the logs before the python error14:11
ogra_psivaa, wow14:12
ogra_thats curious14:12
cjwatsonogra_: it was a fairly substantial change14:12
psivaacjwatson: i dont have specific logs.. but reverting that make the test pass14:12
cjwatsonthough this is the first problem I've heard of from it and I've been watching14:12
timpkalikiana_: so the bug came back today..14:12
cjwatsonpsivaa: I'm going to need some kind of log of the failure14:12
psivaacjwatson: i know it wont be helpful but it's http://q-jenkins.ubuntu-ci:8080/job/psivaa-trusty-touch-mako-smoke-messaging-app-autopilot/15/console vs http://q-jenkins.ubuntu-ci:8080/job/psivaa-trusty-touch-mako-smoke-messaging-app-autopilot/16/console14:13
psivaabut let me check if there is anything in the auth.log14:13
fgintherkalikiana_, timp any idea why it's still showing up? has it not been fixed?14:13
kalikiana_timp: fginther I recall it was "fixed" when fginther and I were looking at it and https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1262982 is still open because only part of the problem was addressed14:15
ubot5Ubuntu bug 1262982 in unity-mir "dialer-app crashed: QUbuntu: Could not create application instance" [High,Confirmed]14:15
cjwatsonright, so assuming base-passwd was upgraded successfully, the difference is that a bunch of system users that never should have had valid login shells (a long-standing security issue) now really don't have valid login shells14:16
kalikiana_greyback was offering to try to reproduce, that's the last I remember14:16
=== elopio_ is now known as elopio
=== cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: retoaded | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
* cprov leaves for a quick lunch and will brb14:19
cjwatsonpsivaa: auth.log might well be helpful, indeed14:19
=== cprov is now known as cprov-afk
greybackkalikiana_: could you log a bug with unity-mir, giving me steps to try to reproduce it? Just for my records (as I forgot about this)14:19
greybacktimp: ^^14:19
timpgreyback: I don't know how to reproduce it, I only saw the failing tests in an MR that I was reviewing14:20
fginthergreyback, we have another qmlscene crash here: https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/4469/14:21
timpfginther: do you know if it is an existing bug or do we need a new one?14:21
greybackfginther: the output from unity8 in those cases is valuable. Is it possible to get that?14:21
greybackas unity8 usually will say why it rejects the connections in it's own logs14:22
timpgreyback: https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/4469/artifact/results/log/unity8.log ?14:22
kalikiana_greyback: this is there https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/126298214:22
ubot5Ubuntu bug 1262982 in unity-mir "dialer-app crashed: QUbuntu: Could not create application instance" [High,Confirmed]14:22
fginthertimp, I don't know if this relates to the prior bug, could someone trace the crash file?14:22
fginther(someon who might know what to look for :-) )14:23
timpfginther: I don't know what you mean with that. Is there some specific log file that jenkins gives us that someone needs to have a look at?14:24
fginthertimp, the qmlscene crash file14:24
greybackkalikiana_: ah, thanks14:24
fgintherhttps://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/4469/artifact/results/crash/_usr_lib_arm-linux-gnueabihf_qt5_bin_qmlscene.32011.crash14:24
fgintherthere's also a unity8 crash14:24
timpfginther: that's a job for someone in the unity8 or mir team?14:25
timpfginther: I'm looking at it but it doesn't mean much to me14:25
greybacktimp: there's no "REJECTED" error messages, meaning unity8 isn't explicitly rejecting any applications, so that's not the cause of the crash14:26
greybacktimp: but that log has lots of unity8/mir crashes, which doesn't look right not me at all14:26
greybacks/not/to/14:26
greybackfginther: for that case, I'm suspecting a mir failure causing clients to crash14:27
greybackterminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::logic_error> >'14:28
greyback  what():  compositor_acquire would block; probably too many clients.14:28
greybacknever seen that before anyway. Will need Mir team help14:28
fginthergreyback or timp, can you file a bug if one doesn't already exist?14:30
psivaacjwatson: http://pastebin.ubuntu.com/6715060/ is the auth.log with v3014:34
psivaahttp://pastebin.ubuntu.com/6715062/ is with v29 (passing one)14:34
cjwatsonok, so what's trying to su to nobody?14:35
timpgreyback: ^ can you report the bug if needed? I don't really know what's going on14:35
kalikiana_but there is a bug…14:35
cjwatsonpsivaa: where would I find the top-level test scripts being run here?14:36
greybacktimp: I'm extending that bug14:37
timpkalikiana_: that's why I said "if needed" :)14:37
timpgreyback: ok, thanks14:37
psivaacjwatson: http://bazaar.launchpad.net/~phablet-team/messaging-app/trunk/view/head:/tests/autopilot/messaging_app/tests/test_messaging.py contains the tests14:38
cjwatsonhm, that's not the cause ...14:39
cjwatsoncould be utah, but utah seems to use sudo to get at the "nobody" user and sudo apparently doesn't care that the target user doesn't have a login shell14:40
psivaacjwatson: utah is not involved here14:40
psivaahmm probably it does.. not sure :)14:41
cjwatsonpsivaa: where does generic-mediumtests-runner-mako live14:42
cjwatson?14:42
psivaacjwatson: http://s-jenkins.ubuntu-ci:8080/job/generic-mediumtests-runner-mako/14:43
cjwatsonpsivaa: I mean the code14:43
cjwatsonthe actual test runner itself14:43
greybackfginther: timp can either of you tell me, is unity8 restarted for each and every test?14:44
psivaacjwatson: http://bazaar.launchpad.net/~canonical-ci-engineering/jenkins-launchpad-plugin/autopilot-testrunner-touch-saucy/files14:45
psivaai think that's where it is. and if that's what you're looking for :)14:45
cjwatsonpsivaa: maybe ... it would be useful if you happened to have a jenkins console log that matches your auth.log dump, so that I can compare timestamps usefully between them14:49
cjwatsonI'm flailing14:49
cjwatsonI guess I know it comes before the unlock_screen.py call in run_all_autopilot.sh14:50
* cjwatson tries grepping his oldish emulator tree14:52
dobeydidrocks: https://code.launchpad.net/~dobey/cupstream2distro/native-versions/+merge/20073614:54
didrocksdobey: did you try it with SRU mode, dest ppa and so on?14:55
didrocks(I don't see tests for those cases)14:55
dobeydidrocks: didn't know there were extra tests for those. i can add them if they are necessary. what is "SRU mode" though?14:57
didrocksdobey: there is a dest ppa but it's not reflected in versioning (the +series is different, that's it)14:57
didrocksdobey: should be transparent for you, just look at the test cases, I'm sure there is one for dest ppa at least, not sure for SRU mode (there is none if it's transparent to it)14:58
cjwatsonpsivaa: or failing that, perhaps I could have a tarball of all of /var/log/ ?  Ideally from the failing case, but the successful case would be better than nothing14:58
dobeydidrocks: ok14:59
cjwatsonI've grepped all the source I can think of and can't find this su call14:59
didrocksdobey: with that, I'm happy to approve your merge, will count on you to support it if further issues are involved though :)15:00
psivaacjwatson: just a reboot prints this in auth.log without any tests being run.15:00
psivaahttp://pastebin.ubuntu.com/6715183/15:00
didrocks(I still don't like we are introducing inconsistencies but if some upstream are puzzled about the packaging, they will talk to you I guess)15:00
psivaabut i'll get the tarball15:00
cjwatsonpsivaa: ok, that usefully rules out a bunch of stuff15:00
didrocksdobey: I guess you need to test for a second release the same day as well15:01
dobeydidrocks: ok15:01
rsalvetididrocks: Saviq: not sure if a regression, just moved bug 1267076 to unity815:01
ubot5bug 1267076 in unity8 (Ubuntu) "swipes on thumbnail crashes unity8" [Undecided,New] https://launchpad.net/bugs/126707615:01
didrocksrsalveti: oh indeed, not sure either. Will try to flash an older one15:02
didrocksSaviq: tell us if you have any idea15:02
didrockspsivaa: cjwatson: what do you think about, if we can't find the reason (which is probably in the testing tool with invalid usage) in 1 or 2 hours to revert the change and take some quiet time to continue the investigation? Does it makes sense Colin?15:04
Saviqdidrocks, not a regression15:05
Saviqdidrocks, bug #124040815:06
ubot5bug 1240408 in unity8 (Ubuntu) "unity8 crashed with SIGSEGV in QCoreApplication::postEvent()" [Medium,Confirmed] https://launchpad.net/bugs/124040815:06
didrocksSaviq: I never had enough music icons to create the carroussel. I should add more I guess :)15:06
didrocksok, thanks Saviq, rsalveti ^15:06
Saviqdidrocks, yeah I know15:06
didrocksSaviq: I'll let you dupe it?15:06
Saviqdidrocks, already done15:06
didrockssooo quick :)15:06
fginthergreyback, unity8 is restarted and the phone is rebooted between test suites, but not between individual test cases15:08
rsalvetiawesome, thanks!15:10
greybackfginther: thanks for the clarification.15:10
psivaacjwatson: just sent an email with the logs15:13
=== cprov-afk is now known as cprov
psivaacjwatson: also, http://ci.ubuntu.com/smokeng/trusty/touch/mako/118:20140108:20140107.1/5941/messaging-app-autopilot/ has some logs attached at the bottom15:18
cjwatsondidrocks: ETA 20min to upgrade my device to a vaguely recent devel, after which I should stand a better chance15:19
cjwatsonpsivaa: thanks15:19
didrocksthanks, keep us posted15:20
* ogra_ finds the discovery that we have anything su'ing to nobody worrying enough :)15:21
didrocksogra_: nobody isn't a friend of yours? :)15:22
cjwatsonogra_: quite15:22
ogra_didrocks, i dont like perfect people ... :P15:22
cjwatsonthe trivial workaround is to pass "-s /bin/sh" to su, once we find the call15:22
didrocksahah15:23
cjwatsonassuming we don't find that it's better to use a different user15:23
ogra_yeah, i would prefer the latter15:23
cjwatsonwell15:23
cjwatsonrunning things as nobody isn't necessarily wrong - what would be wrong is if it ended up using any files15:23
cjwatsonbut we'll see15:23
cjwatsonsorry, I mean owning any files15:23
ogra_yeah15:24
cjwatsonhopefully it's reproducible on grouper15:24
psivaacjwatson: assume you are not running the test to reproduce the issue. phonesim is needed to run that particular failing test15:29
cjwatsonpsivaa: no need since you established that the su call is visible on a simple reboot15:33
=== alan_g is now known as alan_g|tea
psivaacjwatson: ack, confirmed that again15:34
=== alan_g|tea is now known as alan_g
cjwatsonbah, there's no indication of that su call in auth.log on grouper15:50
* cjwatson tries devel-proposed15:50
ogra_on what device do you see that su call ?15:50
cjwatsonogra_: mako15:51
cjwatson(apparently)15:51
cjwatsonogra_: can you see if you have it?15:51
ogra_maguros pvrsrv thing that runs on the android side does weird stuff to get the graphics driver up ...15:51
ogra_ah, mako, k15:51
cjwatsonthis doesn't look like android-side15:51
ogra_right15:51
cjwatsonif it were, it surely wouldn't have been affected by a base-passwd change15:51
ogra_root@ubuntu-phablet:/# grep su /var/log/auth.log15:52
ogra_root@ubuntu-phablet:/#15:52
ogra_thats my mako, recent promoted image, upgraded today15:52
ogra_(note my mako is my actual phone, i wont run tests on it, but popey has a test device he could run tests on)15:53
cjwatsonI suppose it could be due to some set of installed test packages15:53
cjwatsonpsivaa: any chance you could run "grep -wr nobody /" on a device exhibiting this, and show me the result?15:54
psivaacjwatson: sure 1 sec15:54
cjwatsonI can partially revert if I have to, but I'd really rather chase this down as the change made all trusty systems more secure15:55
popeycjwatson: happy to run whatever tests on my phone15:56
cjwatsonpopey: do you see "Successful su for nobody by root" in /var/log/auth.log?15:56
dobeydidrocks: more tests added on https://code.launchpad.net/~dobey/cupstream2distro/native-versions/+merge/200736 ; i didn't see any existing stuff for "sru mode" and i'm not sure how it would apply in this case (i think it would be transparent since the series is different anyway, as you said)15:58
popeycjwatson: under what circumstances?15:59
psivaacjwatson: http://pastebin.ubuntu.com/6715504/ is the output of that.15:59
cjwatsonpopey: to start with, just as it is15:59
popeyno15:59
popeyi see no reference to "nobody" in that log16:00
cjwatsonpopey: then after running the messaging-app tests and rebooting16:00
psivaacjohnston: please note that the lines with Documents are copied old auth.logs16:00
didrocksdobey: looking good. Mind if I have a deeper look my tomorrow morning? Want to finish some stuff tonight16:00
cjwatsonyeah, I know16:00
popeyok16:00
cjwatsonpsivaa: I think it might have got stuck at /proc or /sys16:01
cjwatsonpsivaa: could you try "grep -wr nobody /usr /var"?16:01
dobeydidrocks: sure16:04
psivaacjwatson: http://pastebin.ubuntu.com/6715544/16:06
cjwatson/usr/bin/with-ofono-phonesim:su nobody > /etc/ofono/phonesim.log <<EOF 2>&1 &16:07
cjwatsonbing16:07
didrocksdobey: thanks for the patch!16:07
dobeydidrocks: sure. i just wanted proper support for native daily release versions :)16:08
cjwatsonpsivaa: Please try http://paste.ubuntu.com/6715569/ - the latter part should apply to /usr/bin/with-ofono-phonesim16:10
cjwatsonpopey: I think you can stand down now, thanks16:11
popeyok16:11
cjwatsonpsivaa: any luck?16:22
psivaacjwatson: running the test.16:23
cjwatsonpsivaa: I should have mentioned that you probably need to reboot after applying that patch16:23
psivaacjwatson: the tests do that already16:23
cjwatsonok16:23
didrockspsivaa: the change is in the test runner?16:24
cjwatsonthe change is in ofono-phonesim, see above16:24
psivaacjwatson: and it fixes. the test pass :)16:24
cjwatsonyay16:24
didrocksok, thanks16:24
cjwatsonuploaded16:24
didrocksexcellent :)16:24
cjwatsonhttps://launchpad.net/ubuntu/+source/ofono-phonesim/1.19-0ubuntu716:25
cjwatsonurgh, competing with the test rebuild16:26
cjwatsonif only we had more arm64 hardware ...16:27
cjwatsondidrocks: I think maybe I should cancel one of the test rebuilds to make room here - I assume you want to get back to green this evening?16:44
didrockscjwatson: if possible, so that we have an image kicked soon16:45
didrockscjwatson: otherwise, the cronjob at 2 am UTC will kick it16:45
ogra_3am16:45
ogra_:)16:45
* didrocks is lost in time16:48
ogra_if it is only one of time ans space thats still ok ... both is bad though16:50
ogra_s/ans/and/16:50
didrocks;)16:53
didrocksspace is ok16:53
didrockswell… I guess16:53
balloonsfginther, ping17:00
fgintherballoons, pong17:00
balloonsfginther, can you help me rebuild konsole-qml-plugin in https://launchpad.net/~ubuntu-touch-coreapps-drivers/+archive/daily?17:01
balloonswe don't have a trusty build for it17:02
fgintherballoons, actually there is one, but it has saucy in the name17:02
didrocksogra_: joining?17:03
ogra_didrocks, no :P17:03
balloonsfginther, hehe.. so the 10-30 is the name eh? anyways, we need a build against the newer libs in trusty17:03
fgintherballoons, ack, I'll try a fresh build17:04
fgintherballoons, is this the correct branch? lp:ubuntu-terminal-app/plugin17:10
balloonsfginther, yes I believe so17:10
didrocksogra_: tsssss17:12
ogra_heh17:12
balloonsdidrocks, I did notice you have dialer app assigned to me.. it's not a core app17:14
didrocksballoons: oh sorry, yeah I know, typo :)17:15
didrocksballoons: will fix in next one, thanks!17:15
balloonswhich is to say, I've not handled issues in the past, heh :-)17:15
didrocksballoons: no worry, I pinged directly Bill on that one in fact17:15
didrocksthe typo was just on the email17:15
balloons:-)17:22
=== jasoncwarner__ is now known as jasoncwarner
timpwhat's wrong here? https://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-trusty-amd64/2113/console17:30
timpERROR: No artifacts found that match the file pattern "work/output/*.deb". Configuration error?17:31
timpERROR: 'work/output/*.deb' doesn't match anything, but 'output/*.deb' does. Perhaps that's what you mean?17:31
timpit seems to fail when installing packages before running tests?17:31
balloonscprov, what happened with this? https://code.launchpad.net/~andrew-hayzen/ubuntu-ui-toolkit/fix-swipe-delete-001/+merge/19990617:49
cjohnstontimp: looks like there is a dbus issue17:52
cjohnstonballoons: isn't that the same one as earlier?17:53
balloonscjohnston, yes.. I just don't know what happened with it. I see it's still failing17:54
cjohnstonballoons: it hasn't run again since last we talked has it?17:55
balloonscjohnston, I'm not sure.. I had to hit some meetings and left it with timp17:55
cjohnstonPS Jenkins bot (ps-jenkins) wrote 4 hours ago:17:55
balloonswas something wrong on the ci end?17:55
balloonsthat's the question17:56
cjohnstonno..17:56
balloonskk, so it is test failures then..17:56
cjohnston_usr_lib_arm-linux-gnueabihf_qt5_bin_qmlscene.32011.crash <--17:56
cjohnstonballoons: my understanding is that crash is the issue17:56
balloonsI see the pending build btw fginther for konsole-qml-plugin, ty18:00
=== retoaded changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
=== alan_g is now known as alan_g|EOD
kenvandinerobru, can you review https://code.launchpad.net/~ken-vandine/ubuntu-html5-theme/0.1+13.10.20130916-0ubuntu2/+merge/20072218:18
kenvandinealesage, can you look at this failure, gcov related18:19
kenvandinehttps://jenkins.qa.ubuntu.com/job/unity-trusty-amd64-autolanding/67/console18:19
alesagekenvandine, willdo18:19
kenvandinealesage, thx18:20
robrukenvandine, done18:23
kenvandineoh... you did it last night... since mine :)18:24
kenvandinei proposed branches for all of the out of sync packages yesterday :)18:24
kenvandinemost are merged already though18:24
robrukenvandine, oh ok18:24
kenvandinealesage, i have another one that is failing because it finds lcov 1.10 and gcov.m4 doesn't list 1.10 as a valid version18:26
kenvandinealesage, should i just update the gcov.m4 file?18:26
kenvandinealesage, or is there more to it than just adding the version?18:26
alesagekenvandine, yes I think just update the version18:26
kenvandinecool, thx18:27
kenvandinerobru, humm... you did dee as well18:28
kenvandinebut dee ftbfs in ci tests18:28
kenvandinebecause of the lcov version18:28
robrukenvandine, oops, yeah, I didn't realize you'd done any. so I just did a couple that i saw18:29
alesagekenvandine, yes that's going to be a problem all over :/18:29
kenvandinehaha... we did discuss it in the meeting yesterday :)18:29
alesagekenvandine, need to upstream that gcov.m4 file somewhere18:29
kenvandinehttps://code.launchpad.net/~ken-vandine/dee/1.2.7+13.10.20130924.1-0ubuntu2/+merge/20071918:29
kenvandinerobru, can you review that one?18:29
kenvandinei merged trunk so it won't conflict with your change18:29
kenvandinebut hopefully will build in CI now18:29
robrukenvandine, done18:30
kenvandinethx18:30
* kenvandine hopes it passes18:30
kenvandinealesage, let me know what you figure out on with the unity build18:31
kenvandinethat one looks weird, unrecognized gcovr format18:31
robrukenvandine, https://code.launchpad.net/~unity-team/libqtdbusmock/trunk/+activereviews is this the same scenario as libqtdbustest? pete-woods says only the changelog changes were necessary, but didn't comment for this project (which is an identical change)18:31
kenvandineyeah18:31
kenvandinei saw that too18:31
kenvandinei'll revert the rules change there too18:31
robrukenvandine, ok, ping me and i'll approve the changelog change then.18:31
alesagekenvandine looking at, will report18:31
kenvandinerobru, pushed18:33
robrukenvandine, done18:33
kenvandineok, bamf needed the gcov.m4 change too18:36
kenvandinehttps://code.launchpad.net/~ken-vandine/bamf/0.5.1+14.04.20131125-0ubuntu2/+merge/20072318:37
kenvandinerobru, ^^18:37
robrukenvandine, done18:42
kenvandinethx18:42
timp18:52:54 < cjohnston> timp: looks like there is a dbus issue18:45
timpcjohnston: yes, but the code changes don't touch dbus. is it an issue with jenkins?18:45
timpcjohnston: why dbus? It says some deb files are missing. I don't see any failed tests18:46
cjohnstontimp: I'm wondering if there is a crash like the other one?18:47
alesagekenvandine gcovr log items may be red herring: last successful build (65) also had gcovr complaints; `mkdir` operation failure at the very end appears to be the culprit18:48
alesagefginther, does this look at all familiar?  https://jenkins.qa.ubuntu.com/job/unity-trusty-amd64-autolanding/67/console18:49
fgintheralesage, I think I know what's happening here, give me a few minutes to get it fixed19:11
balloonssergiusens, ping19:12
alesagefginther, thanks kenvandine ^^19:12
cjohnstonfginther: can you take a look at https://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-trusty-amd64/2113/console please19:13
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: fginther | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
kenvandinealesage, fginther: thx19:19
fginthercjohnston, I can fix that, thanks for the info19:19
cjohnstontimp: ^19:20
timpfginther: you'll fix the ERROR: No artifacts found that match the file pattern "work/output/*.deb". Configuration error?19:22
timpfginther: cool. do you know what caused it?19:22
fginthertimp, it's fixed (at least this case, I have some others to correct). One of the CI tools was automatically updated and it resulted in a mismatch in behavior19:24
timpok, thanks19:24
sergiusensballoons, pong19:55
balloonssergiusens, solved it myself heh. I swear everytime I ping to ask you something I end up figuring it out.. :-p20:00
sergiusensballoons, hey, that's how I operate as well :-)20:00
cyphermoxrobru: kenvandine: https://code.launchpad.net/~mathieu-tl/cupstream2distro-config/apps-test-packages/+merge/200900 ?20:01
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: fginther | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: upstream merger cutting over to saucy
kenvandinecyphermox, looking20:24
kenvandinecyphermox, approved20:24
cyphermoxthanks20:30
=== kalikiana_ is now known as kalikiana
sergiusensfginther, can we get lp:goget-ubuntu-touch under ci now?22:08
fginthersergiusens, sure22:08
sergiusensfginther, let me get greedy and ask for lp:usensord too :-)22:11
fginthersergiusens, what are these used for (so I know what cu2d stack to use)?22:11
sergiusensfginther, usensord should go in the same place platform-api is22:11
sergiusensfginther, goget-ubuntu-touch where phablet-tools lives22:12
fginthersergiusens, are these ready for daily-release?22:15
sergiusensfginther, they'd need packaging review; but they are fairly ready22:19
sergiusensfginther, as in from the team22:19
fginthersergiusens, in that case I'll prep them for upstream merger now so as not to wait on a packaging review22:20
sergiusensfginther, sounds good22:20
kgunnfginther: just curious...can we determine/backtrack like which exact device (mako) a test was run on ?22:32
kgunnjust curious we saw one mako we were suspect of prior to break...took it out, but put it back22:33
kgunnjust wondering if it might be biting us again22:33
kgunnhttps://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-mako/226/console22:33
fgintherkgunn, yes, the device name is in the console log, one of the first few lines22:33
fginthermako-04cb53b59854653422:33
kgunnyep found it...thanks fginther22:34
fgintherkgunn, if you suspect a bad device, we can remove it from the main pool and attempt some focused tests22:35
kgunnfginther: thanks...i'll just keep an eye on this mp...see if it fails again and monitor the device...if "he" remains a prob...i might ping you tomorrow22:36
fgintherkgunn, ack22:36

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