[03:30] <pitti> Good morning
[07:13] <jibel> good morning
[08:38] <DanChapman> Good Morning all :-)
[09:06] <slickymaster> good morning all
[09:06] <slickymaster> elfy, you there?
[09:24] <Noskcaj> evening slickymaster
[09:24] <DanChapman> hey Noskcaj , slickymaster o/
[09:25] <Noskcaj> hey DanChapman
[09:26] <slickymaster> DanChapan, good morning
[09:26] <slickymaster> Noskcaj, can you spare 5 minutes?
[09:26] <Noskcaj> slickymaster, sure, what is it?
[09:27] <slickymaster> Nosckaj, it's about this test: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1183493
[09:28] <slickymaster> It's tagged as merged but I'm still working on it
[09:29] <Noskcaj> If it's in a usable condition, leave it as merged but push a new version every time you think it's necessary
[09:31] <Noskcaj> If you're looking for something to do, the libreoffice tests are out of order and confusing
[09:31] <slickymaster> Noskcaj, ok, I'll continue working on it and I'll propose the merge when it's finished. Is that ok with you?
[09:31] <Noskcaj> yep
[09:32] <slickymaster> Noskcaj, one last thing, about the translations for the TestDrive, the intention is to get both testedrive and testdricegtk translated, right?
[09:33] <Noskcaj> yeah. Ignore the testdrive-gtk launchpad page though, it's a stub. Just use /testdrive and translate everything there
[09:33] <Noskcaj> (on launchpad)
[09:35] <slickymaster> Noskcaj, wiil do. About libreoffice, I don't think I can spare the time, for now, to work on it
[12:39] <elfy> slickymaster: not really here - as noskag said just work on it as you are then push when there's stuff to merge - you can forget about lkibreoffice testcases anyway - it's not xubuntu default app ;)
[12:54] <knome> elfy, well said sir ;)
[12:56] <elfy> :)
[13:50] <pitti> xnox: btw, did you happen to find out anything about partman-auto with an md device?
[13:50] <xnox> pitti: nope, not yet.
[14:01] <xnox> pitti: wanna hangout about ubiquity & autopilot
[14:01] <pitti> xnox: ah right, that's now; gonna be there
[14:03] <jibel> https://code.launchpad.net/~jibel/+junk/ubiquity-autopilot-runner
[14:03] <jibel> DanChapman, balloons_ xnox pitti ^
[14:04] <jibel> ./run-ubiquity-test ./saucy-desktop-amd64.iso
[14:04] <jibel> DanChapman, balloons_ xnox pitti ^
[14:04] <balloons_> ahh..much better :-p
[14:06] <DanChapman> balloons_, FF is freezing up on me at the mo just waiting for it to catch up
[14:06] <balloons_> DanChapman, ahh.. it's giving alot of feedback through your mic
[14:09]  * DanChapman gets headphones
[14:37] <balloons> DanChapman, I see ff is still causing heartache today
[14:38] <DanChapman> Yeah i'm still waiting on your review ;0)
[14:38] <balloons> DanChapman, ohh, well let's solve that eh?
[14:38] <DanChapman> that should stop the fails for good
[14:38] <xnox> Why is dl-ubuntu-test-iso not in the archive?
[14:40] <balloons> xnox aren't you planning to use zsync?
[14:41] <balloons> ahh.. this uses zsync plus some more, interesting
[14:41] <xnox> balloons: dl-ubuntu-test-iso, i write one config file and simple "dl-ubuntu-test-iso" fetches the complete set of images I am interested in
[14:42] <pitti> xnox: hm, now with ubiquity -d -b it crashes right after selecting the language, http://paste.ubuntu.com/5887752/
[14:42] <xnox> balloons: and i'm surprised this is not in the archive.
[14:42] <balloons> xnox, right right.. but it's not been around since 10.04 to my knowledge
[14:42] <balloons> stemming from here: https://launchpad.net/ubuntu-qa-tools?
[14:42] <xnox> pitti: ouch.
[14:42] <pitti> xnox: ah, sorry, my fault
[14:44] <balloons> xnox, jibel might know more about dl-ubuntu-test-iso
[14:44] <xnox> pitti: looks like parted_devices is not an executable?! =)
[14:44] <pitti> xnox: for some reason it was damaged
[14:44] <xnox>  /o\
[14:44] <pitti> xnox: http://paste.ubuntu.com/5887760/
[14:45] <pitti> xnox: ^ debug log after partman-auto (should have) done its job
[14:46] <pitti> xnox: http://paste.ubuntu.com/5887761/ ← /var/log/partman
[14:46] <jibel> xnox, it has been removed a while ago but cannot remember why
[14:47] <pitti> xnox: can you somehow run just partman-auto in a terminal to see what it's doing, to avoid the ubiquity overhead in each turnaround?
[14:50] <pitti> xnox: c'est l'heure du glace, à bientôt !
[14:51] <stgraber> pitti: de la
[14:51] <stgraber> ;)
[14:51] <pitti> stgraber: I thought that de la == du ?
[14:52] <pitti> anyway, bbl
[14:52] <balloons> pitti, pardonnez mon français-- ice cream hour? ahh stgraber merci
[14:52] <xnox> pitti: well, on only needs to run partman under d-i & debconf. Or run ubuntu-server image over that device only, somehow.
[14:53] <stgraber> pitti: "du chocolat" (masculine), "de la glace" (feminine)
[14:53] <xnox> pitti: btw. parted state is not cleared after ubiquity exists so, one needs to clear /var/lib/parted/
[14:53] <stgraber> pitti: but it's french so there are exceptions ;)
[14:54] <jibel> pitti, du = de le
[14:56] <DanChapman> xnox, for the dual-boot test are you only wanting to run it against windows. Or would you prefer the test to be non-distro specific . Just figuring out what to look for UI wise
[14:56] <balloons> DanChapman, ff test is  merged
[14:56] <balloons> I'll push to prod
[14:57] <xnox> DanChapman: there are multiple configurations. See: http://goo.gl/Kokw5
[14:57] <xnox> DanChapman: https://docs.google.com/a/canonical.com/document/d/1bZ4yQIVgGaUGSYu3qiUHnQt3ieBZoqunP_DcleHCr3I/preview#bookmark=id.35db66d9d3b3
[14:57] <DanChapman> balloons, awesome. That should be it now! if that fails i will eat my socks!
[14:58] <xnox> DanChapman: depending on the # of installed systems, # of available drives, whether they are ubuntu/windows/mac/other linux different options and text is displayed.
[14:59] <xnox> pitti: i'm not sure DEP-8 makes sense, since we are testing ubiquity as is on the cd, instead of the one uploaded. I guess we need to trigger ubiquity upgrade from -proposed in the CD as well.
[14:59] <DanChapman> xnox, ok great will go have a read. thanks
[15:17] <xnox> pitti:  # Skip software RAID (mdadm) devices (/dev/md/X and /dev/mdX)                $(echo "$device" | grep -Eq "/dev/md/?[0-9]*$") && continue
[15:17] <xnox> pitti:  /lib/partman/lib/auto-shared.sh
[15:30] <pitti> stgraber: ah, I thought du would work for both genders; thanks!
[15:30] <balloons> DanChapman, do you have further tests targetted to add for ubuntu-autopilot-tests?
[15:35] <pitti> xnox: aah, thanks
[15:36] <xnox> pitti: i think there is also a filter there to skip loop mounted devices.....
[15:37] <pitti> xnox: well, it's not a loop device, so that part should be fine (they don't even appear in parted_devices)
[15:37] <xnox> pitti: i think the logical reason behind it, is that not non mdadm /boot is required by the installer at the moment, despite the fact that grub2 learned how to read those.
[15:37] <DanChapman> balloons, that i have been working on? or to add to the bug list?
[15:38] <xnox> pitti: and one can't automatically guess which partition to use as /boot for an md device..... but we even chose not to install grub.... so it shouldn't be relevant. Hmm.
[15:38] <pitti> xnox: ok, so I'll try again with hacking that
[15:39] <pitti> xnox: hah nice, that works! at least I get the autopartitioning screen now
[15:39] <xnox> =)
[15:40] <pitti> xnox: I'll add that to the script with a comment that we want that in the general case, but not in the test which covers the case when we indeed don't have a bootable device
[15:40] <xnox> well, i'd expect it to fail soonish, it might detect it's raid array and start trying to install mdadm and what not =/
[15:41] <xnox> fingers crossed, it's enough to finish a normal install =)
[15:41] <pitti> xnox: if we could spare 6 GB of RAM we could just use scsi_debug..
[15:41] <xnox> pitti: oh, i can spare 6GB of RAM locally =)
[15:41]  * xnox has 32GB
[15:42]  * pitti has 4
[15:42] <pitti> xnox: sudo modprobe scsi_debug dev_size_mb=6000, and go wild :)
[15:43] <pitti> that should be mostly indistinguishable from a real scsi disk, unless you look rather hard (device path and such)
[15:43] <xnox> nice. =) didn't know i could do that.
[15:46] <pitti> xnox: aaaaand success!
[15:48] <DanChapman> balloons, i wonder if creating tests for say libreoffice where ProcMan is needed is it worth it, considering the problems with FF and it being a rather simple test
[15:49] <pitti> DanChapman, balloons, jibel, xnox: please have an updated script which now DTRT: http://people.canonical.com/~pitti/scripts/test-ubiquity.sh.txt
[15:49] <balloons> DanChapman, I would consider libreoffice a lower priority as there is a nice set of autopkg tests for it
[15:49] <pitti> I just tested an ubiquity installation end-to-end with autopartitioning
[15:49] <pitti> fdisk -l /dev/md42 looks reasonable, too
[15:52] <balloons> DanChapman, so I was just looking at the list, what else can we add / do?
[15:52] <balloons> DanChapman, sorry I should be more clear. for ubuntu-autopilot-tests, I'm looking at the trello board
[15:53] <balloons> most of our original targets are done and deemed not doable
[15:53] <balloons> *or
[15:53] <DanChapman> balloons, i had a hack at rhythmbox little while back but it was getting really hacky. I was gonna ask pitti if it's possible to mount a music cd with umockdev and how?
[15:53] <DanChapman> balloons, I think gnome-calculator should go on there
[15:53] <xnox> pitti:  \o/
[15:53] <pitti> DanChapman: not with umockdev, but with scsi_debug you can do it
[15:53]  * DanChapman just heads to trello
[15:54] <pitti> DanChapman: I do that in the udisks2 and in the gvfs tsts
[15:54] <balloons> DanChapman, ahh.. good point. I'm really sad about shotwell, you should open the card and check the linked bug and see if anything has changed
[15:54] <pitti> DanChapman: main issue is that you need root for it
[15:55] <DanChapman> balloons, will take a look at shotwell. I never did look to see why it couldn't be done.
[15:55] <balloons> DanChapman, the issue is there was no way for us to programmtically get at the camera object
[15:56] <balloons> but you know, they didn't change the app to give us keyboard shortcuts, but maybe pitti's changes will show us the object now
[15:56] <balloons> the deal was the camera object didn't appear in autopilot for us to interact with
[15:56] <pitti> if it's not exposed, please file an autopilot-gtk but
[15:56] <balloons> carla did work already on mocking a camera and everything for it, so there was quite a bit of work done
[15:56] <pitti> bug; I'll look into it
[15:57] <DanChapman> pitti, will have a peak at gvfs.
[15:58] <pitti> DanChapman: is root a problem for your tests?
[15:58] <pitti> DanChapman: https://git.gnome.org/browse/gvfs/tree/test/gvfs-test#n983
[16:02] <pitti> DanChapman: actually, http://cgit.freedesktop.org/udisks/tree/src/tests/integration-test#n389 is structurally easier, if you want to look at that
[16:02] <pitti> DanChapman: it's the same approach, but with less wrapping around it
[16:07] <DanChapman> balloons, if i remember correctly the camera comes up in the tree view in the left pane. We can't see the items inside objects like treeview and combobox. But can click on the treeview object to get focus so we can keyboard nav. I'll stick it on my todo and have a play before we rule itout
[16:08] <balloons> DanChapman, ok, and as pitti said, if there's something he might be able to help with, let's note it :-)
[16:10] <DanChapman> pitti, im not sure if root is a problem or not. balloons do you know??
[16:11] <balloons> mm.. it has potential to be yes
[16:11] <pitti> DanChapman: autopkgtests have no problem with root; a "make check" upstream integration has, and if you want to run tests during package build
[16:11] <balloons> the tests themselves run as a normal user
[16:11] <pitti> we cannot currently mock block devices purely as user
[16:11] <pitti> that's a rather complex thing to do
[16:12] <balloons> but if you do your setup via root before running the test, should be fine
[16:13] <pitti> DanChapman: I suggest your root setup leaves some marker in the file system which your tests can pick up (like the name of the fake cd drive)
[16:13] <pitti> DanChapman: and if your tests don't find the marker, you just unittest.skipIf() it
[16:14] <pitti> so that the other tests still work in a normal "make check" style
[16:14] <pitti> (if you integrate them in the upstream build/test system)
[16:16] <DanChapman> ahh ok i get what your saying. I'll have a go, will come back to you if i get stuck on that one :-P
[16:20] <DanChapman> balloons, U1 would be a good test to have. Do you know if the U1 guys have a dummy account they use for testing?
[16:23] <pitti> DanChapman: ubuntuone-client just got an autopkgtest, that might have some kind of local dummy server to test against?
[16:23] <balloons> DanChapman, I *think* elopio could shed some light on that. In general we left software center and u1 alone as they do there own automated testing
[16:24] <balloons> and of course have special needs, like test accounts, etc :-)
[16:25] <balloons> we also left unity alone as they too have there own testsuite in autopilot :-)
[16:25] <DanChapman> balloons ahh ok. I saw it in the bug list. Should we remove it then?
[16:25] <balloons> DanChapman, you could comment and mark won't fix
[16:25] <balloons> should that change, well :-)
[16:26] <elopio> DanChapman: it depends on the level of testing you have in mind. For user testing, we run most of the suites against a local or staging server, where we can create a new user for every test.
[16:33] <elopio> pitti: there's no dummy server. For the unit tests, they fake the parts needed for each test.
[16:33] <pitti> elopio: ah, ok
[16:34] <elopio> there are also some dummy clients, that test some features from the servers. So the real client needs mostly a manual run to check that the integration looks good.
[16:37] <DanChapman> elopio, is it any use to have an autopilot test for U1-control-panel? just looking it already has a wealthy test suite anyway
[16:39] <elopio> DanChapman: it would be nice, of course. Currently it's not a priority, since the development has freezed. And if it's resumed, it will probably change the UI to use the SDK.
[16:50] <DanChapman> balloons, ive moved nautilus and terminal back to todo on trello as they both use ProcMan and can be introspected now
[16:50] <balloons> DanChapman, :-)
[18:57] <asac> doanac: one question ... the smem job that i see that runs together with autopilots
[18:57] <asac> doanac: is that the job getting the data for memory budget?
[19:13] <doanac> asac: it produces this report: http://reports.qa.ubuntu.com/memory/idle/arch/armhf/
[20:13] <Letozaf_> balloons, Hi
[20:14]  * SergioMeneses says hi everybody
[20:15] <Letozaf_> I am working on the settings tab autopilot test for sudoku app, as I will not finish it tonight, it's a bit too long, I pushed what I did til now, probably tomorrow I will finish it, hope: https://code.launchpad.net/~carla-sella/sudoku-app/settingsTab
[20:15] <Letozaf_> SergioMeneses, Hello
[20:15] <Letozaf_> balloons, just if you want to take a look ,but don't have to :)
[20:19] <SergioMeneses> Letozaf_, hi how you been?
[20:19] <Letozaf_> SergioMeneses, fine and you ?
[20:20] <SergioMeneses> Letozaf_, fine too working :D
[20:21] <Letozaf_> SergioMeneses, oh so you're problably quite busy ;)
[20:22] <Letozaf_> SergioMeneses, what do you do ?
[20:24] <SergioMeneses> Letozaf_, i'm working as system administrator
[20:25] <SergioMeneses> not too busy right now... everything is working well
[20:26] <Letozaf_> SergioMeneses, cool nice job, like me :D
[20:27] <Letozaf_> SergioMeneses, well hope you enjoy it
[20:27] <SergioMeneses> Letozaf_, I do :)
[20:27] <Letozaf_> SergioMeneses, good, good :D
[20:29] <SergioMeneses> Letozaf_, I have a little issue with Apache but I'm reading about it
[20:31] <Letozaf_> Letozaf_, oh! unfortunatly I do not have Apache where I work, I wish I did :p
[20:31] <Letozaf_> SergioMeneses, you are lucky
[20:31] <Letozaf_> SergioMeneses, it's nice working with open source instead or proprietary software :p
[20:32] <SergioMeneses> Letozaf_, ofcourse :) that is the reason to be working here
[20:32] <SergioMeneses> I can learn a lot and get better skills about services
[20:32] <Letozaf_> SergioMeneses, yeah true :D
[20:33] <Letozaf_> SergioMeneses, I also do it for fun :p
[20:33] <SergioMeneses> sure
[20:33] <SergioMeneses> I'm going to get some coffee
[20:34] <asac> doanac: ok ... so thats not what gives use the other memory dash preview you showed me?
[20:34] <doanac> asac: no
[20:41] <phillw> has any one seen the scarlet pimpernel about (aka balloons)? :)
[20:43] <Letozaf_> SergioMeneses, I am going to bed now, bye and good luck for your job :)
[20:44] <SergioMeneses> Letozaf_, ok see you!
[20:44] <knome> phillw, said something about 4 hours ago
[20:44] <phillw> he's probably tied up with auto-testing :)
[20:47] <knome> or mirroring his handsome face
[20:47]  * knome hides
[20:47] <knome> bbl
[21:30] <balloons> knome, phillw I've been feeling quite ill
[21:32] <phillw> balloons: sorry to hear :( I've got a "winged" guy also on lubuntu.  It's just a request to see if https://wiki.ubuntu.com/phillw/Activities can go live before I edit to death!
[21:32] <phillw> *edit it to death!*
[21:33] <balloons> phillw, I'd say yes.. kick off a round of review on the mailing list and let people know and give input :-)
[21:33] <phillw> else, I can throw it to the tender mercies of the mailing list :)
[21:33] <phillw> I'll do both - and take a backup of the exiting one :)
[21:33] <balloons> the only other thing I want to see there is stuff on running the development release
[21:34] <balloons> it's much nicer than what we have :-)
[21:34] <balloons> good work!
[21:35] <phillw> balloons: not too sure what else to add in for that... most of those pages being referred to are pulled from testing pages. Let me have a think, if I can't come up with some thing 'short and sweet' I'll ask for input from the ML
[21:35] <balloons> well, I'd like to have something on, hey install the testin version of ubuntu
[21:36] <balloons> in a vm or on a box, and use it to participate in cadence testing, etc
[21:36] <phillw> Sure, I can pull a heading up for that, and include on it some links
[21:36] <balloons> right.. and if your really up for it, run it fulltime
[21:36] <balloons> that's never really been documented..
[21:39] <phillw> as we have the page https://wiki.ubuntu.com/QATeam/Overview/TheStages I guess making a fully fledged one for https://wiki.ubuntu.com/QATeam/Overview/TheStages#Virtual_Machines with the header being 'how to test the dev release' would fit in?
[21:41] <phillw> I'm not sure enough about cadence tetsting's ins and outs to further edit the page https://wiki.ubuntu.com/QATeam/Cadence/Saucy maybe when you're feeling better you can have a look at that and then it can be fully added as a header section (unless you're happy with it as it stands, in which case I'll do that in this editing session I'm about to do)
[21:42] <phillw> I've got a couple of hours to do a last head on edit!
[21:43] <phillw> I'd better mention testdrive, or my name will be mud!
[21:45] <phillw> Yeah, it's okay.. I can see how to format it up! It'll get done in next couple of hours..
[21:53] <slickymaster> good night everyone
[21:53] <Noskcaj> hello slickymaster, Thanks for the translations
[21:54] <slickymaster> Noskcaj, you're welcome
[21:55] <slickymaster> Noskcaj, I've also finished Xfce4 Settings Manager and I'm going to push it now to merge proposal
[21:56] <slickymaster> Noslcaj, I've not covered all the items in the settings manager because several items were already covered in other tests
[21:56] <balloons> phillw, got it.. go for broke mate
[21:57] <slickymaster> Noskcaj, do you think I should mention that in the proposal comment?
[22:00] <Noskcaj> slickymaster, it might be a good idea. I'll merge it when i get home from school unless elfy or balloons beat me to it
[22:01] <slickymaster> Noskcaj, will do it, then
[22:02] <stgraber> balloons, knome: do you have a list of changes and links to mockups for the bits you want me to change on the QATracker?
[22:02] <stgraber> I have a vague hope of doing some of that on my flight to London on Saturday
[22:03] <knome> stgraber, http://temp.knome.fi/qa/iso-tracker-mockup-12.png
[22:03] <knome> stgraber, i can write an email running through the changes exactly if that helps
[22:04] <stgraber> knome: yeah, that'd be helpful and attach the mockup so I have it offline. I have a bunch of notes in my irclogs and elsewhere but that won't be too helpful if I do it over the ocean ;)
[22:04] <knome> i'll do that :)
[22:05] <balloons> knome, awesome, I'll let you be the one source of communication on this
[22:05] <knome> balloons, i'll cc you too.
[22:05] <balloons> I think we've hashed out the ideas well enough
[22:06] <knome> anybody else who should be informed?
[22:06] <balloons> everyone else when we have the results ;-) otheriwse.. none come to mind
[22:06] <knome> okay
[22:31] <knome> stgraber, balloons: you both have mail
[22:38] <stgraber> knome: what extra tags do you want?
[22:38] <stgraber> knome: you currently have: <a> <em> <strong> <cite> <blockquote> <code> <ul> <ol> <li> <dl> <dt> <dd> <pre> <img>

[22:39] <knome> i mean, something
[22:39] <knome> let me check and propose
[22:39] <stgraber> knome: added h1 to h5 for now
[22:39] <phillw> balloons: now... the $64,000 question... do you want it in alpha / beat / RC (as it is now) with cadence week numbers in brackets, or do you want it cadence week number order with alpha / beta / RC in brackets?
[22:39] <knome> stgraber, i'm thinking we might not want to enable h1...
[22:39] <phillw> balloons: https://wiki.ubuntu.com/Testing/Testing_The_Devlopment_Release#preview
[22:40] <stgraber> knome: hmm, yeah, might make it a bit confusing with the site's own headers
[22:40] <phillw> Grr.  https://wiki.ubuntu.com/Testing/Testing_The_Devlopment_Release
[22:40] <knome> stgraber, unless we style them appropriately (eg. the <h1> in testcase shouldn't be as big as the <h1> in the page header or so)
[22:41] <stgraber> knome: h3 to h5 are unused on the standard pages, not sure how they look like though
[22:41] <stgraber> well, h6 is free too
[22:41] <stgraber> I'll enable those for now, if you need h2, let me know
[22:41] <stgraber> knome: and done (those are simple Drupal settings)
[22:41] <knome> stgraber, i'd say h3/h4 would be enough
[22:42] <knome> stgraber, if you can enable those in the sandbox, i can come up with some css for them soonish
[22:42] <knome> stgraber, considering the use we have for the elements, just h3 would be fine tbe
[22:43] <stgraber> knome: ok, qa.dev.stgraber.org updated too
[22:43] <knome> stgraber, great, thanks
[22:43] <knome> stgraber, i just want something to separate two or more blocks of text from each other
[22:43] <knome> stgraber, so that's why i've been asking for those :)
[22:45] <stgraber> knome: for the "You are currently on: Ubuntu ISO Testing" it's mostly to distinguish the dozen instances on the same server (as I can't easily change the <title> without hacking Drupal). But I should be able to move that bit to something title-looking next to the Ubuntu logo (I "think" there's a block area I can use there)
[22:45] <knome> stgraber, that's what i'm thinking
[22:46] <knome> stgraber, the note is a bit confusing if you don't know about all those different instances or do not care
[22:46] <knome> stgraber, it might lead people thinking "(is this) where i *should* be?" :)
[22:47] <knome> (and of course, it uses valuable, top-of-the-page space without being overly useful)
[22:52] <knome> stgraber, h3 { display: inline; font-size: 125%; border-bottom: 1px solid #ccc; }
[22:52] <knome> stgraber, that should be increasingly good-looking once the testcases have a white background
[22:53] <stgraber> ok
[22:54] <knome> if it ends up looking bad, i'll let you know of any replacement css
[22:54] <knome> but i doubt that
[23:01] <xnox> pitti: jibel: balloons: i am blown away =) cloud-init cloud image in a qemu, to run auto-package-test which launches a VM to drive an installer, and watchint it via doubly connected vnc forward......
[23:01] <xnox> inception - the programmer's special edition =)
[23:14] <stgraber> knome: YGM
[23:16] <knome> stgraber, you should probably discuss the critical/non-critical bugs with balloons
[23:17] <stgraber> knome: he's Cced ;)
[23:17] <knome> right
[23:17] <knome> it's 2am ;)
[23:18] <knome> >
[23:18] <knome> > – Reports for the testcase (also see new preferred table layout)
[23:18] <knome> You mean the target for "To see a full list of bugs reported for this
[23:18] <knome> testcase..."?
[23:18] <knome> i'm not following that
[23:20] <knome> what i meant that the table columns are rearranged
[23:20] <knome> +is
[23:21] <stgraber> knome: ah, I understood the table columns to be "(also see new preferred table layout)" and interpreted the "Reports for the testcase" as being "we need some page to list all the bugs for a testcase"
[23:21] <knome> well, that'd be useful :)
[23:22] <knome> what's an edit icon that doesn't suck?
[23:23] <knome> i thought "details" more than "edit" when looking for that icon
[23:28] <stgraber> knome: well, I guess a usual pen like icon or something along those lines
[23:29] <stgraber> knome: that icon is shown when you have right to alter a result, either because it's your own or because you're an admin
[23:30] <stgraber> the copy/paste briefcase looks a bit odd for that (if I didn't know what that link is supposed to do, I'd never guess ;))
[23:30] <knome> that's because you're not supposed to guess, you're supposed to know >:)
[23:32] <knome> stgraber, http://temp.knome.fi/qa/elementary-actions-16-edit.png ?
[23:32] <stgraber> yep, that'd do the trick
[23:32] <knome> will you pick that up or want me to email that?
[23:33] <stgraber> e-mail please, in 24x24 if you have
[23:33] <knome> stgraber, re: critical/normal bugs... i suppose the logic was that if a test is failing, all bugs should be critical
[23:34] <knome> i know that's not waterproof, but it would mean one less input box for the use
[23:34] <knome> *user
[23:34] <knome> all the other icons are 16px. is there a reason why you want to force 24 for this, or would you like them all in that size (and why?)
[23:35] <stgraber> ah, did you get everything down to 16px? the current ones are all 24 i think
[23:35] <knome> yep, all is down to 16
[23:35] <stgraber> ok, then 16px is fine
[23:36] <knome> i don't think we're making it any harder to use, and it's a bit more compact this way
[23:36] <stgraber> so typically from a release team point of view, I only care about the red bugs, everything else I just ignore
[23:36] <stgraber> having to then go and check individual reports and bugs makes me waste time
[23:36] <knome> i see
[23:37] <stgraber> so I prefer having two input fields and having the user decide which are blockers and which aren't than have the release team go through them all and generate yet another report :)
[23:37] <knome> mhm
[23:37] <knome> i'm fine with that
[23:37] <knome> i'm more interested in the improved looks/readability than the actual features
[23:39] <stgraber> haha, I'm quite the opposite, I couldn't care less about design/readability so long as I get all I need in less than 30s on the site ;)
[23:39] <stgraber> (well, I tend to use the API to shorten that time even more)
[23:39] <knome> heh, yeah