| === elfy is now known as Guest54311 | ||
| === elfy is now known as Guest77157 | ||
| === Guest52375 is now known as forestpiskie | ||
| === forestpiskie is now known as elfy | ||
| === cking_ is now known as cking | ||
| === qwebirc681520 is now known as slickymasterWork | ||
| paulliu | charles_: Can I get the rotation_lock by dbus methods from /com/canonical/indicator/rotation_lock ? | 13:40 |
|---|---|---|
| paulliu | charles_: the rotation_lock seems to be a gsettings. Can you also export it to the dbus interface so we can access it? | 14:46 |
| paulliu | charles_: For testing. | 14:46 |
| === charles_ is now known as charles | ||
| charles | paulliu, I can do that, but I think you may be able to pull directly from the gsettings if you're wanting to test it in qml | 14:49 |
| paulliu | charles: no. I'm writing the autopilot test. | 14:49 |
| paulliu | charles: we want to use the autopilot to turn on/off the indicators rotation lock. And see if it did changes the real gsettings. | 14:50 |
| charles | paulliu, ack | 14:50 |
| charles | paulliu, I don't mind adding that to the rotation indiator, but just to make sure it's the right thing, why are you wanting to query this via dbus? | 14:53 |
| charles | eg if you want to verify the gsettings independently you can do it from the command line with "gsettings get com.ubuntu.touch.system rotation-lock" | 14:53 |
| elopio | Good morning team. | 14:54 |
| paulliu | charles: ok. I'll use the command line. | 14:59 |
| charles | paulliu, ack | 15:01 |
| paulliu | charles: when I turn on/off the Rotation Lock, it didn't change the value of com.ubuntu.touch.system rotation-lock value. | 15:29 |
| * charles looks | 15:30 | |
| charles | paulliu, wfm | 15:31 |
| charles | paulliu, I pulled down the rotation lock indicator's menu and toggled the "Rotation Lock" menuitem | 15:32 |
| charles | paulliu, repeatedly doing that + querying "gsettings get com.ubuntu.touch.system rotation-lock" gives me true, false, true, false as expected | 15:32 |
| paulliu | charles: ok. Maybe something weird on my phone. | 15:33 |
| charles | paulliu, you're running "gsettings get" in the phablet-shell session? :) | 15:33 |
| paulliu | charles: yes | 15:34 |
| paulliu | elopio: can you test if the fixtures works? | 15:42 |
| paulliu | elopio: my phone dies. | 15:42 |
| elopio | paulliu: sure. Same branch? | 15:43 |
| paulliu | elopio: yes | 15:43 |
| paulliu | elopio: just pull | 15:43 |
| elopio | paulliu: I get self.assertEqual(fixture._is_rotation_lock_enabled(), True) | 15:46 |
| elopio | testtools.matchers._impl.MismatchError: False != True | 15:46 |
| paulliu | elopio: yeah. I got the same. So if you turn on/off the rotation lock, is "gsettings get com.ubuntu.touch.system rotation-lock" shows the same value? | 15:47 |
| paulliu | elopio: before my phone dies, I cannot get the correct value by gsettings. But charles can. | 15:48 |
| elopio | paulliu: no, it doesn't matter the state of the checkbox, it always returns false | 15:49 |
| paulliu | charles: ^ | 15:49 |
| elopio | also, the indicator icon is not being shown when I click the checkbox. Something stoped working. | 15:49 |
| charles | ...? | 15:50 |
| * charles re-tests | 15:50 | |
| elopio | gsettings set com.ubuntu.touch.system rotation-lock true does work. | 15:50 |
| charles | okay so score 1 for testing | 15:52 |
| elopio | \o/ | 15:53 |
| charles | this is working for me on 14.10 (krillin r191), but when I switch to 15.04 (mako r64) I get a consistent 'false' | 15:53 |
| paulliu | charles: it's weird.. Just gsettings.. | 15:53 |
| charles | my first guess is that an indicator-display branch landed in 14.10 but not 15.04; if so that's an oversight | 15:54 |
| charles | previously uss had a different key and then went with 'rotation-lock' in the gsettings, there was a branch to switch to that in indicator-display. maybe that didn't land in trunk for the 15.04 images | 15:54 |
| charles | checking | 15:54 |
| elopio | I can use the checkbox to disable the lock. Not to enable it. | 15:55 |
| charles | no... no code changes between the two branches | 15:56 |
| paulliu | elopio: so for the test we might want to do that twice.. | 15:56 |
| paulliu | elopio: if we change to test in the reverse order, I wonder the code will pass. | 15:57 |
| elopio | paulliu: we can't automate at this level if there is an error. | 15:57 |
| charles | no, this is broken, we shouldn't write the test to work around that | 15:57 |
| elopio | what we do is report a bug, and put a skip with a link to that bug. | 15:57 |
| charles | +1 | 15:57 |
| paulliu | ok. | 15:58 |
| elopio | and make a comment on the bug report to reenable the test once it's fixed. | 15:58 |
| elopio | paulliu: your fixture looks awesome. | 15:58 |
| elopio | a couple of details. | 15:58 |
| elopio | paulliu: for the moment, we should make the helpers compatible also with py2. | 15:58 |
| paulliu | elopio: ok | 15:58 |
| elopio | so when calling super, you need to use the old style. like super(IndicatorDisplayRotationLock, self).__init__() | 15:59 |
| charles | paulliu, elopio, I have a meeting right now but I'll triage this right afterwards | 15:59 |
| elopio | charles: thanks. | 15:59 |
| charles | paulliu, elopio, please paste the bug url here | 15:59 |
| elopio | paulliu: second, I think that we should have only one fixture_setup class. I would move the unity8/shell/fixture_setup.py to unity8/fixture_setup.py and put the one you added new there. | 16:00 |
| elopio | what do you think about that? | 16:00 |
| paulliu | elopio: ok. | 16:01 |
| paulliu | elopio: btw, are you testing that on rtm? | 16:04 |
| elopio | paulliu: no, I'm on vivid, krillin. | 16:05 |
| === roadmr is now known as roadmr_afk | ||
| === roadmr_afk is now known as roadmr | ||
| alesage | elopio, I'm reviewing the make qmltest, might need you to lead me into this a little | 16:58 |
| elopio | alesage: sure | 16:59 |
| elopio | the easiest way to test it that I have found is bzr bd. Then install the built packages and open qtcreator to make projects with the templates. | 16:59 |
| alesage | elopio, ok sure | 16:59 |
| alesage | elopio, so this is a dumb question but how do I see the existing template? it's just the default dummy project, yes? | 17:00 |
| elopio | alesage: I don't get your question. How to create a project from the template? | 17:00 |
| alesage | elopio, more like "what is a template" | 17:01 |
| elopio | alesage: when you open qtcreator, you will see a page called ubuntu-sdk | 17:01 |
| elopio | from that page click the link create a new project | 17:02 |
| elopio | there you will see the templates, in the Ubuntu section. | 17:02 |
| alesage | elopio, k I see | 17:02 |
| elopio | alesage: on the branch, you will see many wizard.xml files | 17:02 |
| elopio | that's what makes the templates appear here, and what tells qtcreator which files to copy into the new project. | 17:03 |
| alesage | elopio, so you modified "App with Simple UI"? | 17:04 |
| elopio | alesage: I modified many. | 17:05 |
| elopio | I changed the default main file from main.qml to Main.qml in all templates. | 17:05 |
| alesage | elopio, ok slowly dawning on self over here | 17:06 |
| elfy | balloons: \o/ thanks for talking to IS | 17:14 |
| balloons | elfy, no problem.. all appears well now | 17:16 |
| elfy | yep | 17:18 |
| elopio | rhuddie: ping, meeting. | 17:31 |
| elopio | paulliu: have you filed the bug, or do you want me to do it? | 17:47 |
| paulliu | elopio: I'll do it. | 18:02 |
| elopio | paulliu: thanks. | 18:03 |
| elopio | balloons: if you want to review the template branch, feel free. The more the merrier. | 18:03 |
| elopio | I'm going for lunch. | 18:04 |
| paulliu | elopio: https://bugs.launchpad.net/ubuntu/+source/indicator-display/+bug/1410915 | 18:11 |
| ubot5 | Launchpad bug 1410915 in indicator-display (Ubuntu) "com.ubuntu.touch.system rotation-lock can't be changed by the checkbox in indicators" [Undecided,New] | 18:11 |
| paulliu | charles: https://bugs.launchpad.net/ubuntu/+source/indicator-display/+bug/1410915 | 18:12 |
| charles | paulliu, ty | 18:12 |
| dkessel | good evening. looks like half the ubuntu world is subscribed to bug 1268257 :D I have never seen a bug with a heat of > 10000 | 18:26 |
| ubot5 | bug 1268257 in nvidia-graphics-drivers-331-updates (Ubuntu) "nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"" [High,Triaged] https://launchpad.net/bugs/1268257 | 18:26 |
| balloons | dkessel, ;-) | 18:49 |
| balloons | evening to you as well | 18:49 |
| dkessel | evening balloons :) Let me motivate myself by telling you that I will be looking at the qa tracker code again in a few minutes | 18:53 |
| dkessel | lightdm in vivid is still failing for me BTW :p | 18:54 |
| balloons | dkessel, oO. I think we nailed the last snafu of the rebuild yesterday by getting bug numbers showing again | 18:54 |
| balloons | and yea, vivid is having some fun. There's a keyboard input install bug as well | 18:54 |
| === chihchun_afk is now known as chihchun | ||
| Letozaf_ | balloons, hi, did you see https://wiki.ubuntu.com/UtopicUnicorn/ReleaseSchedule is still on Ubuntu 14.10 schedule ? | 20:25 |
| balloons | Letozaf_, ? what do you mean? | 20:25 |
| Letozaf_ | balloons, shouldn't there be the release schedule of 15.04 ? | 20:26 |
| balloons | Letozaf_, yes. https://wiki.ubuntu.com/VividVervet/ReleaseSchedule | 20:26 |
| Letozaf_ | balloons, this one ends October 2014 | 20:26 |
| balloons | let me fix the wiki too | 20:26 |
| balloons | Letozaf_, wiki and calendar all fixed, thanks for noticing :-) | 20:32 |
| Letozaf_ | balloons, yw :) | 20:32 |
| dkessel | balloons, knome: here is some progress on the qa tracker changes after two months of no progress: https://imgur.com/9561kt0 | 20:56 |
| dkessel | (a bit hacky) | 20:56 |
| * balloons looks | 20:59 | |
| elfy | so did elfy | 20:59 |
| balloons | nice | 20:59 |
| elfy | I like | 20:59 |
| balloons | ^^ me too | 20:59 |
| elfy | ha - that'll be snap then :) | 21:00 |
| elfy | anything that means people don't have to mouseover 70 little icons to find a bug works for me | 21:00 |
| elfy | though it is likely to make the test page looooong I guess | 21:00 |
| elfy | it needs more than critical bugs imo | 21:03 |
| elfy | and is status/importance.assignee of any interest at this point | 21:03 |
| elfy | maybe a table with bug number and title and perhaps a repeated column so | 21:04 |
| elfy | bug - title | bug - title | bug - title | 21:04 |
| elfy | just a thought :) | 21:04 |
| * dkessel keeps elfy's suggestions for the next tracker hack evening | 21:53 | |
| knome | elfy, that'd make it harder to read, i prefer one bug per line | 21:58 |
| knome | could have checkboxes to filter out different statues though | 21:58 |
| elfy | knome: yes - but would you like the testcase page to be really looooooooooooooong | 21:58 |
| knome | sure, but with filters, it's doable | 21:58 |
| knome | and we can work on the listing to make each row less tall | 21:59 |
| elfy | you'd have to page down past 30 or more bugs - then lines and lines of text - and then finally somewhere to report | 21:59 |
| elfy | filter out kylin | 22:00 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!