[07:16] <tsdgeos> pstolowski: this looks on your side https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1484299
[07:16] <tsdgeos> pstolowski: tell me if not
[07:22] <pstolowski> tsdgeos, looking
[07:24] <pstolowski> tsdgeos, yeah, it's on our side
[07:27] <tsdgeos> pstolowski: i also did a unity8 landing, so you need to rebuild our silo
[07:28] <pstolowski> tsdgeos, ok
[08:09] <tsdgeos> cimi: can you do https://code.launchpad.net/~aacid/unity8/previews_in_order/+merge/267058 and https://code.launchpad.net/~aacid/unity8/even_more_stable_page_header_test/+merge/267199 ?
[08:53] <cimi> tsdgeos, doing them between trying to recover my arale without bootstrap
[08:53] <tsdgeos> oki!
[08:54] <cimi> tsdgeos, it keeps failing to go to recovery even if i flash it
[08:54] <cimi> :/
[08:54] <tsdgeos> ouch
[09:10] <cimi> tsdgeos, I need to see what --bootstrap does
[09:11] <cimi> tried to flash recovery, flash from recovery
[09:11] <cimi> it seems to flash but then when it boots I have the meizu logo and that's it
[09:11] <cimi> adb is offline
[09:12] <tsdgeos> so
[09:12] <tsdgeos> i have this
[09:12] <tsdgeos>    people.canonical.com/~jhm/barajas/recovery-krillin.img
[09:12] <tsdgeos>    fastboot boot recovery.img
[09:12] <tsdgeos> for recovering a dead phone
[09:12] <tsdgeos> obviously the krillin bit is wrong for you
[09:12] <tsdgeos> try to see if there's an arale image around
[09:12] <cimi> I do the same
[09:12] <tsdgeos> or ask in #ubuntu-touch
[09:12] <tsdgeos> oh
[09:13] <cimi> i actually even tried to flash recovery
[09:13] <tsdgeos> i don't know more
[09:13] <cimi> but it fails somewhere
[09:13] <tsdgeos> ask in #ubuntu-touch i guess
[09:13] <cimi> I have to wipe, shame, I had my nice chroot inside arale :(
[09:18] <pstolowski> tsdgeos, cimi may I ask you to review https://code.launchpad.net/~stolowski/unity-scopes-api/new-widgets-doc-wily/+merge/267921 ?
[09:20] <tsdgeos> cimi: i've approved, but please review too, aprove too and then top approve
[10:26] <pstolowski> tsdgeos, fyi, silo 4 has been rebuilt
[10:27] <tsdgeos> coolio
[10:37] <tsdgeos> any idea of what /usr/lib/arm-linux-gnueabihf/libubuntu_application_api_test.so.3.0.0 is?
[11:00] <greyback_> tsdgeos: it's a library for AP testing I think, lets it mock sensor output
[11:00] <tsdgeos> ok
[11:00] <tsdgeos> it's causing unity8 shutdown to get stuck sometimes
[11:00] <tsdgeos> not sure if get stuck or take a long time
[11:00] <tsdgeos> the process eventually dies
[11:01] <tsdgeos> but not sure if it's autopilot killing it or what
[11:01] <tsdgeos> running autopilot tests is still a nightmare
[13:49]  * tsdgeos creates a script to run them one by one
[13:49] <tsdgeos> so muhc better
[13:59] <greyback_> tsdgeos: care to share :)
[13:59] <tsdgeos> it's 3 lines
[14:00] <tsdgeos> greyback_: http://paste.ubuntu.com/12071224/
[14:01] <greyback_> tsdgeos: autopilot3 run -v <testsuite> - prints a bit more info, just fyi
[14:01] <tsdgeos> yeah, too much
[14:01] <greyback_> yep, that I agree with
[14:03] <tsdgeos> and this way i can time it out at 120 secs
[14:03] <tsdgeos> which is also a nice side effect
[14:21] <tsdgeos> cimi: removed the ; in https://code.launchpad.net/~aacid/unity8/even_more_stable_page_header_test/+merge/267199
[14:54] <tsdgeos> cimi: here's another branch for you https://code.launchpad.net/~aacid/unity8/more_autotests_dash/+merge/265401 !
[14:55] <cimi> tsdgeos, happy time :D
[15:01] <cimi> tsdgeos, in the tests, we have 15000 ms as time
[15:02] <tsdgeos> 15s?
[15:02] <cimi> yes
[15:02] <cimi> tsdgeos, are we supposed to wait 15s every time or there is a smarter way?
[15:02] <tsdgeos> where is that 15000ms?
[15:22] <cimi> tsdgeos, init
[15:22] <tsdgeos> cimi: which init?
[15:22] <cimi> tsdgeos, testDashShell
[15:23] <tsdgeos> it's not waiting 15000
[15:23] <tsdgeos> it's waiting up to 15000
[15:25] <cimi> tsdgeos, yeah
[15:26] <cimi> tsdgeos, but why?
[15:26] <tsdgeos> because the dash is slow to set up itself
[15:26] <cimi> tsdgeos, it could be also 30s then
[15:26] <tsdgeos> it could be 15000000
[15:26] <tsdgeos> yes
[15:26] <tsdgeos> it's 15000 because it's waht we use in other tests that do the same
[15:26] <cimi> yeah, I know that
[15:26] <tsdgeos> and it was originally 15000 because no reason i guess
[15:26] <tsdgeos> more than 5000 until it worked :D
[15:27] <cimi> :/ ok
[15:27] <cimi> wish we could be smarter, if CI is slower one day, 15 might not be enoug
[15:27] <tsdgeos> then we make it bigger
[15:27] <tsdgeos> i for one hope we get faster CI
[15:27] <tsdgeos> not slower :D
[15:44] <tsdgeos> http://paste.ubuntu.com/12071889/
[15:44] <tsdgeos> woot!
[15:45] <tsdgeos> "Cannot find new threads: generic error"
[15:49] <cimi> tsdgeos, can we jump to uitk 1.3 for that file?
[15:49] <tsdgeos> cimi: for the test?
[15:49] <cimi> tsdgeos, yeah
[15:49] <tsdgeos> sure
[15:50] <cimi> tsdgeos, it's just the header, but the test that greps the import we have in uitk13 will require that too
[15:50] <cimi> uitk13 branch
[15:51] <tsdgeos> cimi: done