| wxl | elfy: kind of ot but do you have a link to the qa contest you did for stickers? | 00:55 |
|---|---|---|
| === chihchun_afk is now known as chihchun | ||
| elopio | veebers: so, I don't fully understand. But to fall on the safe side, I can just make branches for those project to make everybody use the base from the toolkit. | 04:10 |
| veebers | elopio: I'm just trying something now which should hopefully clarify it for myself then I'll be able to explain it better | 04:16 |
| elopio | veebers: ok, so tomorrow I'll prepare the extra branches. | 04:52 |
| elopio | good thing we made this card. | 04:52 |
| elfy | wxl: http://xubuntu.org/news/help-the-community-with-testing-and-win-xubuntu-stickers/ | 05:43 |
| wxl | elfy: thx | 05:48 |
| wxl | yay just booted my raspberry 2 with snappy | 05:48 |
| wxl | squee | 05:48 |
| elfy | wxl: welcome | 06:30 |
| === chihchun is now known as chihchun_afk | ||
| === chihchun_afk is now known as chihchun | ||
| === vrruiz_ is now known as rvr | ||
| pitti | vila: so adt-run -d --- ssh -d works for me with an LXC target, so this looks phone specific | 10:44 |
| pitti | vila: -U should never be used on a phone in general, but I suppose you are doing this on purpose? did you set the phone to r/w before? | 10:45 |
| pitti | ah, apparently you do as apt-get update worked | 10:45 |
| pitti | vila: ok, I give up on bug 1449446 for now, I need more information | 11:06 |
| ubot5 | bug 1449446 in autopkgtest (Ubuntu) "adt-virt-ssh -d breaks satisfying adt-satdep.deb dependencies" [Undecided,Incomplete] https://launchpad.net/bugs/1449446 | 11:06 |
| vila | pitti: yup, writable to test silos with citrain device-upgrade | 11:51 |
| vila | pitti: I haven't dig deeply to understand why I need -U though | 11:51 |
| vila | pitti: the log file is fine but lp fails to display it, I just downloaded it to check. Apart from a couple of ^M ... which may enough to trick lp ? | 11:56 |
| vila | pitti: and thanks for the shell advices ! I'll probably need more for some time ;) | 12:06 |
| pitti | vila: no, it's like 2 out of 3 messages are missing in the log, I'm not sure what happened there | 12:42 |
| vila | pitti: doh | 12:51 |
| vila | pitti: weirdly enough, I'm currently seeing an 'echo "Reboot #$X"' disappearing when X > 3 but still presents in the log ! | 12:51 |
| vila | pitti: with qemu in that case | 12:53 |
| vila | pitti: ha ha ! Comparing my buffer with the log, I got: | 12:54 |
| vila | shell: tee: standard output: Resource temporarily unavailable | 12:55 |
| vila | log: Reboot #3 | 12:55 |
| vila | yeah, that indeed, exactly ;) | 12:55 |
| vila | pitti: but anyway, when you say 2 out of 3, it is some big chunks (start/end) are missing or little chunks all over the place ? | 12:57 |
| pitti | vila: the latter; I really have no idea what happened there :/ | 12:57 |
| vila | pitti: ok, I'll retry with a phone later and see, any hint on what should be there and isn't ? | 12:58 |
| pitti | vila: for example, "adt-run: DBG: testbed init" or "adt-run: DBG: $ vserver: adt-virt-ssh ..." | 12:58 |
| pitti | vila: oh wait! this log doesn't actually contain the debugging for adt-run | 12:59 |
| pitti | vila: so maybe it's just because the branch uses Depends: @, and that's somehow not satisfiable after the apt-get upgrade, or something strange like that | 13:00 |
| vila | pitti: err, as in I forgot adt-run -d or it's not supposed to end up htere ? | 13:00 |
| pitti | vila: it is supposed to end up there (I ran it here, and it's all in the log | 13:01 |
| vila | pitti: nope, it doesn't happen with the same command but without -d for adt-virt-ssh | 13:01 |
| vila | hmm, unless something weird happened at X: adt-run --- adt-virt-ssh (no -d) X; adt-run --- ssh -d ; adt-run --- ssh | 13:02 |
| vila | pitti: well, according to my own report, I didn't use adt-run -d /me blushes | 13:03 |
| vila | only adt-virt-ssh -d, will redo | 13:04 |
| boiko | vanguard: hi guys, I need some help with writing an emulator to interact with on-screen notifications in ubuntu touch | 13:45 |
| boiko | elopio: is vanguard working? or should I use ubuntu-qa? | 14:12 |
| elopio | boiko: ubuntu-qa please. | 14:12 |
| boiko | ubuntu-qa: hi guys, I need some help with writing an emulator to interact with on-screen notifications in ubuntu touch | 14:12 |
| Saviq | boiko, fwiw, this should get you on the right path | 14:14 |
| Saviq | http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/head:/tests/autopilot/unity8/shell/tests/test_notifications.py#L159 | 14:14 |
| elopio | fgimenez: ^ | 14:20 |
| fgimenez | Saviq, thx, elopio does http://bazaar.launchpad.net/~canonical-platform-qa/ubuntu-sanity-tests/trunk/view/head:/ubuntu_sanity_tests/helpers/unity8/settings_wizard.py contain also a good example? | 14:22 |
| elopio | fgimenez: of the helpers style, yes. But boiko needs to restart unity with testability if his tests are running on touch. | 14:22 |
| fgimenez | elopio, ok clear now :) | 14:23 |
| elopio | then wait for the notification to appear, and then swipe it away. This part is easy. I think it would be mostly to help him getting a nice base test class for unity integration. | 14:23 |
| boiko | elopio: so, some of the notifications are dialogs with multiple actions (snap decisions?), s not sure just swiping them away would work | 14:43 |
| elopio | boiko: I see. But the principle is the same, if the user in your tests needs to dismiss the notification, write a dismiss method with all the steps necessary. | 14:46 |
| boiko | elopio: yep, well, actually right now the dismissing of the notification is not part of the test, it is just to prevent the notification from getting in the way of the subsequent tests | 14:47 |
| elopio | boiko: fgimenez: it's worth analyzing that if the test is not testing the notifications, maybe we can stop the notification service or something like that. | 14:47 |
| elopio | but we'll need other tests that check the interaction with the notifications. | 14:48 |
| boiko | elopio: yep, FYI: the test I am working on is to check that dialer-app is doing the right thing on a valid USSD session, the dialog appearing is just a side effect | 14:49 |
| elopio | right, I guess that if there's no risk of the USSD session breaking the notifications, then you can split that test. Maybe even test the notification integration with lower level API tests. | 14:52 |
| boiko | elopio: still I need the dialog dismissed somehow at the end of the test :) | 14:54 |
| boiko | elopio: I was talking to tiagosh and he gave me the idea of killing the telephony-service-indicator process at the end of the test | 14:56 |
| boiko | elopio: that might be the easiest fix for now | 14:56 |
| elopio | boiko: I let you to discuss about it with fgimenez. Whatever solution you two come out with will be good for me. | 14:57 |
| boiko | elopio: thanks | 14:57 |
| fgimenez | boiko, i guess the notification doesn't have any control to interact with, right? | 15:00 |
| boiko | fgimenez: it has two buttons, "Ok" and "Cancel" but they both just dismiss the notification itself | 15:01 |
| boiko | fgimenez: in this particular case it is useless, but we have also tests for incoming calls that show the dialog to accept/reject the call | 15:02 |
| boiko | fgimenez: in that case it would be nice to be able to actually click the notification. Right now what we do is to trigger a dbus call to telephony-service-approver accepting/declining the call | 15:03 |
| fgimenez | boiko, you can create classes that expose methods for interacting with each kind of notification, for instance http://bazaar.launchpad.net/~canonical-platform-qa/ubuntu-sanity-tests/trunk/view/head:/ubuntu_sanity_tests/helpers/unity8/settings_wizard.py#L419 | 15:05 |
| boiko | fgimenez: the problem is: the notifications themselves are in unity (which is not running in testability mode by default) and dialer-app is in a different process | 15:05 |
| brendand_ | boiko, you have to restart it in testability mode first | 15:06 |
| brendand_ | boiko, then do your test | 15:07 |
| boiko | brendand_: ok | 15:08 |
| boiko | fgimenez: brendand_: thanks for the help, I will try to cook something in the next few days, let's see how it goes | 15:09 |
| fgimenez | boiko, you can ping the vanguard for review | 15:15 |
| boiko | fgimenez: nice! thanks | 15:15 |
| brendand_ | ubuntu-qa - anyone can confirm this sanity suite regression? unity8.shell.emulators.UnityEmulatorException: No scope found with id clickscope | 15:23 |
| rhuddie | brendand_, I've seen that one before | 15:23 |
| alesage | cking ping hey that rhymes :) | 15:25 |
| alesage | cking I'm wanting to persuade you to present some of you coverity findings during a UOS session next week, any interest? | 15:25 |
| brendand_ | rhuddie, intermittently? | 15:25 |
| brendand_ | rhuddie, it seems to be plaguing the whole suite now | 15:26 |
| brendand_ | rhuddie, unless i did something wrong maybe | 15:26 |
| rhuddie | brendand_, when I saw it, it was intermittent and very hard to reproduce. | 15:26 |
| rhuddie | brendand_, so that sounds different | 15:27 |
| cking | alesage, don't you mean cppcheck findings? | 15:27 |
| alesage | cking exactly :) | 15:27 |
| alesage | cking, I'd like to do a "static analysis" topic | 15:27 |
| cking | alesage, actually, I was aiming to just use these findings to try and get leverage and a coverty scan license | 15:28 |
| alesage | cking, no better forum to publicize this work :) | 15:28 |
| alesage | cking, but you have worked with the coverity scanner, yes? or am I misremembering | 15:29 |
| cking | alesage, coverity scan is free and superior to cppcheck anyday, but it has big limitations to the number of times one can use it per week on large projects | 15:30 |
| alesage | cking, I'm very curious about the "onboarding" process for the free service | 15:30 |
| alesage | cking, I see | 15:30 |
| cking | alesage, it is limited, one has to either own the project or be a significant author to sign a project up to it | 15:31 |
| alesage | cking do you get access to their web console, etc.? | 15:31 |
| cking | alesage, yep, I get access to the webby front-end goodness | 15:31 |
| alesage | cking, anyway the session could literally be me asking you these questions :) and maybe us presenting a few interesting defects | 15:31 |
| cking | i use it for all projects I package into debian | 15:32 |
| alesage | cking, doesn't have to be longer than 15 min | 15:32 |
| alesage | cking, balloons and I trying to sort some QA-relevant sessions | 15:32 |
| elopio | projects-team: I'm breaking the rule of 2 because these cards are boooring. | 15:33 |
| cking | alesage, i'm more convinced we'll get better coverage if I blog about it, I get tens of K hits on my blog | 15:33 |
| elopio | I'm done, but waiting for three jenkins runs. | 15:33 |
| cking | alesage, and I'm bogged down with some critical work that needs attendind to at the mo | 15:33 |
| alesage | cking, whell that's fair, can't stand in the way of your work | 15:34 |
| alesage | cking, thanks for considering | 15:34 |
| alesage | cking I'll have more questions at some point, ok? | 15:34 |
| cking | alesage, ask anytime, I'm very happy to discuss it | 15:35 |
| cking | however, I really think the perfect solution is to get a coverity scan licence for devs and the QA process | 15:35 |
| balloons | cking, alesage thanks for considering | 15:36 |
| alesage | cking, we'll have to discuss that further--would you be willing to give me a tour of the free process at some point? | 15:36 |
| cking | alesage, sure, I can do that, it's very simple, here's a starter: https://scan.coverity.com/faq | 15:38 |
| cking | alesage, sign yourself up, and I'll add you to a project so you can see what it looks like | 15:39 |
| alesage | cking, thanks | 15:39 |
| elopio | vila: are you ok with this one? https://code.launchpad.net/~canonical-platform-qa/qakit/flake8-fixes/+merge/256674 | 15:44 |
| vila | elopio: I approved it long ago didn't I ? | 15:44 |
| vila | elopio: fixing the key exposure will require changing it anyway | 15:45 |
| elopio | I can't top-approve it :/ | 15:46 |
| elopio | alesage: can you? | 15:46 |
| alesage | elopio, let me check | 15:46 |
| vila | elopio: hmm, I can't either, NeedsFixing ;-) | 15:47 |
| alesage | elopio I can't either :/ | 15:52 |
| pitti | vila: oh, you figure the phone ran out of space and thus it couldn't create /tmp/ssh_askpass.XX any more? | 15:53 |
| === chihchun is now known as chihchun_afk | ||
| alesage | elopio, vila, seeing the problem one sec | 16:01 |
| elopio | oSoMoN_: alex-abreu: returning to the issue killing the web container, is there something else you need from us? | 16:05 |
| oSoMoN_ | elopio, not at this point, alex-abreu is debugging the issue | 16:05 |
| elopio | cool. The bug fix in autopilot is easy, but the release is painful so it will take some time. | 16:06 |
| elopio | thanks alesage. I suppose we don't have autolanding, right? | 16:24 |
| alesage | elopio, not sure if thomi set it up, assume no | 16:25 |
| alesage | elopio will look into | 16:25 |
| elfy | wxl: now I am awake enough to think about that - what you asked wasn;t at all offtopic for this channel :) | 16:30 |
| wxl | elfy: well, tangenital :) | 17:12 |
| === chihchun_afk is now known as chihchun | ||
| === om26er_ is now known as om26er | ||
| teward | balloons: ping if you're still around, and don't mind a PM | 18:50 |
| balloons | teward, pong | 19:07 |
| teward | balloons: mind a PM? | 19:07 |
| balloons | go for it | 19:07 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!