#ubuntu-quality 2013-08-01 <smartboyhw> Noskcaj, ping <smartboyhw> Noskcaj10, ping <balloons> Noskcaj10, tests are fully synced to rev189 <smartboyhw> Hey hey balloons <balloons> goodnight smartboyhw :-p <smartboyhw> LOL <balloons> ROFL! <balloons> I win! <smartboyhw> balloons, meh:( <balloons> how are you? <balloons> I'll stay for a min :-) <smartboyhw> balloons, great:) <balloons> how was your trip? find the UK interesting? <smartboyhw> balloons, which autopilot tests would you recommend me to touch on? (Since many are completed it seems) and UK is great! <pitti> Good morning <Noskcaj10> smartboyhw, pong, i was at school <smartboyhw> Noskcaj10, I can't seem to understand the structure of the .pot file, I just can't seem to get how the .ui.h thing works <Noskcaj> smartboyhw, Right now, i'm working with kirkland to fix the translations. I was just letting you know you "missed a spot" <smartboyhw> Noskcaj, OK. Please work with him to fix the translations then:) <smartboyhw> I might be busy these days. I've got a piano exam coming up on the 13th (ABRSM G8) <Noskcaj> ok <smartboyhw> Then if it is approved I will work on doc of another project <smartboyhw> More useful than Testdrive (LOL)( <slickymaster> good morning all <slickymaster> knome, ping. Are you there? <rbasak> jibel, pitti: adt-virt-lxc ready for review again in https://code.launchpad.net/~racb/ubuntu/saucy/autopkgtest/lxc/+merge/172856. It assumes cloud-init in the container, and defaults to "ubuntu" as the normal user inside the container. I'm not sure how that sits with merging into Debian. <rbasak> But this should be good for testing, and I'd appreciate feedback on that. The catch is that Debian has no LXC template for a container that uses cloud-init, so I'm not sure how useful this will be to Debian right now anyway. <rbasak> (though of course Debian users could use Ubuntu containers) <pitti> rbasak: ah, one needs cloud-init for a container? I thought the normal approach would be to debootstrap (I think that's what the templates do) <pitti> rbasak: but thanks for this! we can add some debian/rules magic to only install the backend on ubuntu builds <rbasak> pitti: Ubuntu has "ubuntu" and "ubuntu-cloud" templates. "ubuntu" is debootstrap, "ubuntu-cloud" takes a cloud image with cloud-init in it. There's currently no general mechanism for knowing when a container is ready after it has been started, and adt-virt-lxc needs that. cloud-init provides boot-finished, so I'm using hta.t <rbasak> hta.t? Left and right hands are out of sync! <pitti> rbasak: I broke my tongue trying to pronounce it! <rbasak> It's only off-by-one :-P <rbasak> I suppose I could "adduser autopkgtest" in the container actually. Then it'd be consistent. <rbasak> But I still need the boot-finished signal in order to use debootstrapped containers without cloud-init. stgraber and hallyn were talking about some kind of standard mechanism for that. <rbasak> But I think it's a bit far away at the moment, and using boot-finished works for now. <knome> slickymaster, pong <slickymaster> knome, just a quick question. Remeber that yesterday we spoke about the typo in Xubuntu Docs? <knome> yes <slickymaster> knome, well I already branch it and my question is in which file do I correct the typo? in the xml? <knome> yes, the xml <knome> anything that is in build/ will be ignored <slickymaster> knome, the one under xubuntu-docs/desktop-guide/C/ right? <knome> slickymaster, that's right <slickymaster> knome, :) thanks. I push it by lunchÂ´ <slickymaster> I'll <knome> ok, thanks <slickymaster> knome, you don't have to thank me <pitti> rbasak: do you know if I can specify a particular boot device in cloud-init? <pitti> rbasak: for supporting nested VMs for jodh I want to pass the original pristine VM as a virtio drive to the "outer" VM, so that within the VM you can start a nested one (with a locally created overlay) <pitti> rbasak: passing that as -drive and building the VM on top of /dev/vdc seems more efficient than wasting memory for copying the VM image into the VM <pitti> rbasak: but sometimes the VM doesn't start up; that could be because it tries to boot from the wrong device, or that cloud-init works on the wrong device <rbasak> pitti: good question <rbasak> pitti: I'm not entirely sure. Checking with smoser might be an idea. I don't think cloud-init would do anything wrong here, and you should be able to force boot from /dev/vda from the qemu command line I think. But /dev/vdc's filesystem will have the same UUID as /dev/vda's filessytem. So could the initramfs be mounting the wrong root fs? <pitti> rbasak: hm, would it? I'm booting an image with an overlay <pitti> rbasak: oh, how can I force booting from /dev/vda? I was looking for that but didn't find it <rbasak> Looking at a cloud image, /etc/fstab defines / as LABEL=cloudimg-rootfs <pitti> rbasak: "-boot order=c" doesn't work <pitti> rbasak: ah, that could be it then <rbasak> So I think the initramfs will look for that, and find two filesystems with that label. <rbasak> And one is read-only. <pitti> indeed, it boots fine in maybe 50% of the cases <rbasak> Perhaps your "outer" VM needs to modify that to /dev/vda and rerun update-initramfs? But then you'll have two images, and hackery. <pitti> rbasak: argh, they indeed both have identical UUIDs and labels <pitti> rbasak: that would be it, thanks <rbasak> It's a valid requirement, though. We should provide users with a way to do that. <pitti> rbasak: I'll think about it a bit, how to obfuscate the pristine r/o /dev/vdc enough <pitti> rbasak: the hint about label/uuid was spot-on, cheers <rbasak> pitti: I was basing my understanding of boot order definiton upon what I can do from virt-manager, and I know that translates to the command line somehow. Looking at the manpage I assume that -boot order=c should work - now that you agree it's probably the label/uuid, is that consistent with your observations? <pitti> rbasak: in the worst case we have to scp the VM instead of passing it as -drive, it would just waste some 250 MB of RAM <rbasak> pitti: how about attaching the disk after the outer guest has booted? <pitti> rbasak: it's a bit hard to see what the outer VM is doing, but it's very well possible that it was booting alright from /dev/vda <pitti> rbasak: it's plausible that the initramfs got confused and mounted the wrong rootfs, or that cloud-image worked on the wrong one, or possibly both <pitti> rbasak: attach after boot> that sounds like a nice trick, how does one do that to a running VM? * rbasak looks <pitti> rbasak: I guess over its monitor? <rbasak> Yeah <rbasak> I'm not sure if you can hotplug a fixed disk like that though. <pitti> I should probably replace -monitor stdio with a named pipe or a bash fd <rbasak> But it looks like you can do it for virtual cdrom hardware and USB <rbasak> http://en.wikibooks.org/wiki/QEMU/Monitor <pitti> http://www.linux-kvm.org/page/Hotadd_pci_devices <pitti> rbasak: seems SCSI and virtio are fine, just not IDE (but who cares) <rbasak> Great! <pitti> rbasak: thanks! <rbasak> It still seems a bit hacky though. I'm interested to hear what smoser thinks. I'll send him the log of this as he's not on here. <rbasak> No problem. I hope it works! <slickymaster> knome, As it turns out, the typo isn't present in the offline-packages.xml file. It's in the *.po files that the typo is present, which are the files that contain the translations <knome> slickymaster, okay. in that case, i should probably update the translations <slickymaster> knome, I can just go ahead and correct the typos in all of those files <knome> slickymaster, no need to - it's an automatic process <slickymaster> knome, okie dokie, I'll leave it in your hands * knome tries to get to look at it before he leaves <pitti> rbasak: works nicely! now off to scripting that <rbasak> \o/ <pitti> jodh, jibel, rbasak: bug 1158391 updated with a new patch; now with 50% more hacks and stability! <ubot5> bug 1158391 in Auto Package Testing "ability to have a DEP-8 test run a test in a separate full system environment" [High,In progress] https://launchpad.net/bugs/1158391 <jibel> pitti, since you had 50% of boot failure, that makes 75% successful boots ;) <pitti> jodh, jibel: as discussed this doesn't yet contain a wrapper script to simplify the qemu-img / qemu run, as jodh potentially wanted to change the image before booting, or put other stuff in between; let's see how much of that we can generalize, and then provide a convenience script as a second step <pitti> jibel: darn, you got me there! rational arithmetic is hard! <jodh> pitti: thanks. Yes, I'm finishing up reworking my scripts to configure the vm on first boot atm... <pitti> jodh: ah, nice; did you run into the boot hangs with the previous patch? <jodh> pitti: alas, never got that far due to issues attempting to do crazy stuff in nbd-mounted chrooted vm images ;) <pitti> jodh: heh, no worries <pitti> jodh: if you are happy (for the first version) with the commands I gave in https://bugs.launchpad.net/auto-package-testing/+bug/1158391/comments/3, I think I can land this now <ubot5> Launchpad bug 1158391 in Auto Package Testing "ability to have a DEP-8 test run a test in a separate full system environment" [High,In progress] <pitti> jodh: you'll need to loop over ssh, it'll fail while the sub-vm is still booting up <jodh> pitti: yup - they work for me :) <pitti> jodh: cool <jodh> pitti: yes, I'm building up a library of routines to do "ssh polling" and other such grossities <pitti> jodh: bin/testbed/wait_bootfinished <jodh> pitti: ah! :) <rbasak> pitti: you could use a udev rule instead of that polling loop for the pristine_vm hotplug event, but it's probably not worth the effort. <pitti> jodh: that's for prepare-testbed, though, but it might have some overla0p <pitti> rbasak: well, then I'd still need to wait for teh rule to get executed <jodh> pitti: is there a command I can run to install the dep-8 Depends packages in the pristine VM? <rbasak> Good point. <pitti> rbasak: I actually want to block run-adt-test until it appears (it's not noticeable anyway), so that we avoid chowning and running the test while it's not there yet <pitti> jodh: adt-run? <pitti> jodh: I guess at some point we'll need the whole run-adt-test machinery in the VM, so that you can use it to attack the nested VM :) <rbasak> pitti: the patch looks good to me then * pitti is reminded about the "Ship in a bottle" Star Trek NextGen episode <jodh> pitti: ok, so that then would require that I have the dep-8 tests execute conditionally (based on my ADT_ENVIRON_TYPE=nested variable as mentioned the other day). <jodh> pitti: again, works for me :) <rbasak> I'm not sure the run-adt-test machinery is the appropriate thing to use inside the VM. But I guess that depends on the amount of reuse. If it's just to start sub-VMs and run stuff in them, then I think we should move that functionality to a more generic tool and put that in cloud-utils in the end. <pitti> jodh: ah right, it's not quite run-adt-test, as we don't want to run the controller script in the child VM again <pitti> jodh: but anyway, adt-run will install test depends; it might not be appropriate for the reason above, so perhaps calling pbuilder-satisfydepends directly is better for that case <rbasak> Or just apt-get install? Why do we need the more complex depends syntax here? <jodh> pitti: but I've still got to install pbuilder in the pristine VM right? :) <pitti> jodh: no, these VMs have autopkgtest installed already <pitti> and consequently, pbuilder <pitti> jodh: we build them that way, after all :) * jodh really should read the adt scripts at some point ;) <rbasak> pitti: I don't think we should rely on that. We shouldn't depend on adt-virt-null any more than we have to. <pitti> jodh: it's the list in bin/prepare-testbed, the cloud-config bit <pitti> jodh: search for "packages:" <rbasak> jodh: by pristine VM, do you mean the inner nested one? I think pitti is talking about the outer one. <pitti> rbasak: yes, but we still need adt-run, so our pristine VMs always have to have autopkgtest installed <pitti> rbasak: they are really identical <pitti> except of course we boot the outer one with an (initially empty) writable overlay <rbasak> Oh I see. The image has these things preinstalled? <pitti> rbasak: yes, by way of "packages:" in cloud-config <rbasak> Then the inner one might use a different cloud-config <pitti> well, at that point we don't generate VMs any more; everything is already instaled <rbasak> I'm confused. Can we define some terms? <pitti> we don't actually want cloud-config to go and install required packages at each run; this only happens at "prepare-testbed" (which we run once a day), not for every test <pitti> rbasak: I guess cloud-config will actually consider the config again in the nested VMs, but as the packages are all installed already it has nothing to do <rbasak> I see. So you create a new VM daily, use cloud-config to install things, then shut it down again? <rbasak> Then you use a clone of that for every test? <rbasak> Then you use a clone of that for every package? <pitti> rbasak: yes; we use the generated VM as a read-only backing of a qemu-img generated throwaway overlay <rbasak> So that outer VM running the dep8 test will see autopkgtest and auto-package-testing installed. <rbasak> And the inner VM started by the outer VM will also have these things preinstalled in its image. <pitti> correct <rbasak> OK <pitti> it still uses cloud-init, but it should be mostly a no-op at this point <pitti> at least it's reasonably fast <rbasak> Now I think that although these things are true, our tests shouldn't rely on this. <pitti> and I have actually used them while I was offline in a train <pitti> (well, with apt-cacher-ng for the actual tests) <rbasak> Since I'd like to see adt-virt-null replaced with adt-virt-kvm eventually, and don't want us to lock in to the current adt-virt-null situation. <pitti> rbasak: well, that's fine; for now we don't promise that much about the child VMs, except that "they boot and you can log in and sudo" <rbasak> The reason I don't like it is that by using adt-virt-null we're influencing the test environment in a way that the dep8 spec allows us not to do. <pitti> but it's the case that they are identical to the real autopkgtest VMs <rbasak> Right. <pitti> rbasak: right, in particular we cannot currently run "breaks-testbed" tests <rbasak> Yep <rbasak> So if we want things installed in a dep8 test, we should use a Depends, or for the inner VM manage that part ourselves and make sure it is done. Even if we need autopkgtest and it's there already, since that might go away. <pitti> rbasak: so for now, I think we should let jodh play around with that stuff to get a better feel for what's still missing and how we want to wire this together <pitti> rbasak: yep * jodh plays <rbasak> OK :) * pitti scratches off another item from is "stuff to get done OMGbeforeholidays" <rbasak> pitti: thanks for your work! <pitti> rbasak: my pleasure; nice idea with the hotplugging! <rbasak> I still don't like it. I've asked smoser for his opinion for when he wakes up. <pitti> jibel: so, mind if I land that and break the world? I'm here until tomorrow evening to deal with regressions/fires, at worst I'll back it out <rbasak> I mean it works. It just seems like a workaround for something that ideally shouldn't be necessary. <pitti> rbasak: I can't say I'm that trilled by it, but it's at least efficient and seems to be reliable <rbasak> It didn't occur to me that we have to worry about regressions. <pitti> rbasak: yesterday I was considering just scping the image, but you know how long such hacks tend to last <rbasak> Perhaps this functionality should be limited to a dep8 Feature? <pitti> rbasak: I mean in the case that VMs suddenly hang or stop booting and we block autopkgtests with that <jibel> pitti, go ahead and break the world, you're on vacations tomorrow, that'll let me a week to fix it :) <pitti> jodh: not tomorrow yet <pitti> err, jibel ^ <rbasak> Although atm, the tests still influence each other. With the current setup, it's more of a Feature for the entire test suite of a package, not one indiviual test. <pitti> jodh: assigned bug 1158391 back to you for further input what you would like to see <ubot5> bug 1158391 in Auto Package Testing "ability to have a DEP-8 test run a test in a separate full system environment" [High,Confirmed] https://launchpad.net/bugs/1158391 <jodh> pitti: ok, thanks. <jodh> hmm, why is my ADTRESULTSDIR unset ? <pitti> jibel: world duly broken, I'll watch out for autopkgtest failures (well, I do that anyway..) <jibel> thank you <smoser> pitti, rbasak i was reading http://irclogs.ubuntu.com/2013/08/01/%23ubuntu-quality.html#t09:47 <smoser> i dont have an easy way to convince an initramfs to boot off of one out 2 identical drives. <smoser> attach after boot should be fine. <smoser> the other way would be to boot with '-kernel' and '-initramfs' and '-append' with 'root=/dev/vda' <smoser> er.. whatever it was supposed to do (or even root=/dev/by-path/virtio/0/0 or whatever that would be) <smoser> we do boot by label, which is less than ideal, but booting by uuid woudln't even help you here. <smoser> the attach after boot is the cleanest path i think. <smoser> oh, the other thing.. pitti mentioned '250M' <smoser> thats a bad size i think. <smoser> as it implies that you've not uncompressed the qcow image <smoser> which means that all reads tothat disk go through cpu decompression <smoser> rbasak, how could you possibly "flag" that other disk ? <smoser> this really is not cloud specific in any way <smoser> other than being about 6 million times more likely to occur in a cloud <smoser> https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/665235 <ubot5> Launchpad bug 665235 in Ubuntu on EC2 "grub-legacy-ec2: attaching a volume to maverick instance may boot off it" [Wishlist,Triaged] <rbasak> smoser: yeah it's probably an initramfs thing, not a cloud-init thing <rbasak> smoser: maybe a way to tell the initramfs/mountall to ignore certain paths? <rbasak> I'm not sure how we'd get that message through though. <smoser> well, not really. <rbasak> It's sort of circular <smoser> yeah. <smoser> the hardest thing of this is that it is event driven <smoser> the finding of root= <smoser> udev sees it, adds a path, and 'wait-for-root' gets an event and mounts it because that added disk matched criteria <smoser> so you can't say "if i have 2 disks that are the same, then ..." <smoser> because, well, then you'd have to wait around some arbitrary time for the possibility of another disk appearing that matched that criteria <rbasak> I'd like to say "/dev/vdc" (or /dev/disk/by-path/...) does not match your criteria. <rbasak> Kernel cmdline seems appropriate, but if we can do root=/dev/vda and that works, perhaps that's my answer. <smoser> you can, but thats yucky <smoser> becauase then you have to just "know" the right kernel paramters <smoser> or inspect them. <rbasak> Good point <smoser> or i have to publish them (which is only marginally better, but then implies that people *should* do this) <rbasak> Anyway, I wondered if there was an easy solution, and/or if we care. Sounds like it's more complicated than it's worth. <smoser> consuming cloud images should not require knowing intimate details about the inconsistency of the linux kernel command line parameter system. <smoser> one option might be to use grub's env area <smoser> or MBR area <smoser> where we would allow reading of the 'root=' param from a well defined location inside the MBR. <rbasak> MBR involves modifying the disk image though, at which point we might as well change the label. <smoser> grub woudl have to do it. <smoser> not so much though <smoser> and modifying the label doen'st really help so much as i might move to uuid :) <rbasak> Perhaps the BIOS should have a config area for this stuff. <rbasak> Doesn't UEFI do something like that? :) <smoser> and modifying the label would break boot of that image! <smoser> your mention of uefi is very relevant. <rbasak> OOI, is there a UEFI-supporting qemu model? <smoser> in that MBR is not sufficent as i would ideally hope to sometime in the near future have cloud images that are uefi/mbr dual boot <smoser> yes, there is. <smoser> but thats not rreally any better. <smoser> its just changing the place that you look to use your intrinsic and brittle knowledge. <smoser> you see that bug above ? <smoser> https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/665235 <ubot5> Launchpad bug 665235 in Ubuntu on EC2 "grub-legacy-ec2: attaching a volume to maverick instance may boot off it" [Wishlist,Triaged] <smoser> that was the first time i went through this thought process :) <smoser> and punted. <smoser> root=/dev/*da1 <smoser> thats what we want :) <rbasak> What if virtual machines always used /dev/vda as the root fs, and it was up to <rbasak> right <smoser> root=/dev/*da1,LABEL=X <smoser> or uuid <rbasak> it was up to the host to make sure that the first disk is first <smoser> oh, shoot. did we lose /dev/disk/by-path ? <smoser> i seem to recall that , and i dont have it here. <smoser> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1193705 <ubot5> Launchpad bug 1193705 in systemd (Ubuntu) "[udev] /dev/disk/by-path missing" [Low,Incomplete] <smoser> so that wont be helpful <rbasak> btw, cloud-localds needs genisoimage which doesn't recommend or suggest. <smoser> well it doesn't require it. <rbasak> also qemu-utils for qemu-img <rbasak> in the default use case it needs it <smoser> it does depend on it in saucy i think <smoser> unless i didn't upload <rbasak> The problem remains in saucy <rbasak> I just started a fresh instance based on a recent daily and upgraded everything <smoser> http://paste.ubuntu.com/5936522/ <smoser> so its in trunk <rbasak> OK so it'll get there in the end. No worries :) <smoser> ah. but that iddn't make it to saucy. <smoser> rbasak, so... <smoser> this and your other tool <smoser> that you mentioend <smoser> the dependency creap of cloud-utils scares me <rbasak> Yeah I need to finish it all <rbasak> And adt-virt-kvm <rbasak> Maybe split the package up? <smoser> so my long term plan is to move cloud-localds and some of the other things into <smoser> cloud-image-utils <smoser> or the like <smoser> yeah. <smoser> because you dont likely need genisoimage in your cloud image <smoser> so you're welcome to do that for me :) <smoser> i'd even depend on 'mtools' in cloud-image-utils <rbasak> For nested kvm I do :) <smoser> well, that is a very specific use case of a cloud instance. <smoser> not necessarily a incorrect one. just probably not the most common <smoser> the kernel is the other area whwere we end up with feature creep <smoser> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1206961 <ubot5> Launchpad bug 1206961 in linux (Ubuntu) "Include rbd and kvm modules in the virtual package" [Undecided,Confirmed] <smoser> that was the motivation for my discussion on dropping 'linux-virtual' and having 'linux-server' and 'linux-generic' where linux-server would include this sort of stuff, but would not include bluetooth and audio drivers. <smoser> anyway. <rbasak> Yeah makes sense <rbasak> Thanks for the discussion <balloons> smartboyhw, sorry I dozed off before we finished conversing last night it seems :-p check out: http://www.theorangenotebook.com/2013/07/automating-core-apps-how-we-doing.html <smartboyhw> balloons, yeah <dkessel> warm evening <balloons> dkessel, evening to you * dkessel has 'run-adt-test' failing silently :/ <dkessel> pitti, are you there? can you tell me why run-adt-test is (silently) failing here?: http://paste.ubuntu.com/5936933/ <pitti> hey dkessel <pitti> dkessel: sorry, didn't get to your mail yet <dkessel> pitti: oh nvm - i guess i need to download the vm image again after the reboot.... * dkessel remembers he had this before... last year <pitti> dkessel: you mean that immediately exits? <pitti> dkessel: I was just about to give your branch a try, but I don't have much time today any mor3e <dkessel> pitti: yup, that exits quite immediately <pitti> dkessel: I don't have much experience with running adt-test as user <pitti> i. e. "anything could happen" <pitti> dkessel: nevermind, I mis-looked; it's run-adt-test <dkessel> pitti: well if you could find some minutes the other day, that would be great... <pitti> dkessel: does /tmp/adt/disks/pristine-saucy-amd64.img actually exist? <pitti> dkessel: btw, I set BASEDIR=/home/martin-scratch/images/adt in ~/.adtrc, so that I don't keep losing my VMs <dkessel> ahhh .adtrc... - yeah that was my problem... it was missing after reboot. thanks <pitti> I also have APTPROXY=http://(864)930-0890:3142 in there, to use apt-cacher-ng <pitti> together with -s, it's a real joy to see download and install taking seconds only :) <pitti> dkessel: I'm running the tests with run-adt-test now; the actual maven tests are running now <dkessel> pitti, good hints with the environment variables :) - well let's see if it fails on your system too... <pitti> dkessel: yes, I get the same error <pitti> dkessel: when I run "sudo adt-run --built-tree=. --no-built-binaries --debug --- adt-virt-null" in the unpacked tree (in the VM) I get further <pitti> ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5:compile (default-compile) on project cli: Fatal error compiling: tools.jar not found: /usr/lib/jvm/java-7-openjdk-amd64/jre/../lib/tools.jar <pitti> dkessel: but this downloads from http://repo.jenkins-ci.org, so this would fail in the data center anyway <pitti> dkessel: shouldn't we have all these modules packaged already? <pitti> dkessel: I have absolutely no idea about the original error yet, I'll try to have a look tomorrow * pitti waves good night, need to leave <dkessel> pitti: night <m-b-o> balloons ! <balloons> hey m-b-o :-) <balloons> ok, so is autopilot confirmed installed now? <m-b-o> installing atm <m-b-o> it's about https://bugs.launchpad.net/ubuntu-weather-app/+bug/1207315 <ubot5> Launchpad bug 1207315 in Ubuntu Weather App "Autopilot test failures when run on device" [Undecided,New] <balloons> ahh yes.. I get to look through popey's bugs in a few <m-b-o> I'm on the device via ssh. So I can start a testrun from there? <m-b-o> autopilot is now installed <balloons> m-b-o, yes, there's a nice wiki page talking about this. let me pull it up <m-b-o> got it running :) <balloons> m-b-o, I think this is the page I was looking for: https://wiki.ubuntu.com/QATeam/AutomatedTesting/UbuntuTouch <m-b-o> UInput: UInputError('"/dev/uinput" cannot be opened for writing',) <balloons> did you use phablet-test-run? <m-b-o> ballons: thanks! <m-b-o> autopilot run ubuntu_weather_app <knome> balloons, HELLO. <knome> balloons, we need your help :) <balloons> m-b-o, this page too: https://wiki.ubuntu.com/Touch/Testing/Autopilot. But you've got it going so :-) <knome> balloons, can you re-enable the xubuntu product being visible in packages. ? <balloons> knome, ey-ey capt'n <knome> ta <knome> balloons, for me, it says status: active though, so please tell me if i should be able to do that myself <balloons> Xubuntu Desktop has you as owner and still active <balloons> knome, what are you having trouble with/ <knome> balloons, it doesn't appear in the tracker... <balloons> knome, you should add a build for it.. and a milestone too <balloons> knome, so you can see all the milestones now for saucy.. I have a milestone for each app <knome> aha... <balloons> you can do the same, or lump all your apps under one milestone <balloons> you see last cycle we had milestones for each testing event <balloons> that's the traditional way of doing it <knome> how do i control milestones? <balloons> knome, do you have access? it's a tab <knome> summary products testcases testsuites series builds <balloons> nice.. so you can't set product families or milestones <knome> >__< <balloons> ok, well, I can. so how would you like it setup? <balloons> yes sad panda <knome> is there any possibility i can get super cow powers? :P <knome> look at the xubuntu desktop product - we all have it organized under that <balloons> have you been working with stgraber on the ui stuff? tell him you'd like super cow powers, haha.. he controls the acl's, but again you are already set as owner for xubuntu stuff in packages <knome> as long as it shows up in the tracker for testing anyway you see it fit, we're happy <knome> yes, but looks like i can't do much! <balloons> product families are silly.. and milestones can be static <balloons> builds are the most important <balloons> so you want a milestone for xubuntu? called what? <knome> what are the milestones usually called? <balloons> from there you can edit the builds for apps you want to appear, etc <knome> if it's the name that's showing up in the tracker frontpage "Xubuntu Desktop" would be good <knome> this is just over-confusing because you have ten things and the name is the same for al! <knome> *all <balloons> well step back for a moment from the craziness that is the package tracker. the iso tracker has milestones you know. saucy daily, saucy alpha 1, saucy beta, saucy final <balloons> historically the package tracker followed this line of thinking and name milestones for each testing event. So if we had a testing week, that was a milestone. If we had a specific call for testing, that was a milestone <knome> generally, do you do multiple milestones for packages? <balloons> now, we've eschewed that and have milestones for the entire cycle; a bit like the dailies <knome> right <balloons> perhaps we should push our thoughts a bit more on this <knome> then the milestone should be called Saucy <balloons> make a proper daily milestone, add product families for apps, add slot things accordingly <knome> yes... <knome> oh please yes <balloons> lol.. iterations my friend.. <balloons> that seems to make a lot of sense. I think it's definitely worthy of a mockup <balloons> we can use the test site to do a quick trial run of how it could look <knome> sure <knome> let me turn up my desktop machine, this chair isn't comfortable <knome> turn on too <balloons> http://packages.qa.dev.stgraber.org/ <balloons> knome, forgive me, but your getting some ubuntu packages assigned to xubuntu for test purposes :-p\ <knome> fffst <knome> ;) <balloons> you = xubuntu <knome> basically, we have testsuites like "Xubuntu Office" <knome> and "Xfce" <knome> which contain several testcases, like Abiword, Gnumeric, ... <balloons> I'm a visual person, so let's start here and iterate ;-) <knome> then we have the Xubuntu Desktop product <knome> let me get my head around it <balloons> ok, it's coming together here: http://packages.qa.dev.stgraber.org/qatracker/milestones/254/builds <balloons> ok, so the basic layout is setup now <knome> except the products shouldn't be named by apps <knome> that doesn't make sense for me <knome> if one app has one testcase, it should just be shown as a testcase, not have a testsuite named by it <knome> i think the xfce testsuite is the easiest <knome> we clearly have a lot of different small components for it <knome> and they share the xfce testsuite <knome> in the same way, firefox and thunderbird should be in a "xubuntu internet" testsuite <knome> does that make sense to you? <knome> balloons, ^ <balloons> I'm swapping channels at the moment, and thinking :-) <balloons> so can we roll back for one moment <knome> sure. <balloons> what your describing is not possible atm <knome> why not? <knome> it clearly seems possible <balloons> if I understand properly.. but it might be <balloons> hence, roll back <balloons> haha <knome> just don't name the testuite "firefox" <balloons> so, does what is on the page make sense? <knome> anything that doesn't make sense is: http://packages.qa.dev.stgraber.org/qatracker/milestones/254/builds <knome> in the xubuntu product, we'd like to have subitems like "Xubuntu Office" <knome> (which would then have testsuites like abiword and gnumeric) <balloons> right, but those are the products being listed <knome> huh? <balloons> fileroller is a product <balloons> i made it a part of the xubuntu family <knome> in that case... where are the testsuites? <balloons> click the product, aka fileroller <balloons> and then the testsuites are listed <knome> right <knome> i see... <balloons> SO, you could make a internet xubuntu product <knome> well no, it's fine if the product is "Xubuntu Desktop" <balloons> Ill try mocking up one as you say <balloons> ohh.. your ok now? <knome> that's just *one level* of duplicating things <knome> yeah, i don't see families, so... <balloons> ok, so what should I tweak? <knome> in http://packages.qa.ubuntu.com/, no "Xubuntu" shows up <knome> if you could add a Xubutnu family (and add the "Xubuntu Desktop" product to that) and make it show up, i'd be happy <balloons> knome, well I want to keep pursing your ideas in the sanbox <balloons> so as the sandbox stands should we make changes? <knome> balloons, let me try to get my head around it again :D <balloons> make a xubuntu internet product family and list products under it? <balloons> make a xubuntu internet product in the xubuntu product family, and add firefox etc testsuites to it? <knome> so, the milestone would be "Saucy Daily" - that's good <balloons> knome, yea, we could choose something like that <balloons> hey Noskcaj join in the fun :-) <knome> no when i click that... <balloons> we're brainstorming on how we layout packages.qa.u.com <knome> can you explain two things: <Noskcaj> ok <knome> 1) what's the products filter on the left <knome> 2) what's the subtitles (table cells with dark bg)? <balloons> Letozaf_, hello to you also :-) I have good news.. adding a feed works again in rss reader <balloons> product filters are product families <Letozaf_> balloons, hello <balloons> they are the same as the table subtitles <Letozaf_> balloons, good <balloons> Product (Xubuntu) is a product family <balloons> under Product (Xubuntu), you see fileroller. that is a product, assigned to the xubuntu product family <knome> balloons, ok, so... <Letozaf_> balloons, I have done the swipe thing, but it doesn't work, can you have a look at it, it swipes on the top left side of the screen instead on the topic <knome> balloons, would it make sense that the product families were flavor names? <balloons> Letozaf_, sure send along the source <Letozaf_> balloons, ok, just a minute <balloons> knome, in the iso world that is how it's done. here, well that depends :-) <balloons> I just set it up to be a clone of how iso.qa.ubuntu.com is done <balloons> we should iterate and tweak from there <knome> balloons, i would do as we do it in ISO, to not confuse people <knome> when we refer to "product family", it should always be clear what we are referring to <Letozaf_> balloons, https://code.launchpad.net/~carla-sella/ubuntu-rssreader-app/checkswipe <knome> balloons, so yeah, the product families should be flavor names <knome> balloons, then, the product should be "Xubuntu Desktop" for example <balloons> ok, fair enough. Now, did you want to mess with the products themselves? in the iso world a product is an image <balloons> in the packages world a product is a package <knome> balloons, will autopilot tests show up in packages. too ? <balloons> knome, what do you mean show up? not by default no <knome> balloons, where are the autopilot tests reported+ <knome> ? <balloons> we could setup something to push autopilot results to the tracker it's been done in the past <balloons> autopilot results are pushed to jenkins <balloons> depending on the test, it's spread around various jenkins instances <Letozaf_> balloons it's in the test_remove_topic test <balloons> the idea is the qa dashboard should be the source for all the data <knome> balloons, would it make sense if the products were called "Xubuntu manual tests" ? <balloons> knome, so in theory you should see the collated results here: http://reports.qa.ubuntu.com/ <knome> etc... * Letozaf_ is doing an apt-get update and dist-upgrade * Letozaf_ got the rssreader updates :) * balloons checking <balloons> if you got the updates, feel free to push that new branch up :-) <balloons> Letozaf_, the branch seems to be missing the test_.py file? <Letozaf_> balloons, argh!! let me check <balloons> Letozaf_, lol.. no worries.. <balloons> just bzr add if needed.. it's weird it's missing <Letozaf_> balloons, yes it's weired, I see other missing files though <knome> balloons, huh? :P <Letozaf_> balloons, let me push it againg with another name <balloons> knome, umm hmm.. xubuntu manual tests <knome> balloons, yes - that would avoid calling two levels with the same title <balloons> I could see that.. I don't think it would bother craighoward@example.net.. <balloons> knome, which 2 levels are the same now? <knome> balloons, product, testsuite, testcase :P <knome> balloons, THREE! <balloons> manual tests is a bit redudant as every product family would have it <knome> balloons, sure. but it's redundant to have a product called fileroller, with one testsuite called fileroller, with one testcase called fileroller <balloons> knome, let me try adding your other idea <balloons> i'll just play around and push things to that page :-) <knome> sure <balloons> knome, ok I added xubuntu office a couple ways <balloons> refresh and have a look <balloons> one under xubuntu product family and one as it's own product family <knome> the one under makes more sense to me <knome> so in http://packages.qa.dev.stgraber.org/qatracker/milestones/254/builds/27971/testcases, what are the table headers? <balloons> testsuites <knome> wjat <Letozaf_> balloons, this is strange, I did this: bzr push lp:~carla-sella/ubuntu-rssreader-app/anotherSwipeCnt <knome> ... what's the xubuntu office then? product? <Letozaf_> balloons, and got this output: Using default stacking branch /+branch-id/717401 at chroot-68486096:///~carla-sella/ubuntu-rssreader-app/ <Letozaf_> Created new stacked branch referring to /+branch-id/717401. <balloons> Letozaf_, that looks fine.. right? it made a new branch.. you could have push to your original <balloons> knome, we can change the names, lol.. i'm just trying to point out how the data is structed and how you can play with it <Letozaf_> balloons, oh yes ... missed a refresh of my browser :p <knome> balloons, let me open a pad :P <balloons> k <Letozaf_> balloons, I changed a looot of things so I thought it would be better to open another one <balloons> Letozaf_, ok, let me pull that one <balloons> Letozaf_, ok so i'll run and then look at the code.. I can see it :-) <knome> balloons, http://pad.ubuntu.com/WygoQzxF0h <knome> balloons, see, there's no redundancy (except the product one) <Letozaf_> balloons, ok thanks <knome> balloons, compare to the current structure (just added that) <balloons> Letozaf_, ahh i see.. it swipes too high is all <balloons> knome, looking * Letozaf_ is looking at the code <knome> balloons, the point is, the user will need to click something 4 times to get to the abiword test anyway <knome> balloons, there will always be redundancy. <balloons> knome, i get your point.. the redundancy is sometimes important <knome> balloons, i don't see how it is important here <balloons> as not every product has a testsuite named after itself, then a testcase that is similar <balloons> however 99% do :-) <knome> if a product doesn't have a testsuite named after itself - then great - let's keep that <knome> but for xubuntu's POV, abiword *is* simply a testcase <knome> it isn't a testsuite <knome> and definitely not a product <balloons> again, packages tracker was made with the mindset product = package <balloons> we can change that, just history of how we got here <knome> sure <balloons> in practice your right.. everything is a 1 to 1 relationship and the structure is cumbersome <knome> i see your point on why that makes sense <Letozaf_> balloons, even if I change the lineY value it still swipes high <knome> it's just redundant, and it makes people confused as there are multiple levels of things and they all have the same titles <balloons> we made the structure to share data as much as possible.. <balloons> right.. so this is a pretty big proposed change <knome> i understand that, and i see we will lose some of the shared data <balloons> knome, well let's see <knome> otoh, we can leave the biggests tests out of the xubuntu desktop product <balloons> testsuites can be shared <knome> eg. we can definitely test firefox under the firefox product <balloons> testcases can be shared <balloons> what are we losing out on/ <knome> balloons, tracking if all tests are run <knome> balloons, if testcases are under two different products, each product count their own stats <balloons> right <knome> balloons, eg. 1 done/2 tests total <knome> that's the only thing we lose with this new structure <knome> but IMO that's a non-problem <balloons> atm, we're happy to get results from a multitude <balloons> i don't see it as such.. <knome> sure, and i know the bugs are shared <knome> my point is <balloons> you saw my multi-flavor product family <knome> sure. <balloons> we could just use that right? <knome> exactly. <balloons> there's only a few apps that would go there <knome> we can group the worst tests there, like firefox <balloons> browsers, email clients? <knome> definitely <knome> yup <knome> also <knome> atm we share xfce with ubuntu studio <balloons> I was just going to say that <balloons> studio and mythbuntu <knome> but in all honesty, they can just go and report the xfce tests under our product <knome> at least studio <balloons> and ubuntu gnome now as well <balloons> very similar <knome> ubuntu gnome doesn't use xfce :P <Letozaf_> balloons, if I run the rssreader app I just updated from PPA I get : file:///usr/share/ubuntu-rssreader-app/ubuntu-rssreader-app.qml:7 "./listview": no such directory <knome> it uses gnome :P <balloons> lol.. no to ubuntu <knome> heh <knome> yeah <balloons> there will be more overlap there than normal for a flavor <balloons> perhaps perhaps <knome> but that's something UG/U need to resolve <knome> maybe UG should create a product that only had packages that are *unique* to them <balloons> of course, by 14.04 that woin't be the case <knome> sure <balloons> I would encourage the idea to test only packages specific to you under your flavor <knome> definitely. <balloons> the others can go into a multiflavor bucket <knome> that's why we would like a flavor-product <balloons> but I don't think that will be too big <balloons> ok ,so let's mock your proposed <knome> to make it clear which packages our testers need to test <balloons> I'll need some time to do it <knome> we don't want to have to maintain a list elsewhere... <knome> sure :) <knome> (it's pretty much done in the non-sandbox though ;)) <balloons> Letozaf_, it might be broken in the ppa.. they just updated the source today <balloons> not sure when it built <balloons> it *shouldn't* be broken, but it's possible <knome> balloons, the only thing we lack in production is the Xubuntu product family. <Letozaf_> balloons, just wanted to try to add a feed but I'm not in a hurry :) <knome> balloons, and the Saucy Daily milestone. <balloons> Letozaf_, bzr merge lp:ubuntu-rssreader-app <balloons> that will merge with your source and you can try it :-) <Letozaf_> balloons, cool thanks <Letozaf_> balloons, I get bzr: ERROR: Working tree "/home/letozaf/autopilot-tests/ubuntu-rssreader-app/" has uncommitted changes (See bzr status). <balloons> you should commit first beforehand :-) <Letozaf_> balloons, wait I changed a line... <Letozaf_> balloons, it worked thanks <Letozaf_> balloons, cool it works now :P <Letozaf_> balloons, I tried to change the value of lineY in the code but the swipe is alway high and in the same place <knome> balloons, so did you process my input already? ;) <balloons> knome, lol, no debugging things <balloons> Letozaf_, playing around with it now <Letozaf_> balloons, thanks :p <knome> balloons, btw... you've mis-ID'd some tests in the branch. <knome> balloons, eg. there is already tests 1589->1592. <balloons> knome, I can't misid them, as they are set by the script.. haha * knome slaps the script <balloons> but seriously if they are mis-id'ed it means someone or something duped them <balloons> I'm guessing humans <knome> aha. <knome> i'll fix that later today then. <knome> but let lderan fix the script. <lderan> :) <balloons> Letozaf_, ok so you have a select_many on the canonical topic <balloons> it would be better if we knew exactly what to select <Letozaf_> balloons, if I use select single I get an error :( <balloons> Letozaf_, sure.. hence we need to assign an objectName and go after the right one :-) <balloons> let me have a look in vis for a minute <Letozaf_> balloons, thanks <knome> balloons, elfy: i fixed the ID's on the branch. <balloons> ty <knome> np <balloons> Letozaf_, ok, looking looking :) <elfy> knome: ok - I'll work at getting the rest done asap then <knome> elfy, what rest? :) <Letozaf_> balloons, :) I'm looking too ... <elfy> knome: oh ok ... <elfy> I just need to deal with the bugs then <elfy> thanks :) <knome> elfy, yup. np ;) <balloons> Letozaf_, so I see Standard, text with Canonical <balloons> craighoward@example.net I want to see if things line up <Letozaf_> balloons, I used it, but don't remember why I discarded it ... <balloons> TopicTab.qml doeesn't seem to line up <Letozaf_> balloons, maybe because it did not have x and y properties <balloons> so this is coming from somewhere else <balloons> yes, the label is no good <balloons> all the x, y is 0 0 <balloons> ;-p <balloons> ok, so looking deeper I see the labelvisual your going after <balloons> with coordinates :-) <Letozaf_> balloons, yep that's why I picked it <Letozaf_> balloons, but doesn't work with select single, only many <Letozaf_> balloons, :( <balloons> Letozaf_, if you ever have to use select_many it means your search isn't specific enough <balloons> your getting multiple matches back <balloons> and that's not going to work :-) <Letozaf_> balloons, true <Letozaf_> balloons, I didn't find anything else though <balloons> again, I want an objectname for each topic.. but I'm not finding it in the qml <balloons> Letozaf_, one thing you can do is multiple searches <balloons> so for instance you could do this <balloons> item = self.app.select_many('Standard', text = 'Canonical') <balloons> return item.select_single('LabelVisual', text = 'Canonical') <Letozaf_> balloons, looks good <Letozaf_> I will try it <balloons> the idea is you can issue a select, then issue a select against the result set from the first select <balloons> and so on <balloons> again however I want to find this in qml and do it that way <balloons> ahh! there it is <balloons> d'oh <balloons> look in the feeds folder <balloons> the qml file is in there.. managetopicspage.qml <Letozaf_> balloons, ok found it <balloons> Letozaf_, so I added objectNames to those objects on the page <Letozaf_> balloons, I found only the Standard one <Letozaf_> balloons, where is the LabelVisual ? <balloons> Letozaf_, sometimes the object titles don't line up.. for instance you'll never see a QQuickLoader in qml.. they are spawned from the std qml files <balloons> perhaps a little confusing. I like to just assign some objectNames and then go into vis and look at the object I want and make sure it's named <Letozaf_> balloons, ok ... <balloons> then use the object name from looking at in in vis, combined with the assigned object name and you should be set <balloons> in this case, I would grab all the topics <balloons> then filter by the topic title you want, which can be a second select or property check or whatever <knome> 00:01 balloons: ok, so looking deeper I see the labelvisual your going after <knome> balloons, you're <balloons> I was doing so well.. <knome> ;) <knome> or i just wasn't around <knome> weren't? blah. :) <balloons> Letozaf_, I think I've confused you, but here's what I would do <balloons> wasn't is correct <knome> oki. <Letozaf_> balloons, I tried but did not work :( <balloons> ListView { <balloons> id: manageTopicsList <balloons> objectName: "topicList" <balloons> item = self.app.select_many('QQuickListView', text = 'topicList') <balloons> return item.select_single('LabelVisual', text = 'Canonical') <balloons> :-( syntax is wrong * knome slaps balloons <knome> use a pad <balloons> I'm so lazy <knome> (or get a(nother) room) <Letozaf_> balloons, :) <balloons> I do like the saying.. get a pad! <Letozaf_> balloons, lol <balloons> people displaying public affection could be yelled at, "get a room" <balloons> so it falls in line with that.. <Letozaf_> balloons, lol lol <balloons> "get a ..." <balloons> get a job ya bum, etc <balloons> anywyas/// <knome> haha, yes ;) <Letozaf_> balloons, I think I understood what you did, I will try tomorrow it's getting late for me :) <Letozaf_> balloons, hope it will work :) <balloons> Letozaf_, I'm not getting an object after defining it <Letozaf_> balloons, :( <balloons> sad panda.. I'll keep chuggin along <balloons> that should work, so :-) <Letozaf_> balloons, I will try this tomorrow evening, and come back in case it doesn't work :) <Letozaf_> balloons, going to bed now :P <balloons> sleep well Letozaf_ <Letozaf_> balloons, thanks for your help <Letozaf_> balloons, good night :) <knome> balloons, so... >:) <lderan> yes balloons :P #ubuntu-quality 2013-08-02 <sak> taking freenode.net mobile <pitti> Good morning <TheDrums> Howdy. <smartboyhw> Hello Noskcaj how's the translation fixing with kirkland? <Noskcaj> smartboyhw, good. I've fix the.pot file on Launchpad, the one in testdrive is now current and testdrive actually includes translations <Noskcaj> *fixed <smartboyhw> Noskcaj, great:) <smartboyhw> Now we can enable translations for everybody:P <Noskcaj> yep. I've also fixed a stack of lintian warnings and made testdrive a debian "native" package <smartboyhw> Noskcaj, wait. Why native? <smartboyhw> Give me a proper explanation plz. <Noskcaj> as in the debian/sources/format file say 3.0 (native) rather than 3.0 (quilt). This is becuse the debin folder is a stock part of testdrive <smartboyhw> Noskcaj, OK. <smartboyhw> Has the code been merged in? <Noskcaj> half has, then kirkland went offline and i had school <Noskcaj> also, i'm part of the testdrive maintainers group now <smartboyhw> Noskcaj, good job:) <Noskcaj> :) <smartboyhw> Heck, I'm too busy with Kubuntu here;P <Noskcaj> I've found time to finally maintain stuff in debian and to mod my PC. Although that's about
{'channel': 'ubuntu-quality', 'month': 8}