[00:01] <komputes> balloons: ok merge requests done for FF and TB
[00:03] <komputes> balloons: also ManualStyleGuide is immutable :(
[01:04] <balloons> komputes, ohh really? you can't edit? you sure your logged in?
[01:21] <phillw> balloons: sorry to say, but I took my eye off the bug, and it is now again a problem for us human testers... bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674
[01:46] <fenrw> yes, I ran into that one as well
[01:49] <phillw> fenrw: I can only apologise, I thought it had been sorted.  I do try to keep up with the VM issues:'(
[01:50] <balloons> :-(
[01:51] <fenrw> phillw: it was the first test I ran, I thought it was a problem with the VM at first (ran from testdrive/kvm) I ran it on aquemu next and it was fine
[01:52] <phillw> balloons: with that many confirming it, I mistakenly thought it was .... "Yeah, they will get it fixed". I lost out.
[01:53] <phillw> balloons: of course, I could always ask as to why our canonical type person never followed the bug to completion :P
[01:56] <phillw> fenrw: I do seem to have become the guy to push VM bugs, But in all honesty, I cannot keep with them all, I do follow those that affect me and any of the testers who nag me.
[02:01] <fenrw> what is the best course to take when running a test and you hit a bug like that?
[02:02] <fenrw> phillw:
[02:07] <phillw> fenrw: nag me and balloons :D
[02:09] <phillw> fenrw: the -release team do cut me a lot of slack (i.e., they do allow me to nag them over such things)
[02:11] <fenrw> phillw: okay, I will test again tomorrow ;-)
[02:12] <phillw> with VBox 4.2 arriving, and test drive hopefully being able to use it. With the KVM issue I am kept caught sort of busy. But, that is not a real complaint. I just want you guys to have the testing tools that you prefer.
[02:13] <fenrw> well it's good to test on multiple VMs as that shows
[02:14] <phillw> I'm a KVM person, but I do appreciate that others prefer such as VBox.
[02:16] <balloons> fenrw, with any bug you find, it's best to keep up with it.. report and ensure the folks responsible have what;s needed to fix i
[02:16] <balloons> then just follow up over time and when the fix is ready, help confirm it
[02:16] <phillw> With Vbox 4.2 arriving, I have the 'fun' of teaching people about LVM's. http://en.wikipedia.org/wiki/Logical_volume_management
[02:18] <phillw> balloons: once Vbox 4.2 arrives fully and test drive supports it. I do think we need to tell people about LVMs
[02:18] <fenrw> I marked that it affects me, i'll continue to watch it
[02:22] <fenrw> phillw: how will LVM affect things?
[02:22] <phillw> SergioMeneses it seems the ubiquity bug has been sorted, but we have a regression in KVM. Please try in Vbox
[02:23] <SergioMeneses> phillw, I'm downloading it
[02:24] <phillw> fenrw: instead of having to reboot each time you make a new extended partition area, you can make an new area without needing to re-boot.
[02:25] <komputes> balloons: sorry, i wasn't logged in, thx
[02:25] <balloons> komputes, :-)
[02:26] <phillw> LVM and KVM are very closely tied together in how they work. They also run as the system that makes cloud computing possible.
[02:28] <phillw> fenrw: They are parts of the kernel, that being the low level part of linux. that makes a computer work. Both KVM and LVM are 'in the system', they just need turning on.
[02:28] <SergioMeneses> hey komputes !
[02:28] <SergioMeneses> balloons, \o
[02:28] <xnox> LVM and KVM are not related at all.
[02:29] <fenrw> hm, I don't know much technically behind KVM, Vbox, etc. Mostly have experience with VMWare
[02:29] <xnox> LVM - does disk management, such that you can treat multiple block devices as a pool of available space and allocate slices.
[02:29] <komputes> ola SergioMeneses
[02:30] <phillw> xnox: LVM is built into the linux kernel?
[02:30] <SergioMeneses> komputes, hola! hablas español?
[02:30] <xnox> KVM - does virtualisation aka faking enough for a different linux kernel to believe it's booting on a real system.
[02:30] <komputes> SergioMeneses: um poco
[02:30] <phillw> xnox: KVM is buily into the linus kernel?
[02:30] <fenrw> LVM sounds like a feature for multiple VMs on a single host utilizing a SAN
[02:30] <xnox> phillw: it's a kernel module, but so is btrfs and a module for your webcam.
[02:31] <komputes> SergioMeneses: so I got started on my own branch and made some changed to FF and TB
[02:31] <xnox> fenrw: My main machine is installed on lvm, cause it allows me to make snapshots and use snapshot as scratch throw away space for packaging building.
[02:31] <phillw> xnox: so, as I said that they are built in, where was I wrong?
[02:32] <xnox> LVM and KVM are no tied together at all. as they are complete different sub-systems / features.
[02:32] <xnox> s/no/not/
[02:32] <phillw> xnox: I did not say that, i said that they work together?
[02:33] <SergioMeneses> komputes, mmmm
[02:33] <xnox> "<phillw> LVM and KVM are very closely tied together in how they work"
[02:33] <xnox> lvm is implemented on windows, sun, mac osx etc. it's quite a generic concept https://en.wikipedia.org/wiki/Logical_volume_management
[02:34] <SergioMeneses> komputes, pm
[02:34] <SergioMeneses> see you there
[02:34] <xnox> kvm is one way to do virtualisation, xen virtualbox vmware are different ways to achieve virtualisation
[02:34] <phillw> xnox: yes, they are both available in the kernel and need no tweaking of the kernel to have them function? I was not trying to split hairs :D
[02:35] <xnox> they require some kernelspace modules, but they are mostly user-space utilities.
[02:35] <phillw> xen is an overlay, now out dated. It uses an overlay to access the kvm area.
[02:35] <xnox> just by having a linux kernel - without lvm2 command-line binary you will not be able to do anything with lvm volumes.
[02:36] <xnox> xen is rapidly developed and has features that are not available in kvm.
[02:36] <xnox> and hardly can be called an overlay.
[02:37] <phillw> xnox: xen is not built into the kernel.
[02:37] <xnox> sure it is.
[02:37] <xnox> one needs xen kernel modules for dom0 support
[02:38] <SergioMeneses> where is smartboy?
[02:39] <phillw> xnox: http://blog.codemonkey.ws/2008/05/truth-about-kvm-and-xen.html
[02:40] <phillw> I'm not wanting an argument, just what is current for new-commers
[02:44] <xnox> phillw: two years later xen dom0 support got merged as part of 2.6.37 and 2.6.39 kernels. phillw, 5 years is a long time.
[02:45] <xnox> compare raring with hardy
[02:45] <phillw> 3.5 now...
[02:45] <phillw> xnox: I do want an argument!
[02:46] <phillw>  *DO NOT*
[02:46] <phillw> the job's I see, ask for KVM.
[02:48] <fenrw> somewhere in here, LVM and xen got interchanged and can't tell who or for what :)
[02:52] <phillw> fenrw: join the club... LVM is a system that is more easy to use than extended partitions. I've had to hold off as I was awaiting VBox 4.2 to arrive and test drive be able to use it.
[02:54] <fenrw> testdrive is pretty nifty, does it delete the VM when you close it?
[02:54] <fenrw> I don't see a way to load an existing VM from it, so I am assuming so
[02:57] <fenrw> I need to read the config file again :)
[02:57] <phillw> it gets a bit complicated. If you have extended partitions you can make a new one and do a live boot (real machine). Using areas with the virtual machines you can allocate an area on the hard drive similar to Wubi
[02:58] <phillw> The reason of using a section of hard disk (LVM) is that it will remain after a fail.
[03:00] <phillw> as xnox has had to really talk me through getting a log from my KVM system, in words of on syalble. He's best at saying if it can be done from VBox and from having a system that is not LVM per machine.
[03:03] <fenrw> hmmm, lost me on that last part
[03:04] <phillw> it is 03:00 here , the questions and comments here tonight to need addressing so we can better let new testers know what is best helpful for getting results from a failed install.
[03:05] <SergioMeneses> phillw, it works! :) using Vbox
[03:06] <phillw> fenrw: I'll book some time with xnox, who is far more experienced than I am. If he can explain it to me, I can then write it up so anyone can understand it :)
[03:07] <phillw> SergioMeneses that's great, just means we have a regression on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674
[03:07] <phillw> One step forward, one step back :D
[03:08] <SergioMeneses> phillw, I think so xD
[03:08] <fenrw> I haven't gotten testdrive and vbox to work yet
[03:08] <SergioMeneses> btw we have the same bug about the slides :S
[03:09] <phillw> fenrw: have a chat with SergioMeneses, he is best placed to help you with VBox
[03:10] <fenrw> I might give it a try loading without testdrive and make sure it works that way first
[03:10] <fenrw> or, not make sure, but see
[03:12] <SergioMeneses> fenrw, I use testdrive to get the isos, then I open Vbox and choose the iso  ~/cache/testdrive/iso
[03:12] <SergioMeneses> but you can use both, it is not a big deal :)
[03:13] <fenrw> I tried that, I'm getting an error about pae both ways
[03:13] <SergioMeneses> phillw, lubuntu installer has not background
[03:13] <SergioMeneses> fenrw, which error?
[03:13] <fenrw> kernal requires the following features not present on the CPU: pae
[03:14] <fenrw> unable to boot - please use a kernal appropriate for your CPU
[03:15] <SergioMeneses> fenrw, here is the solution http://askubuntu.com/questions/164764/virtual-pc-error-unable-to-boot-please-use-a-kernel-appropriate-for-your-cpu
[03:16] <SergioMeneses> or this one http://www.linuxliveusb.com/en/help/faq/virtualization/154-unable-to-boot-please-use-a-kernel-appropriate-for-your-cpu
[03:16] <fenrw> $ arch
[03:16] <fenrw> i686
[03:16] <fenrw> installing raring-desktop-i386.iso
[03:16] <fenrw> which works on aqemu
[03:16] <fenrw> I'll take a look at those
[03:17] <SergioMeneses> balloons, phillw busy?
[03:17] <SergioMeneses> fenrw, :)
[03:17] <balloons> SergioMeneses, bedtime for moi
[03:17] <SergioMeneses> balloons, ok.. dont worry
[03:18] <SergioMeneses> balloons, we have the new testcase for thunderbird now :D
[03:19] <balloons> SergioMeneses, yay!
[03:19] <SergioMeneses> https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1115645
[03:19] <fenrw> SergioMenenses, It looks like the second one might help, I've ran into the first one as well when i tried to install the AMD64 version.. to be honest not sure why my arch says i686 when it's an AMD x2 64bit
[03:19] <SergioMeneses> you can check it tomorrow :D
[03:19] <balloons> yea, i have several things to merge looks like
[03:19] <balloons> very good work
[03:19] <SergioMeneses> fenrw, dont worry, take your time :D
[03:19] <SergioMeneses> balloons, and thanks to komputes for his help :)
[03:20] <komputes> Glad to help.
[03:21] <fenrw> thanks SergioMeneses, clicking that checkbox fixed it :)
[03:22] <SergioMeneses> fenrw, jejeje nice
[03:26] <fenrw> I booted the raring-desktop-i386 vbox to a live disk and got a system program problem detected
[03:30] <SergioMeneses> fenrw, ?
[03:30] <komputes> balloons: I'll try to look out for the test naming convention next time
[03:30] <fenrw> looks like colord-sane crashed
[03:37] <fenrw> I wonder if it has to do with the 32-bit/16-bit color warnings vbox was giving me earlier
[03:39] <SergioMeneses> fenrw, mmmm... sounds rare, I dont have any issue like that
[03:39] <SergioMeneses> phillw, ? ↑↑↑↑
[03:44] <komputes> I'm having a hard time clicking on the bottom bug here: http://packages.qa.ubuntu.com/qatracker/milestones/256/builds/37168/testcases
[03:45] <komputes> the one that links to 1127331
[03:45] <komputes> Anyone else can reproduce?
[03:49]  * SergioMeneses can not find his yubikey
[03:51] <balloons> komputes, same for me :( https://launchpad.net/ubuntu-qa-website/+filebug Although there is an existing bug with the rollover pop-ups already (they cutoff). might want to link them
[03:52] <SergioMeneses> balloons, is it broken?
[03:52] <SergioMeneses> it doesnt work for me
[03:56] <komputes> balloons: https://bugs.launchpad.net/ubuntu-qa-website/+bug/1035503 ?
[03:56] <balloons> komputes, yes that's the one
[03:56] <SergioMeneses> komputes, ++
[03:56] <balloons> k, I'm really really off now.. had to post to g+ :-_)
[03:56] <balloons> g-night
[03:57] <SergioMeneses> balloons, good night!
[03:58] <komputes> night SergioMeneses
[03:58] <komputes> night balloons
[03:59] <SergioMeneses> komputes, \o
[04:27] <fenrw> I only get the error when booting with vbox to a live session (I haven't tried a full install yet in vbox)
[04:28] <fenrw> (colord-sane crashed)
[04:42] <SergioMeneses> fenrw, which iso are you testing?
[04:42] <SergioMeneses> ubuntu-daily?
[04:42] <fenrw> Sergiomeneses raring-desktop-i386
[04:42] <fenrw> yeah
[04:42] <fenrw> ubuntu
[04:46] <SergioMeneses> fenrw,  look all bugs for live-session http://iso.qa.ubuntu.com/qatracker/milestones/243/builds/38045/testcases/1303/results
[04:47] <SergioMeneses> check if your error is there
[04:50] <SergioMeneses> ok guys! bed time... see you later
[06:26] <pitti> Good morning
[06:37] <Noskcaj> evening pitti
[07:07] <pitti> jibel: do you have an idea why inotify doesn't work in the jhbuild container?
[07:07] <pitti> jibel: e. g. tail -f always shows that error, and turns out that it's also the very likely cause for the e-d-s failure
[07:20] <pitti> jibel: confirmed
[07:20] <pitti> jibel: googling does show some hits with "too many open files" if there are many containers, but this only runs a handful
[07:51] <jibel> pitti, good morning
[07:51] <jibel> pitti, correct, max_users_instance is set to 128, I'll increase to 512
[07:54] <jibel> pitti, can you retry the test
[08:03] <pitti> bonjour jibel
[08:04] <pitti> jibel: ah, I was going to ask you to try that, thanks
[08:04] <pitti> trying
[08:04] <pitti> \o/
[08:04] <pitti> both tail and evolution-source-registry are happy again
[08:05] <jibel> Yay!
[08:05] <pitti> merci
[08:09] <pitti> jibel: that was the sysctl on the rabisu host, not within the container, right?
[08:09] <jibel> pitti, right, on the host.
[08:10] <jibel> I added the change to sysctl.d/60-custom.conf to preserve the setting on reboot
[08:19] <pitti> jibel: for webkit, could that be "webkit" vs. "WebKit" confusino somewhere?
[08:20] <havryliuk> hi, that's me again ;)
[08:20] <havryliuk> anyone good at autopilot? i am having some basic configuration issues, i think
[08:20] <pitti> jibel: (currently doing a manual jhbuild buildone webkit to see whether it's actually failing)
[08:20] <jibel> pitti, that'd be surprising becuase we use the names returned by jhbuild, so they should be consistent
[08:21] <pitti> gosh, this is an unholy fast machine
[08:21] <pitti> it compiles faster that it can scroll through byobu/ssh
[08:25] <pitti> $ jhbuild run pkg-config --modversion webkitgtk-3.0
[08:25] <pitti> 1.11.5
[08:25] <pitti> jibel: ^ ok, so it does build on the machine at least \o/
[08:26] <pitti> jibel: I'll see whether I can reproduce that in automatic mode
[08:28] <pitti> jibel: so jenkins pulls current status/results from rabisu every 10 minutes, right?
[08:28] <jibel> pitti, 2 minutes
[08:29] <pitti> hm, https://jenkins.qa.ubuntu.com/view/Raring/view/JHBuild%20Gnome/ looks like 10
[08:29] <pitti> I usually get the "latest builds" in batches with roughtly the same time, around :02, :11, :12, etc.
[08:29] <jibel> ah, let me check that
[08:30] <pitti> jibel: no worries, it's fine; I just want to understand how that works, i. e. jenkins regularly gets a file from rabisu?
[08:30] <jibel> url check schedule: */2 * * * *
[08:31] <jibel> but there is the publisher in-between so maybe that adds a delay
[08:31] <pitti> ah
[08:32] <jibel> pitti, so every 2 min, jenkins checks if a *.revno file has changed and start a new job if it did
[08:32] <pitti> those in /var/log/jenkins/
[08:32] <jibel> pitti, this job checks *.state files for the result and stops when it's pass/fail or unstable
[08:32] <jibel> pitti, /var/log/jhbuild/
[08:32] <pitti> err, /var/log/jhbuild of course
[08:33] <jibel> pitti, and collect the log file on completion
[08:33] <jibel> I did it this way because of the very restricted policy between the lab and the rest of the work
[08:34] <pitti> jibel: how does it determine "changed"?
[08:34] <jibel> world
[08:34] <pitti> mtime since last call?
[08:34] <jibel> pitti, it checks the content which is the revision number of the module + a timestamp
[08:35] <pitti> jibel: ah, so if that's later than $last_run, it considers it as "has a new build"?
[08:35] <jibel> pitti, initially I used only the state file, and I think I should go back to only use it
[08:37] <jibel> pitti, if that's later than $last_run, it will start a job, and finish immediately with the result of $last_run
[08:38] <jibel> pitti, it's really hackish
[08:40] <pitti> https://jenkins.qa.ubuntu.com/view/Raring/view/JHBuild%20Gnome/job/jhbuild-amd64-baobab/100/artifact/baobab.log
[08:40] <pitti> meh, I wonder if we should run with --distclean and install ccache
[08:40] <pitti> I've seen issues like that a lot
[08:41]  * pitti wonders whether -C/--try-checkout also cleans the source tree, checking
[08:41] <pitti> ok, jhbuild doesn't call git clean-tree anywhere
[08:42] <pitti> argh, my bad, it's "clean", not "clean-tree"
[08:47] <pitti> jibel: so it seems we already call jhbuild with -C
[08:53] <jibel> pitti, yes, but I think this option should completely wipe the source tree
[08:53] <pitti> right, it should
[08:53] <pitti> jibel: ignore me for now, I think that might be an actual regression
[08:53] <pitti> I'm doing a local build and investiage
[08:53] <pitti> hah, it is
[08:54]  * pitti heads bugzillawards
[08:56] <jibel> hm, force_checkout already calls self._wipedir(buildscript, self.srcdir)
[08:56] <pitti> jibel: yes, doesn't help
[08:56] <havryliuk> could anyone help with autopilot? ^__^
[08:56] <pitti> jibel: the error occurs on a fresh checkout, it's an actual bug
[08:56] <jibel> ok
[08:57]  * pitti ^5s jibel
[08:58]  * jibel ^5s pitti back
[08:59] <jibel> havryliuk, usually autopilot gurus hang out in this channel later in the day, like middle of the afternoon (european time)
[09:00] <havryliuk> jibel, i see, thanks, will chase them later ;)
[09:10] <pitti> jibel: I pushed the fix into baobab, now waiting for jhbuild to finish :)
[09:12] <jibel> awesome :)
[09:12] <pitti> meh, it keeps resetting my changed checksums in jhbuild.modules without actually rebuilding
[10:36] <pitti> jibel: could you help me understand some mechanics here?
[10:37] <pitti> jibel: so I pushed that baobab commit (593bd4), and jhbuild-data/jhbuild.modules now has that
[10:37] <pitti> but /var/log/jhbuild/baobab.* still has the old revision
[10:38] <pitti> jibel: that means that jhbuild is past the "checkout" stage, but didn't get round to building it yet, right?
[10:38] <pitti> (gnome/checkout/baobab/ is also current, i. e. at 593bd)
[10:38] <jibel> pitti, correct, old version was jhbuild.modules.bak:baobab (2d89dd812410e8fa03fd98076707917cc7c835ea)
[10:38] <pitti> *nod*
[10:38] <jibel> pitti, new version is jhbuild.modules:baobab (593bd4016a3bfa5f46804eaea7b9f91c72ac3b38)
[10:39] <jibel> and it is still in the queue jhbuild.updates:baobab (593bd4016a3bfa5f46804eaea7b9f91c72ac3b38)
[10:39] <pitti> jibel: oh, thanks for pointing out ~/jhbuild-data/jhbuild.updates
[10:39] <pitti> that's useful
[10:40] <pitti> so folks is in there, too
[10:40] <pitti> webkit is still acting up, though
[10:40] <pitti> ok, I'll let that batch build, and try to reproduce some other failures
[10:41] <jibel> pitti, so it has detected the update but there are lot of packages queued
[10:41] <pitti> jibel: ok, what I thought; thanks for confirming
[10:41] <jibel> parallel builds will help with that
[10:42] <jibel> pitti, BTW +1 for ccache, go ahead if you want to install it, or I'll do it later today
[10:43] <pitti> jibel: doing now
[10:46] <pitti> jibel: what do you prefer, adding PATH definition to .bashrc or jhbuild.cron?
[10:46] <pitti> I think jhbuild.cron is better, then we won't forget to set it up
[10:46] <jibel> pitti, I don't mind, do what you prefer
[10:52] <pitti> jibel: https://code.launchpad.net/~pitti/charms/raring/jhbuild/ccache/+merge/150010, I locally updated jhbuild.cron, too
[10:55] <jibel> pitti, thanks
[10:55] <pitti> jibel: nice, fixing inotify fixed more failing tests (polkit, realmd)
[10:59] <jibel> pitti, nice catch on this one :)
[11:09] <pitti> jibel: btw, that branch doesn't yet have your sysdeps cleanups, right?
[11:10] <pitti> jibel: we need to install the "check" package in manual sysdeps (gdm needs it), want an MP from me?
[11:14] <jibel> pitti, no I haven't updated it yet, no need for an MP unless there is lot more. I added to the list of packages to update
[11:14] <pitti> jibel: merci
[12:31] <havryliuk> people, has anyone arrived that could help with autopilot? c:
[13:42] <pitti> jibel: tail: inotify cannot be used, reverting to polling: Too many open files
[13:42] <pitti> argh, that again!
[13:42] <pitti> jibel: it's like something is leaking inotify usage, or could it be that the other runnign containers are suddenly using more?
[13:42] <pitti> jibel: can we bump this to 5000 or so?
[13:43] <jibel> pitti, I'll bump it significantly and we'll search what's leaking inotify
[13:43] <pitti> jibel: oh, https://code.launchpad.net/~pitti/charms/quantal/jhbuild/jhbuild_from_git/+merge/130365 -> that should go to /raring now, presumably?
[13:44] <jibel> pitti, I merged it into raring
[13:44] <pitti> ah great, thanks
[13:44] <jibel> max_user_instances bumped to 8000
[13:44] <pitti> jibel: branch set to "merged"
[13:45] <pitti> jibel: ok, I guess that needs the container to restart
[13:45] <jibel> I'm shutting down all the other containers
[13:46] <jibel> pitti, ah, there might be another limit for the user
[13:48] <jibel> pitti, I disabled cron and will restart the container after the current run
[13:49] <pitti> jibel: ah, or that; I was going to wait until ibus finished install, and then kill it and reboot
[13:50] <pitti> well, there's some 20 more modules to go, let's let it finish
[13:52] <jibel> that's fine too
[13:53] <jibel> pitti, just tell me before rebooting i'd like to find the culprit
[13:53] <pitti> jibel: do you know a way to shop all open inotify handles?
[13:57] <jibel> pitti, I think that without something like auditd it's impossible, there is nothing reported by lsof the uses so many handles
[13:57] <pitti> yeah, I was already checking that
[14:09] <pitti> ah, figured out totem-pl-parser failure
[14:11] <pitti> jibel: building third-last module
[14:11] <pitti> jibel: we are missing libquvi-dev, but that ought to come in through sysdeps; I modified the upstream totem-pl-parser bug accordingly (should be fixed in jhbuild)
[14:12] <vibhav> I think far
[14:12] <vibhav> Oops, typp
[14:13] <vibhav> I think Raring will be the first development release that has never broken for me
[14:13] <pitti> really, never?
[14:13] <pitti> wow
[14:14] <vibhav> Indwed
[14:14] <vibhav> Indeed *
[14:14] <vibhav> Autopkgtest have made a difference
[14:14] <vibhav> Has*
[14:15] <smartboyhw> vibhav, that's awesome:)
[14:15] <vibhav> Awesome indeed
[14:15] <pitti> 2013-02-22 14:15:01 : jhbuild.cron Ended
[14:15] <pitti> jibel: want to do something before rebooting?
[14:15] <pitti> eek, it's running again, /me kills
[14:16] <pitti> jibel: now nothing is running on the box except getty, sshd, and udevd, and inotify is still broken; so I guess that does need a reboot to pick up the changed sysctl
[14:17] <jibel> pitti, reboot the host you mean?
[14:17] <pitti> jibel: no, reboot the container
[14:17] <jibel> pitti, ok, no problem
[14:18] <pitti> jibel: you asked me to tell you before I reboot the container
[14:18] <jibel> pitti, right, and there's no problem you can reboot :)
[14:20] <pitti> jibel: oh, neither WebKit nor realmd are in jhbuild-data/jhbuild.modules
[14:20] <pitti> jibel: that might have something to do with our problems?
[14:21] <jibel> pitti, did you restart the container ?
[14:21] <pitti> jibel: yes
[14:21] <jibel> tail: inotify cannot be used, reverting to polling: Too many open files
[14:21] <pitti> eek
[14:21] <jibel> :/
[14:21] <pitti> WTH
[14:21] <pitti> jibel: so maybe we need to restart rabisu
[14:21] <jibel> pitti, I'm tempted to restart the host
[14:23] <pitti> jibel: 7 minutes until cron kicks in again :)
[14:41] <pitti> jibel: thanks for rebooting; inotify seems happy again at least
[14:42] <pitti> oh, rebooting again apparently
[14:42] <jibel> pitti, forgot something before previous boot, sorry
[14:42] <pitti> np
[14:42] <jibel> pitti, I didn't think you'd login so promptly
[14:42] <pitti> oh, it was uptime 7 mins, I just thought I check whether it's already rebooted; no harm done
[14:43] <jibel> pitti, so that'd mean inotify leak is on the host
[14:43] <pitti> jibel: or perhaps in one of the other containers?
[14:44] <jibel> they were all down
[14:44] <jibel> could be an issue with lxc though
[14:45] <jibel> stgraber, have you ever heard of inotify handles leak with LXC?
[14:46] <jibel> stgraber, I mean you set inotify watch on the guest and they are not freed properly
[14:47] <jibel> pitti, this time it's really up
[14:47] <pitti> thanks
[14:48] <stgraber> jibel: nope but I've seen quite a few machines running out of inotify handles so it wouldn't be completely surprising
[14:48] <jibel> stgraber, do you know a way to track that apart from setting an audit trail on the whole filesystem?
[14:49] <pitti> jibel: so I'm still puzzled why WebKit and realmd don't appear in ~/jhbuild-data/jhbuild.modules, but that sounds like a problem for Monday
[14:51] <jibel> pitti, I don't understand
[14:51] <jibel> $ jhbuild list | grep WebKit
[14:51] <jibel> WebKit
[14:51] <jibel> it should be there, the python script does nothing else than this
[14:52] <jibel> I suspect a bug in my code :)
[15:05] <pitti> jibel: ugh @ jhbuild-data/jhbuild.updates, seems it wants to rebuild the world again
[15:10] <pitti> jibel: ah, but realmd isn't in jhbuild list either, maybe it just fell out of the dependency chain
[15:10] <pitti> jibel: so we'd need to clean up the jenkins job?
[15:10] <pitti> jibel: yep, got removed on November 22
[15:11] <jibel> pitti, ok, I'll add an auto-clean, but removal on the public instance will be manual
[15:29] <balloons> pitti, afternoon to you
[15:29] <pitti> hey balloons, how are you?
[15:29] <smartboyhw> Hey balloons
[15:29] <balloons> I'm pointed out umockdev to some of our autopilot test writers. One is trying to use it to simulate a camera plug/unplug
[15:30] <balloons> having some issues however, so I thought I'd ping you
[15:30] <balloons> sadly she's around after your EOD normally
[15:30] <balloons> hey smartboyhw !
[15:31] <smartboyhw> balloons, I think I should go and merge plars's Nexus7 testcase.... But now we need the Ubuntu Touch ones:P
[15:31] <balloons> smartboyhw, yes I'm trying to merge all the goodies coming on
[15:31] <smartboyhw> balloons, LOL
[15:31] <balloons> for plars, I have to make the new testcase on the tracker too, since it's new
[15:32] <pitti> balloons: yeah, I see the scrollback every morning..
[15:32] <smartboyhw> balloons, add oil
[15:32] <pitti> balloons: maybe email works better; I need to leave in some 15 minutes, too
[15:32] <balloons> pitti, :-) Great, so any thoughts? I can re-summarize. Yes, I figured email questions would serve you best
[15:33] <plars> smartboyhw, balloons: yeah, would be nice to get them in asap, but please make sure they look sane. I'm waiting to get my nexus7 back so I had to work from memory
[15:33] <smartboyhw> plars, OK:)
[15:33] <smartboyhw> balloons, you do merge or I do it?
[15:33] <balloons> but we're trying to write a shotwell ap test -- you think umockdev would be a good fit to help?
[15:33] <pitti> jibel: question, why does /var/log/jhbuild/gnome-shell-extensions.state say "running"? it's not running AFAICS, and the log on https://jenkins.qa.ubuntu.com/job/jhbuild-amd64-gnome-shell-extensions/195/? is complete
[15:33] <plars> smartboyhw: on the subject of ubuntu touch tests - yes, those should be coming pretty soon. I don't think we have daily builds out there yet, so once we do those will become important.
[15:33] <balloons> plars, yes, :-) smartboyhw go ahead and do the merge. I'll do the tracker pieces and merge it to that
[15:33] <pitti> balloons: "ap" == "app" or "access point"?
[15:33] <balloons> ap= autopilot
[15:34] <pitti> balloons: it can record and simulate PtP cameras quite fine, yeah
[15:34] <pitti> balloons: I noticed she tried with the mtp tools, that's most likely not going to work
[15:34] <pitti> most cameras only speak PtP
[15:34] <pitti> so you need "gphoto2", or better, trace shotwell when it's talking to an actual camera
[15:34] <balloons> ok.. i was thinking about justnot using mtp..
[15:34] <balloons> it was having trouble
[15:35] <balloons> so just umockdev record ptp operations instead then?
[15:36] <pitti> balloons: yes; best with the application that you actually want to test (it's mostly record & replay)
[15:36] <pitti> balloons: should work with the gphoto2 tool as well, if you record enough operations (such as retrieving files, etc.)
[15:37] <pitti> but probably easiest to umockdev-record ... shotwell
[15:37] <balloons> pitti, ok, hmm.. I may have to get my feet wet
[15:37] <balloons> ohh nice..
[15:37] <balloons> so literally record shotwell's behavoir
[15:38] <balloons> cool, we'll have to give those things a try and let you know
[15:38] <jibel> pitti, weird, looking at the logs I don't see the reason
[15:38] <pitti> jibel: I guess the "running" state makes it appear as red, but that's probably just a followup issue
[15:40] <smartboyhw> balloons, after you put it in change Bug 1127287 to Fix Committed:)
[15:40] <smartboyhw> plars, the merge is in
[15:41] <pitti> good bye everyone, have a nice weekend!
[15:42]  * balloons waves to pitti
[15:42] <balloons> smartboyhw, plars adding them now
[15:43] <smartboyhw> balloons, :)
[15:44] <smartboyhw> balloons, I like that conversion script:P
[15:46] <balloons> ohh plars btw, https://wiki.ubuntu.com/QATeam/ContributingTestcases/ManualStyleGuide
[15:47] <jibel> pitti, the test was running, jenkins failed to fetch the state file when the container went down. So the check exited with a non-zero exit code
[15:47] <jibel> pitti, and have a nice week end
[15:51] <balloons> so smartboyhw I'm fixing a couple little syntax things in the plars merge.. You need to be on the lookout for such things when you do merges
[15:52] <balloons> things like missing a <dl> tag, or not having the footer on the test
[15:54] <tonyhub> g'morning folks
[15:54] <balloons> morning tonyhub
[15:54] <tonyhub> hi balloons
[15:55] <smartboyhw> balloons, oK. Running the script?
[15:55] <balloons> smartboyhw, yea, I think we should use and expand his tidy script as part of our review
[15:56] <smartboyhw> balloons, agreed
[15:56] <balloons> because we're not always going to remember either :-)
[15:57] <smartboyhw> balloons, :)
[16:14] <balloons> plars http://iso.qa.ubuntu.com/qatracker/milestones/243/builds/38116/testcases
[16:14] <balloons> v
[16:14] <balloons> http://iso.qa.ubuntu.com/qatracker/milestones/243/builds/38116/testcases
[16:15] <plars> balloons: awesome, thanks!
[16:15] <balloons> ty!
[16:15] <balloons> feel free to contribute anytime :-0
[16:50] <komputes> greetings
[16:50] <balloons> hey komputes i'm going through your merges now
[16:50] <komputes> sweet
[16:51] <komputes> I was thinking of another tests, but they are bias because I know they are buggy
[16:51] <balloons> ohh? what's that?
[16:51] <komputes> One is dragging an attachment from an email to the desktop. The other is dragging contacts to a mailing list.
[16:52] <balloons> komputes, i think it's ok to point out things that are broken. sometimes we write a test to confirm a break, and then keep it as a regression watcher ;-0
[16:52] <komputes> Do I include the bug number in the test?
[16:53] <balloons> they have historically done things like that
[16:54] <balloons> since we can update it after it goes away (and in general keep a good watch on things), I don't see that as the worst idea persay
[16:54] <komputes> https://bugs.launchpad.net/thunderbird/+bug/381017 https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/711314
[16:54] <komputes> those are the bugs in question
[16:55] <komputes> balloons: Do you recommend I do a 'bzr update' or 'bzr pull' before making changes?
[16:57] <balloons> yes, doa bzr pull before starting on things
[16:57] <balloons> you want to make sure your changes line up with the newest stuff
[16:58] <balloons> if you don't do that, you'll end up merging them after, which might not be as nice
[16:58] <komputes> it won't overwrite my changes from yesterday if they weren't accepted yet?
[16:58] <balloons> no
[16:58] <komputes> coolio
[16:58] <balloons> if something conflicts, it will tell you
[16:58] <balloons> in which case, there might be an issue.. but if no conflicts, your good
[16:58] <balloons> it won't ever lose stuff tho
[16:58] <balloons> if it conflicts, it will keep both versions
[16:59] <komputes> indeed it did
[16:59] <komputes> bzr: ERROR: These branches have diverged. Use the missing command to see how. Use the merge command to reconcile them.
[16:59] <komputes> now merging
[16:59] <komputes> oooOOoo nexus 7 tests. I want one...
[17:01] <balloons> ;-)
[17:02] <komputes> I did bzr merge but it didn't fix it
[17:02] <balloons> the nexus 7 will run ubuntu (desktop) and ubuntu touch
[17:02] <balloons> and on the desktop, all the autopilot tests will even run
[17:02] <balloons> it's wicked cool
[17:02] <komputes> sweet, need the docking station too then
[17:02] <balloons> komputes, ahh.. welcome to manual merging
[17:02] <balloons> what's the conflict/
[17:02] <balloons> ?
[17:02] <komputes> uncommitted changes
[17:03] <balloons> ohh
[17:03] <balloons> that's simple
[17:03] <balloons> commit what you have
[17:03] <balloons> before you merge
[17:03] <komputes> I want it to show me those changes
[17:03] <balloons> bzr diff
[17:03] <balloons> bzr status
[17:04] <komputes> funny, they are not commits I made, they are the nexus 7 ones
[17:05] <komputes> comitted, pulled, all good
[17:06] <balloons> yes.. if you make changes, but don't commit them
[17:06] <balloons> you can't do any merges
[17:07] <komputes> Aha.
[17:07] <komputes> But still I did not make the changes, I guess they came from the first attempt at pull
[17:13] <balloons> komputes, ok, your branch looks good.. only changes are some minor indenting
[17:14] <komputes> Ok, I'll review the changes and see if I can do that a bit better
[17:15] <balloons> nothing big at all.. did you see javier's script on the mailing list?
[17:15] <balloons> it's a little tidy script that keeps us all in line ;-0
[17:15] <balloons> we'll probably look to adopt that somehow into reviews so we keep everything nicely formatted
[17:22] <balloons> komputes, all merged up
[17:23] <jibel> pitti, I ran the update script manually (no change apart a debug statement) and now WebKit is in the list of modules. Not something for a Friday evening, I'll look into this next week if it vanishes again.
[17:25] <balloons> ok, all pending reviews done ;-) time to sync to the tracker again
[19:49] <balloons> hello Letozaf_
[19:49] <balloons> hey Noskcaj ;-0
[19:49] <Letozaf_> balloons, Hello!
[19:50] <Noskcaj> hey balloons
[19:50] <balloons> Letozaf_, pitti says you can just use shotwell directly in your umockdev commands
[19:50] <balloons> rather than mtp
[19:50] <Letozaf_> balloons, oh! fine, I will try
[19:52] <balloons> komputes, so ldap.utexas.edu is pubnlic eh?
[19:52] <balloons> 8public
[19:52] <balloons> *public
[19:52] <komputes> balloons: do you know one for open source?
[19:52] <komputes> at least you didn't say pubic
[19:53] <balloons> hehe
[19:53] <balloons> komputes, umm.. hmm
[19:55] <komputes> There's a whole list to chose from, too bad we don't have one for Ubuntu members...
[19:56] <balloons> http://ldapwiki.willeke.com/wiki/Public%20LDAP%20Servers
[19:56] <balloons> maybe pick on debian
[19:56] <balloons> db.debian.org
[19:57] <balloons> or a cert provider
[19:58] <balloons> but yea, i guess using a public one works
[19:58] <balloons> to my knowledge, no we don't have a ubuntu one
[20:03] <komputes> balloons: db.debian.org search fail
[20:04] <komputes> I say go with a bigger university with thousands of contac
[20:04] <komputes> chances you'll get a match whatever you search
[20:04] <balloons> ohh
[20:04] <balloons> http://db.debian.org/doc-direct.html
[20:04] <balloons> they locked it down after the compromise
[20:05] <komputes> once i put the DN it works
[20:05] <komputes> you sear for "al" and it gives many results
[20:05] <balloons> good
[20:06] <balloons> yea, works for me too
[20:09] <komputes> balloons: want me to change it and recommit?
[20:10] <balloons> komputes, hmm.. yea, i think poking debian's ldap might be a bit better
[20:10] <komputes> k
[20:10] <balloons> but as you say, any ldap will work
[20:10] <balloons> and there are indeed several
[20:10] <balloons> public ones as you've found
[20:11] <komputes> right, and the Debian server adds the possibly wanted/unwanted configuration of a BASE DN
[20:14] <Letozaf_> balloons, there is a thing that I do not understand, can I ask you ?
[20:17] <balloons> sure
[20:18] <komputes> balloons: is this good? <dt>Give it a name such as "Debian" and a provide the address of a server. If unsure, use the public Debian directory - Name: Debian - Server: db.debian.org - Base DN: dc=debian,dc=org</dt>
[20:18] <komputes> and then i switch the search from bob to al
[20:19] <Letozaf_> balloons, I dumped the sysfs device and udev properties, then I recorded the dynamic behaviour with shotwell, well there isn't much to record, just see the camera attached when I open shotwell, import the photos
[20:19] <Letozaf_> balloons, then when
[20:19] <balloons> komputes, sure, maybe something like: <dt>Give it a name and provide the address of a server. If unsure, try using a public server such as use public Debian directory - Name: Debian - Server: db.debian.org - Base DN: dc=debian,dc=org</dt>
[20:20] <balloons> well, i botched the grammer a little ,but yea
[20:20] <balloons> Letozaf_, k
[20:20] <Letozaf_> balloons, I disconnect the camera and try to run the command using shotwell I see nothing happen, maybe because I did not do much with the camera
[20:21] <Letozaf_> balloons, I mean I would expect to see a mocked camera when shotwell opens
[20:21] <Noskcaj> Letozaf_, would you mind adding yourself to https://wiki.ubuntu.com/QATeam/WhoWeAre
[20:22] <Letozaf_> Noskcaj, sure ik
[20:22] <Letozaf_> Noskcaj, sorry ok
[20:22] <Noskcaj> ty
[20:22] <Letozaf_> Noskcaj, :D
[20:24] <komputes> balloons: done
[20:25] <balloons> Noskcaj, since i have you; https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bugs?field.searchtext=&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&&field.tag=iso-testing&field.tags_combinator=ANY&field.status_upstream-empty-marker=1&field.upstream_target=&field.has_cve.used=&fi
[20:25] <balloons> eld.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search&orderby=-datecreated&start=0
[20:25] <balloons> whoa
[20:25] <balloons> let me try that again that's huge url
[20:25] <Noskcaj> maybe make at bit.ly ?
[20:25] <balloons> http://is.gd/qSVTH7
[20:25] <TheLordOfTime> holy crap balloons... trying to flood us with hugeLinks?  :P
[20:25] <balloons> indeed.. sorry, I didn't realize
[20:26] <balloons> so Noskcaj that's a custom search for unconfirmed bugs found during iso-testing, sorted by date
[20:26] <balloons> newest to oldest
[20:26] <balloons>  looked for anything 'new' or 'incomplete'
[20:29] <Noskcaj> ok, i'm only going to add things from the iso tracker, but others can add whatever to the wiki i'm making
[20:30] <balloons> Noskcaj, that's only things reported via the tracker
[20:30] <balloons> all tracker bugs have the 'iso-tracker' tag on it
[20:30] <Noskcaj> wow
[20:30] <balloons> you can also get a full report on all bugs from the tracker in the reports secton
[20:31] <balloons> http://iso.qa.ubuntu.com/qatracker/reports/defects
[20:31] <Letozaf_> Noskcaj, weired https://wiki.ubuntu.com/QATeam/WhoWeAre doen't like me, cannot logon with Open ID, after logging on I remain on the "You are signing in to http://wiki.ubuntu.com/" page and thats it :(
[20:31] <Noskcaj> ok
[20:31] <balloons> so for instance if you care to see all open bugs reported for the raring dailies: http://iso.qa.ubuntu.com/qatracker/reports/defects/opened
[20:31] <balloons> under 'raring daily'
[20:32] <Letozaf_> Noskcaj, ah! got an error: Internal server error - The server encountered an internal error or misconfiguration and was unable to complete your request.
[20:33] <Noskcaj> https://wiki.ubuntu.com/QATeam/IncompleteBugs is the wiki page i'm partway through making
[20:33] <balloons> Letozaf_, ok so how did it work out with shotwell in the end? pitti says to email him directly with more questions
[20:33] <balloons> he would be best to help of course.
[20:38] <balloons> hopping on http://ubuntuonair.com/
[20:42] <Letozaf_> balloons, well I created the .ioctl file that has the recorded behavior obtained with shotwell in the umockdev command, but there is not much to record, I mean when you open shotwell with the camera attached, you import the photos and then close shotwell and camera, I did this just to try it quickly, but then when you use shotwell with umockdev with the camera disconnected nothing happens, I would expect to
[20:42] <Letozaf_> see a camera detected by shotwell
[20:49] <Noskcaj> https://wiki.ubuntu.com/QATeam/IncompleteBugs now has things on it, please add to it
[20:51]  * balloons goes to look
[20:51] <balloons> Noskcaj, what's the criteria for bugs on this page/
[20:51] <balloons> ?
[20:52] <Noskcaj> balloons, idk, that probably needs working out
[20:52] <balloons> should we try and keep a list of just critical bugs?
[20:52] <balloons> or things we REALLY care about?
[20:53] <Noskcaj> the second one probably, i put in a few at the bottom that need confirming badly too
[20:53] <Noskcaj> phillw, PING
[20:54] <Noskcaj> since phill is away, can someone explain this bug 1131151 , note the window theme
[20:55] <balloons> Noskcaj, ok, update the page with the reasoning for what's listed there. I would encourage you to keep the list short as possible
[20:55] <Noskcaj> ok balloons
[20:55] <balloons> we don't want to make another lp-- consider actually just using a tag and linking things out
[20:56] <balloons> meaning, create a tag on bugs and then make that page a listing of what's been marked and why
[20:56] <balloons> make sense?
[20:57] <Noskcaj> to correct my previous post, is what needs editing http://imgur.com/wVG3AmE
[20:57] <Noskcaj> balloons, yeah
[20:59] <balloons> Noskcaj, ok that's weird
[21:00] <Noskcaj> i agree
[21:00] <balloons> that a xubuntu or lubuntu install?
[21:00] <Noskcaj> lubuntu, that's wh i pinged phillw
[21:00] <balloons> ahh
[21:00] <Noskcaj> the maximise button does nothing too
[21:00] <balloons> so the bug you linked is saying when gnome-setting-dameon isn't running, you don't get a background
[21:00] <Noskcaj> i'm afraid to risk clicking the minimise button
[21:00] <balloons> and probably a few other things not working too
[21:01] <balloons> it's an issue because the flavors might not be running this
[21:01] <Noskcaj> balloons, that bug i linked up the top was the wrong copy/paste, please see the imgur link
[21:01] <balloons> lol
[21:01] <balloons> ok
[21:07] <balloons> hmm.. bzr hates me
[21:08] <Noskcaj> lol
[21:09] <balloons> i couldn't get a good remerge to work
[21:15] <balloons> komputes, all merged up
[21:16] <komputes> balloons: sweet, what else is high priority atm?
[21:16] <komputes> I tried the daily with testdrive, but after the CD Boot screen, I see nothing, just a black screen.
[21:17] <komputes> Those are images from Feb 21
[21:18] <balloons> komputes, ohh?
[21:18] <balloons> I haven't run the daily today
[21:21] <balloons> as far as what else is needed, well, tests for any application you like or enjoy.. or simply expanding the tests for the apps we have
[21:21] <balloons> you can also look at the bugs here; https://bugs.launchpad.net/ubuntu-manual-tests
[21:21] <balloons> this would be helpful; https://bugs.launchpad.net/ubuntu-manual-tests/+bug/774959
[21:22] <balloons> this would be really nice, but you need the hw to help; https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1115502
[21:22]  * komputes is looking
[21:23] <komputes> 1115502 requires someone with access to secure boot hardware, sorry
[21:23] <balloons> yes, it does
[21:23] <balloons> but i had to ask..
[21:23] <komputes> I'll do 774959
[21:24] <komputes> If I have the hardware, I do the other one some other day
[21:26] <balloons> hmm.. this looks straightforward enough; https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1127331
[21:36] <balloons> komputes, so we'll get to try out your thunderbird tests for the cadence week next week ;-0
[21:36] <komputes> o/\o  HIGH FIVE!
[21:38] <komputes> balloons: I saw 1127331, but I was wondering how I could emulate a media device on a VM
[21:38] <balloons> bug 1127331
[21:38] <balloons> depending on your vm, you can share you physical usb ports
[21:47] <balloons> i'm looking over everything for the cadence week
[21:47] <komputes> balloons: Uh, what the "Click on the Install FAMILY icon" - http://iso.qa.ubuntu.com/qatracker/testcases/1300/info
[21:47] <komputes> Whats a family icon?
[21:48] <balloons> komputes, yes.. i added that to the sytle guide ;-0
[21:49] <balloons> it's replace by ubuntu, kubuntu, xubuntu, etc where appropate
[21:49] <balloons> https://wiki.ubuntu.com/QATeam/ContributingTestcases/ManualStyleGuide
[21:49] <komputes> Is the site supposed to replace it with whatever is being tested?
[21:49] <balloons> "When writing your testcase, substitute the word FAMILY in place of ubuntu, kubuntu, xubuntu, etc. The word FAMILY (in caps!) will automatically be replaced with the proper ubuntu flavor according to the testcase context. This is part of keeping your testcase flavor agnostic. "
[21:49] <balloons> yes exactly
[21:50] <komputes> But it's not atm, right
[21:50] <balloons> it will sub in properly depending on the product being tested
[21:50] <balloons> what do you mean?
[21:50] <komputes> Check it http://iso.qa.ubuntu.com/qatracker/testcases/1300/info
[21:50] <balloons> ohh, yes under info it will still show family
[21:50] <balloons> it's a straight print of the text
[21:50] <komputes> so where would it be shown correctly?
[21:51] <balloons> http://iso.qa.ubuntu.com/qatracker/milestones/243/builds/38121/testcases/1300/results
[21:51] <balloons> http://iso.qa.ubuntu.com/qatracker/milestones/243/builds/38079/testcases/1300/results
[21:51] <balloons> that's using the same testcase
[21:51] <balloons> the one you linked. under lubuntu and kubuntu
[21:51] <balloons> see how it reads?
[21:52] <komputes> still says Family
[21:52] <balloons> ?
[21:52] <balloons> lol.. really?
[21:52] <balloons> it shows properly for me
[21:52] <komputes> Oh Testcase is colapasble
[21:52] <balloons> yes
[21:52] <balloons> zomg
[21:52] <komputes> I've been doing it wrong this entire time
[21:52] <balloons> ohhhh
[21:52] <komputes> ZOMG WEBSITE FAIL
[21:52] <balloons> no worries
[21:52] <komputes> SO MANY B00GS
[21:52] <balloons> yea, it's collapsed by default too
[21:53] <balloons> that was a decision intentionally made
[21:53] <balloons> because you also review results on the submission page
[21:53] <komputes> Looks like a section seperator
[21:53] <balloons> kind of how it works out
[21:53] <komputes> ok nm then
[22:18] <balloons> komputes, weird.. look at this gedit test; http://packages.qa.ubuntu.com/qatracker/milestones/258/builds/38183/testcases/1420/results
[22:19] <balloons> 	<dt> Type in “<a href="http://www.ubuntu.com">Link To Ubuntu</a>”</dt> needs the quotes dropped :-)
[22:19] <komputes> balloons: yes, I can try to use escape chars to fix that
[22:20] <komputes> or hex codes i mean
[22:21] <balloons> ohh
[22:21] <balloons> man it appears other places too
[22:21] <balloons>  Type in âThe quick brown foxes jump over the lazy dogâ
[22:22] <balloons> I think it's the character "
[22:22] <balloons> well it's ”
[22:22] <balloons> not "
[22:22] <balloons> and ’ not '
[22:22] <balloons> make sense/
[22:22] <balloons> ?
[22:23] <balloons> i'm still working on setting up the cadence week.. I think a simple s//g will fix it if you want to propose a merge?
[22:23] <balloons> if not I'll have at it
[22:34] <komputes> balloons: Yeah, if you can do it quickly go for it.
[22:34] <balloons> komputes, I just did.. I was just typing to you
[22:34] <balloons> :-) just finished up
[22:34] <komputes> finishing up the Install (live session) testcase
[22:35] <komputes> Testcase format script is broken
[22:35] <komputes> I have  vim-tiny and tidy
[22:35] <komputes> ./TestCaseFormat ubuntu-manual-tests/testcases/image/Install\ \(live\ session\)
[22:35] <komputes> ./TestCaseFormat: You need vim & tidy to run this script
[22:36] <balloons> komputes, actually how can I force the html to not be interperted?
[22:36] <komputes> hex codes
[22:36] <balloons> even in drupal.. hmm
[22:37] <balloons> http://packages.qa.ubuntu.com/qatracker/milestones/258/builds/38183/testcases/1420/results
[22:37] <komputes> balloons: http://code.cside.com/3rdpage/us/url/converter.html
[22:37] <balloons> lol I failed
[22:38] <komputes> otherwise it's interpreted as html
[22:38] <komputes> because it is in fact html
[22:38] <SergioMeneses> hi all!
[22:38] <komputes> ola SergioMeneses
[22:39] <balloons> komputers, I've pretty much just failed
[22:39] <SergioMeneses> komputes, balloons \o
[22:40] <balloons> one more try
[22:40] <balloons> Type in %3Ca href="http://www.ubuntu.com"%3ELink To Ubuntu%3a/a%3E
[22:40] <balloons> no dice
[22:42] <komputes> balloons: did you try the url converter I sent you the link to?
[22:43] <balloons> I did
[22:43] <balloons> I tried this as well; http://ascii.cl/htmlcodes.htm
[22:43] <balloons> ohh bother
[22:44] <balloons> woot
[22:45] <balloons> http://packages.qa.ubuntu.com/qatracker/milestones/258/builds/38183/testcases/1420/results
[22:50] <balloons> thanks komputes
[22:50] <balloons> I was missing the semicolons
[22:52] <komputes> what does <pre> do?
[22:53] <balloons> makes that little box
[22:53] <komputes> ah
[22:53] <balloons> pre=preformatted
[22:53] <balloons> I decided I wanted to add a box to avoid using the quoes
[22:53] <balloons> since it was important to get it right in that case
[22:54] <komputes> balloons: cool well, submitted the merge request, let me know if I can close out Bug #774959
[22:55] <balloons> komputes, ahh.. I saw, let me look
[22:56] <komputes> hi chilicuil
[22:57] <chilicuil> hi komputes o/
[22:58] <komputes> chilicuil: did you write the formatting script?
[22:58] <komputes> https://wiki.ubuntu.com/QATeam/ContributingTestcases/ManualStyleGuide/test_case_format_script
[22:58] <balloons> chilicuil, thanks updating the wiki too
[22:58] <balloons> :-)
[22:59] <balloons> komputes, while messing with gedit i noticed this too: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1131961
[22:59] <balloons> might be a problem on other legacy testcases.. something to look out for
[23:00] <balloons> komputes, so this looks good.. Can you fix the formatting tho
[23:00] <balloons> I see 2 little mistakes
Allow the machine to reboot</dt> line is indented to much, and there's no default footer
[23:01] <chilicuil> komputes: yep, balloons np =)
[23:03] <komputes> balloons: chilicuil: The script does not work for me. I have  vim-tiny and tidy
[23:03] <komputes> $ ./TestCaseFormat ubuntu-manual-tests/testcases/image/Install\ \(live\ session\)
[23:03] <komputes> $ ./TestCaseFormat: You need vim & tidy to run this script
[23:05] <chilicuil> komputes: I thought vim-tiny will be enough.., however I've the full featured vim, try installing vim-gtk and then retry running the script
[23:05] <SergioMeneses> it is a script for vim, right?
[23:06] <balloons> ok, dinner time for me.. l'll keep merging your requests, and anything you get in this weekend/early next week we could probably sneak into the cadence week :-)
[23:06] <chilicuil> balloons: bom apetite
[23:06] <balloons> I'll be offline most of next week, but i'll still get emails.. Thanks for your efforts.. should be a fun week for testing
[23:06] <chilicuil> SergioMeneses: yep
[23:06] <SergioMeneses> balloons, :)
[23:06] <balloons> night SergioMeneses, chilicuil, komputes
[23:07] <SergioMeneses> balloons, see you!
[23:07] <komputes> see you later balloons
[23:08] <komputes> balloons: formatting fixed
[23:08] <balloons> komputes, lol.. I just left feedback on the merge
[23:08] <balloons> ok, I'll check and merge before I run
[23:11] <komputes> balloons: http://bazaar.launchpad.net/~komputes/ubuntu-manual-tests/komputes-manual-tests/revision/24
[23:11] <komputes> can't request a merge since one is still pending
[23:11] <balloons> just merged on my box
[23:11] <balloons> https://code.launchpad.net/~komputes/ubuntu-manual-tests/komputes-manual-tests/+merge/150161
[23:11] <balloons> the merge updates, see?
[23:11] <balloons> so your good.
[23:11] <balloons> as you make changes and push them, it will track until it's in
[23:15] <balloons> merged
[23:16] <balloons> http://iso.qa.ubuntu.com/qatracker/testcases/1497/info
[23:16] <balloons> feel free to close the bug
[23:17] <balloons> ty komputes.. i'm off
[23:17] <komputes> ciao
[23:29] <SergioMeneses> komputes, http://packages.qa.ubuntu.com/qatracker/testcases/1496/info
[23:29] <SergioMeneses> :)
[23:30] <komputes> SergioMeneses: It was fun to do!
[23:31] <SergioMeneses> sure!
[23:41] <SergioMeneses> balloons, around?
[23:42] <SergioMeneses> mmm.... I've read the log