/srv/irclogs.ubuntu.com/2012/12/13/#ubuntu-quality.txt

=== JasonO- is now known as JasonO
=== Ursinha is now known as Ursinha-afk
pittiGood morning06:39
pittitest hacking day!06:39
pittihttps://lists.ubuntu.com/archives/ubuntu-devel-announce/2012-December/000999.html07:01
elfymorning pitti07:05
pittihey elfy07:07
jibelgood morning!07:40
pittibonjour jibel07:40
jibelguten Morgen pitti07:42
jibelready to hack?07:42
pittioui, je suis!07:42
jibelgreat!07:43
jibelSo, I did a little count this morning07:43
jibelI checked https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/07:43
jibeland there are 63 packages with tests and 11 of them are failing07:44
jibellet see how much we can add or fix in a day07:44
pittiI want to work on some failing ones today07:44
pittiand I'm happy to review/test/sponsor contributor tests07:44
jibelpitti, which failing package will you start with?07:47
jibelI can give a try at update-manager07:47
jibelhttps://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job/raring-adt-update-manager07:48
jibelfrom the log there is only 1 failing test, looks like a low hanging fruit07:48
jibelhttps://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job/raring-adt-update-manager/44/ARCH=i386,label=adt/artifact/results/dsc0t-nose-tests-stdout07:48
jibelperfect for me :)07:48
jibelI'll file a bug first for this failure07:50
pittijibel: it's not quite that simple, I'm afraid; it fails with two different missing packages on i386/amd6407:50
pittibut it might still be simple after all, I haven't looked into it yet07:50
jibelpitti, right, never underestimate mvo's code ;)07:51
jibelI filed bug 108979307:57
ubot5Launchpad bug 1089793 in update-manager (Ubuntu) "testOriginMatcherWithVersionInUpdatesAndSecurity failed withAssertionError: None == None : no package 'ecryptfs-utils' installed " [Undecided,New] https://launchpad.net/bugs/108979307:57
jibelso now, I'll prepare a fresh testing environment with prepare-testbed from lp:auto-package-testing07:59
jibel$ ./bin/prepare-testbed amd6407:59
dholbachgood morning08:03
pittihallo dholbach08:03
dholbachhappy automated testing day!08:03
pittihappy hacking day! /me gets his axe08:03
dholbach:-)08:03
jibelHey dholbach08:04
dholbachpitti, jibel: at 9 UTC I'm going to interview didrocks for the ubuntudev hangout when do you think we should do a automated testing hangout?08:04
pittiI can do a hangout for about 1 minute08:05
pittithen google mutes me08:05
jibeldholbach, anytime is good08:05
dholbachpitti, wow08:05
jibelpitti, did you try the nexus with android08:05
jibel?08:05
dholbachis that on raring? :-(08:05
dholbachthat sucks08:05
pittiyes, on raring; not sure whether that matters08:05
pittijibel: I guess I could kill raring on the nexus and install android, yes08:06
jibelwe did hangout with didrocks for hours08:06
dholbachit was similar when I interviewed Laney - but it wasn't after 1 minute, but 3 times in a 1h hangout08:06
jibelI also must set g+ hangout preferences to low bandwidth despite I have a 100Mbps connection08:07
pittidid anyone try killing pulse before, or something like that?08:12
pittiI'm going to look at the eternal udisks2 hang08:18
dholbachmaybe somebody else could later on demo a few things?08:19
dholbachit might be good to have a bit of a schedule and if we could do something in the European start of the day and maybe something in the US start of the day08:20
pittijibel: I updated https://wiki.ubuntu.com/QATeam/RequiredTests to grab udisks2, and noted you down for update-manager08:21
jibelpitti, ack08:23
jibelso it's interesting, adt-run fails when running update-manager tests from the source tree when it runs dh_auto_build08:23
jibelit uses the wrong version of python, despite the override in the rules file08:24
pittierr, not amused; running the udisks Luks tests causes a kernel oops08:34
jibelah, that explains the test hangs forever08:37
pittiI'll check if it also happens in kvm08:37
jtayloris there a time limit on how long autopkgtests can run?08:41
jtaylore.g. is 8 hours too much?08:41
pittiI'd say yes; there is only so much capacity we have in teh DC08:41
jtaylorthere should probably be a restriction specifier for slow tests?08:41
jtaylorso that one can run those less often08:42
jtaylorin dep808:42
pittiautopkgtest defaults to a timeout of 2.7 h (10.000 s) for tests08:42
pittithat does not include the build though, if you have a test with build-needed08:43
pittijtaylor: well, we can't run them less often -- they need to run on each package and dependency upload, otherwise they wouldn't do what we want them to do (prevent regressions from landing in ubuntu)08:46
pittijtaylor: perhaps you can disable some very expensive tests for dep8, and then they can run manually every now and then?08:47
jtaylorcouldn't you run the fast tests on every change and the slow test once a week if there was a change?08:48
pittiwe don't have that kind of smarts ATM08:48
jtayloror at certain milestone points08:48
jtaylorjenkins can do that easily08:48
pittiwel, not in ADT; we can run them as a different kind of test08:49
pittiright08:49
dkesselgood morning08:52
dkesseli want to help with the simple compile/link/run tests08:52
dkesseli'm starting at the top of the list, libatk-dev08:57
pittidkessel: great!08:57
jibelpitti, dholbach and all, I created http://pad.ubuntu.com/testing-hackfest-20121213 to keep track of our progress09:00
pittiah, so we won't use the wiki page?09:02
jibelit's more dynamic and easier to use for the day, then we'll update the wiki page for history09:05
pittiack09:06
jibelmvo, about bug 1089808, I can just remove the dh_auto_build call from the override in debian/rules, right?09:08
ubot5Launchpad bug 1089808 in update-manager (Ubuntu) "debian/rules build failed with ImportError: No module named DistUtilsExtra.command" [Undecided,New] https://launchpad.net/bugs/108980809:08
mvojibel: let me check09:14
mvojibel: yeah, that should be ok09:15
dkesseli am trying to follow the steps on http://developer.ubuntu.com/packaging/html/auto-pkg-test.html09:16
dkesselif i run09:17
dkesselbzr branch ubuntu:libatk1.0-dev09:17
mvojibel: are you on it or should I just do it and upload?09:17
dkesseli get: ERROR: no branch: »bzr+ssh://bazaar.launchpad.net/+branch/ubuntu/libatk1.0-dev/09:18
jibelmvo, I was about to do it, but go for it09:21
jibeldkessel, I think it's bzr branch ubuntu:atk1.009:23
jibeldkessel, atk1.0 is the source package for libatk1.0-dev09:24
dkesseloh, right09:24
jibelaccording to apt-cache showsrc libatk1.0-dev09:24
dkesselthx09:24
* dkessel takes notes on new commands :)09:25
jibelmvo, I'm on bug 1089793, you can save an upload if you wait a bit.09:27
ubot5Launchpad bug 1089793 in update-manager (Ubuntu) "testOriginMatcherWithVersionInUpdatesAndSecurity failed withAssertionError: None == None : no package 'ecryptfs-utils' installed " [Undecided,New] https://launchpad.net/bugs/108979309:27
mvojibel: sure, I will just commit09:27
mvojibel: and wait for your ack09:27
mvojibel: so just to double check, its calling py2 even when run with --with=python3?09:29
jibelmvo, yes09:29
mvojibel: ok, commited09:29
jibelmvo, we had a similar issue last week with unity and fixed it with the same override http://bazaar.launchpad.net/~online-accounts/unity-scope-gdrive/trunk/view/head:/debian/rules09:31
jibelmvo, does apt always re-reads dpkg-status when Cache.open() is called?09:57
jibelmvo, I'm on test_update_origin.py in update-manager09:57
jibelthis test testOriginMatcherWithVersionInUpdatesAndSecurity09:57
jibelthese lines (105-122) http://paste.ubuntu.com/1429365/09:57
jibeland pkg._pkg.current_ver is always None, despite the record is set to 'installed' in dpkg status09:58
mvojibel: it should be09:59
* mvo scratches head09:59
dholbachjibel, awesome10:05
dholbachpitti, didrocks used his tablet for the hangout as well :)10:09
didrockswell, the sound is cutting down on my laptop machine after a minute in a hangout for some unknown reason, so yeah, have to use a tablet :)10:10
pittiyeah, same for me10:10
didrocksweird that not everyone is impacted10:10
dholbachdidrocks, laney had a similar problem on tuesday, but it wasn't after a minute - "just" 3 times in an one hour hangout10:12
didrocks20 minutes in a average is 20 times better! :-)10:12
didrocksquite reliably under a minute here :/10:12
didrockss/in a/on a/10:12
dholbachI'm not impacted as I'm still on quantal on my laptop :)10:13
dholbachI know, cheating, I know :-P10:13
didrocksdholbach: and you tell that without being ashamed of it? :-)10:13
didrocksI see, I see ;)10:13
dholbachI use raring elsewhere :)10:13
didrocksheh10:13
jibelmvo, I did the following test http://paste.ubuntu.com/1429399/  and current_ver is always None, any idea?10:24
mvojibel: give me some minutes, I should have this ready in a bit10:29
mvojibel: eh, I mean, I should be able to look in a bit, just need to finish a mail10:29
smartboyhwHi guys: Automated testing hacking right?10:31
pittihello smartboyhw; yes10:32
smartboyhwpitti, OK so what can I hack?10:32
pittismartboyhw: if you want to start with something small, I guess adding a compile/link/run autopkgtest to a library is a good start10:33
pittismartboyhw: see https://wiki.ubuntu.com/QATeam/RequiredTests for a list of library packages that need one10:33
smartboyhwpitti, OK10:33
pittilet me remove the ones which got tests in the meantime10:33
pittiok, done10:36
pittiI dropped the libs which have tests from https://wiki.ubuntu.com/QATeam/RequiredTests and removed stale locks10:36
mvojibel: hm, could that be that there is simply the "Architecture:" missing? that is fixed in current trunk10:36
pittidkessel: so you are working on libatk, right?10:37
pittidkessel, smartboyhw: if you "grab" a package, please note so on http://pad.ubuntu.com/testing-hackfest-20121213, so that we avoid overlapping10:37
mvojibel: I think thats it, I can upload and it should be green again, the fix is in trunk but not uploaded10:38
jibelmvo, that's it10:39
dkesselpitti: yes, libatk10:39
* jibel hugs mvo10:39
mvojibel: cool, I will upload then10:39
dkesselpitti: i tried, but i can't access it - "Either you have not been granted access to this resource or your entitlement has timed out. Please try again."10:39
* mvo hugs jibel back :)10:39
pittidkessel: ah, odd; anyway, I'll add a note for you10:40
pittidkessel: this should work though standard SSO10:40
pittijibel: edit wars!10:41
dkesselpitti: not for me - tried logging out and in again... don't have any problems accessing e.g. launchpad...10:41
* mvo hugs jibel again, just because10:42
dkesseli get an exception in adt-run when running my test with it: http://pastebin.com/DewiGnWd10:44
pittiit's trying to call /usr/lib/pbuilder/pbuilder-satisfydepends-classic10:45
pittidkessel: please sudo apt-get install pbuilder10:45
pittiit's recommended by autopkgtest, apparently you disabled recommends in apt?10:46
didrockspitti: oh, you're using -classic as well? I have to use that for using some options that are display in --help by unimplemented in other flavors10:46
pittididrocks: it's what autopkgtest calls10:47
didrocksok, so we are aligned on that at least :)10:47
* pitti uploads an udisks2 which should avoid the kernel crash and succeed again10:49
didrockspitti: hum, nice crash. I was telling: this is what I use in my cowbuilder to prepare the source package, but as the other build-deps or maybe not available, I'm doing it with --force-version and --continue-fail10:51
pittiI looked ath the software-center failures a while ago, and it seems there's a gazillion different failures; both due to real bugs, and also some because of the test environment10:51
pittimvo: ^ does it make sense to fix those, or will s-c be obsoleted by the unity dash soon anyway?10:51
dkesselpitti: apt-cache show autopkgtest says "Recommends: apt-utils" for me... not pbuilder. this is on precise...10:52
mvopitti: it will be obsoleted, but I guess its still worth exploring, let me create a VM for it - raring I assume?10:53
pittimvo: right10:53
* mvo run ./bin/prepare-testbed10:53
pittimvo: but I figure you can reproduce most of the failures by simply calling debian/tests/whatever locally10:53
pittidkessel: ooh10:53
pittidkessel: I'm afraid autopkgtest is fairly buggy on precise still10:53
pittidkessel: so you might want to run prepare-testbed and run the full test in kvm10:54
mvopitti: interessting, its doing ok for me, the testsuite is run before each upload but maybe my box is the only system :/10:54
pittidkessel: and for the first test you can just call debian/tests/yourtestname and ensure that succeeds, doesn't print out anything on stderr, and exits with 010:54
pittimvo: in fact, it seems the recent runs fail even before that10:55
pittimvo: a while ago the tests actually ran, with two dozen errors10:55
pittinow it just says "please run sudo update-apt-xapian-index", and then aborts10:55
smartboyhwpitti, I might try libatk1.0-dev10:56
pittismartboyhw: dkessel is working on that one10:57
pittismartboyhw: see http://pad.ubuntu.com/testing-hackfest-2012121310:57
smartboyhwpitti, ok let me choose another one10:57
pittismartboyhw: gdk-pixbuf perhaps, or pango?10:57
pittihang on, pango ought to have one already10:58
pittiah, it's missing an XS-Testsuite: header; I'll fix that10:58
smartboyhwpitti, uh is there anyone who are working on libarchive-dev?10:58
pittismartboyhw: we have one already, see https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/10:58
* pitti updates wiki page10:59
smartboyhwpitti, please update:(10:59
pittidone10:59
dkesselpitti: i have run the test already and verified the results. now i am stuck on how to run my local branch on the testbed10:59
pittidkessel: did you run "prepare-testbed -r raring" already?11:00
dkesseldo i just have to run that from the package source directory?11:01
jibeldkessel, no, first branch the project auto-package-testing: bzr branch lp:auto-package-testing11:02
dkesselpitti: ^11:02
jibeldkessel, then cd auto-package-testing11:02
jibeldkessel, and prepare a test environment with:11:02
smartboyhwpitti, well then: How about libsecret-1-dev?11:02
dkesseljibel: ok, i did the preparation steps yesterday11:02
pittismartboyhw: sounds good! I'll make a note in the pad11:03
smartboyhwpitti, :)11:03
jibeldkessel, ok, did you upload a branch with your tests on bzr or its on your local disk?11:04
dkesseljibel: i have done the preparation, but how do i run my test for libatk on it?11:05
dkesseloh. on my local disk11:05
pittidkessel: push it to LP under e. g. lp:~dkessel/ubuntu/raring/atk1.0/autopkgtest11:09
pittidkessel: and then you can call run-adt-test -r raring -b lp:~dkessel/ubuntu/raring/atk1.0/autopkgtest11:10
pittidkessel: sorry, run it like that to avoid building the package again:11:10
pittirun-adt-test -r raring -b lp:~dkessel/ubuntu/raring/atk1.0/autopkgtest atk1.011:10
pitti(this is all in the documentation, btw)11:10
jibeldkessel, or you can start the VM with: ./bin/run-adt-test -kl11:11
jibelthis will start the test env and log you in11:12
jibelthen copy your files from your local drive11:12
jibelwe should definitely add an option to copy local tests or use any VCS11:13
pittiyeah, that'd be convenient11:13
dkesselpitti: ./bin/run-adt-test -r raring -b lp:~dkessel/ubuntu/raring/atk1.0/autopkgtest atk1.0 fails with: ./bin/run-adt-test: 2: /home/daniel/workspace/auto-package-testing/bin/../etc/config: distro-info: not found11:18
pittidkessel: ah, please instaoo the "distro-info" package11:19
pitti"install"11:19
jibeldkessel, it is documented here http://bazaar.launchpad.net/~auto-package-testing-dev/auto-package-testing/trunk/view/head:/doc/USAGE.md11:20
=== _salem is now known as salem_
dkesseljibel: thanks. i read http://developer.ubuntu.com/packaging/html/auto-pkg-test.html and that is missing distro-info11:23
dkesseljibel: if run-adt-test just outputs "2012-12-13 12:24:06: Info: Cleaning up " - does that mean the test has completed without errors?11:24
pitticheck "echo $?", it should be 011:25
jibeldkessel, if it's all you got from the run it's suspicious11:25
pittierr yes, it should certainly output two screenfuls of pages before that11:25
jibeldkessel, what's the full output, and yeah return status as pitti said11:25
dkesseljibel, pitti: that is the full output....11:26
jibeldkessel, can you run again with -d and paste the output11:27
jibel?11:27
dkesselapperently, it tries to load the image from /tmp. well - i rebooted since yesterday ;) ok, i rerun the prepare step.... but maybe it should fail with an error if it does not find the image ;)11:29
jibeldkessel, right, could you file a bug against https://bugs.launchpad.net/auto-package-testing please ?11:30
jibelyou can change the location of the image cache in the config file.11:31
smartboyhwpitti, a question: Would it be easier for me to use the tests available originally in libsecret?11:35
jibelmvo, should apt-clone testsuite run as root or normal user?11:35
pittismartboyhw: if you can convince the upstream tests to run against the installed library instaed of the ones in the source tree, that's ideal of course11:36
pittismartboyhw: but that is orthogonal to adding a compile/link/run test, so you might want to do both (one debian/tests/upstream and a debian/tests/compile)11:36
smartboyhwpitti, ok11:37
pittismartboyhw: but as long as the upstream tests run during the package build, they are not really that important to be run again in autopkgtest11:37
pittiit cannot hurt of course, so if you can make it work easily, please do :)11:37
dkesseljibel: i filed bug 108988511:47
ubot5Launchpad bug 1089885 in Auto Package Testing "run-adt-test silently fails when test image is missing" [Undecided,New] https://launchpad.net/bugs/108988511:47
jibeldkessel, thanks11:48
smartboyhwpitti, sorry for asking (quite stupid): So in http://people.gnome.org/~stefw/libsecret-docs/c-examples.html#c-schema-example it says I need to have a header..... so I need to create another header right?11:48
jibelupdate-manager is green again \o/11:48
pittismartboyhw: no, I don't think you'll need that for a simple compile test; this isn't installed anywhere11:52
smartboyhwpitti, then I need my OWN schema......11:52
* smartboyhw does not know how to do it....Beginner C guy here 11:52
* jibel -> lunch11:56
pittijibel: enjoy! I guess you won't need the intro session :)11:57
pittidholbach: ok, I have an intro prepped11:57
pittijibel: udisks is green again, too!11:59
pitti♩ another one bites the dust ♫ ♬11:59
pittigrabbing u-d-common next11:59
dkesselpitti: libakt's debian/control said i should edit debian/control.in instead... so i did that - now run-adt test fails with: "no such directory: ./debian/control"11:59
pittidkessel: that's right, you need to edit debian/control.in and then run "debclean"12:00
pittidkessel: hm, does debian/control exist?12:00
dkesselpitti: ... and then commit and push again i guess12:00
pittiright12:00
pittibut ensure that the XS- header is in debian/control as well; debclean should do that, and then you should see it in bzr diff12:01
pittiATTENTION PLEASE12:01
pittiI prepared a short intro about today's hackfest; for those who know about autopkgtest or are already knee-deep in it this won't be of much use, but if we have any newcomers here I'll do it now as dholbach announced in his blog12:02
pittiso can you please wave if you are here for the hackfest?12:02
* dkessel (needlessly) waves :)12:04
* pitti hugs dkessel12:04
pittismartboyhw as well, but he's also already working on a test12:04
pittiok, so let's cut this short12:05
pittidkessel, smartboyhw: I just want to ensure that you have all the links12:06
pittithis document describes all the details about how to create and run tests, including a detailled example of a compile/link/run library test:12:06
pittihttp://developer.ubuntu.com/packaging/html/auto-pkg-test.html12:06
pittiIf you create a test, I suggest that for the first iterations you just run the debian/tests/yourtestname script on your local machine until that succeeds. Once it does, you need to run the test in a virtual machine, to ensure that it also works in that environment and you specified all necessary test dependencies.12:06
pittiIf you start working on a package, please add a note to our coordination pad, to avoid stepping on each other's toes:12:06
pitti  http://pad.ubuntu.com/testing-hackfest-2012121312:06
pittiand finally, you can see the current tests and their status here:12:07
pitti  https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/12:07
pitti*tock tock*, is this thing on?12:09
dkesselyup12:09
dkesselsmartboyhw - can you access http://pad.ubuntu.com/testing-hackfest-20121213 ?12:10
dkesselbecaus i can't12:10
mvojibel: \o/12:13
* dkessel waits.... and waits...12:16
dkesselhow can i stop the test image from upgrading the kernel each time it starts?12:16
pittithere's no switch for that, I'm afraid12:17
pittiit's an unfortunate day, it seems we didn't get fresh cloud images today12:17
smartboyhwdkessel, hmm i can:P12:21
dkesselpitti: :( hm, i did debclean, commit and push - and it still complains about missing "debian/control" when i run: ./bin/run-adt-test -r raring -b lp:~dkessel/ubuntu/raring/atk1.0/autopkgtest12:22
pittidkessel: right, so do you have a debian/control ?12:24
pitti(in your source package branch)12:24
pittidkessel: what's the branch you pushed this to?12:25
pittiI'll have a look on LP12:25
pittioh, got it, https://code.launchpad.net/~d-kessel/ubuntu/raring/atk1.0/autopkgtest12:25
pittiok, the file is there12:26
* pitti runs it himself12:26
smartboyhwpitti, hmm is there more easier packages to work with autopkgtest? I found this one quite hard, if I were to test it's functions12:26
pittismartboyhw: poppler-dev should be more straightforward; you need to add a test dependency to a packge that ships a PDF, and can then try to open that with libpoppler, and check a few basic properties with it12:28
smartboyhwpitti, OK12:28
pittismartboyhw: that should provide quite a nice smoketest, and poppler doesn't have the kind of complicated callback API that libsecret has12:28
pittismartboyhw: but even with libsecret, note that you don't need to do anything complicated12:29
pittismartboyhw: any simple library call will do, which proves that you can compile against the library12:29
pittidkessel: I get12:29
pittichmod: cannot access ‘/tmp/tmp.eVTEXdaDCI/ubtree0-ubtree/debian/tests/build’: No such file or directory12:30
pittiadt-run: unexpected error: failed to chmod +x /tmp/tmp.eVTEXdaDCI/ubtree0-ubtree/debian/tests/build12:30
pittidkessel: which is because your debian/tests/control says "Tests: build"12:30
pittidkessel: but you named your script debian/tests/atk1.0-dev_test12:30
dkesselaaaah so thats that that line means....12:30
dkessel:)12:30
pittismartboyhw: poppler-dev should be more straightforward; you need to add a test dependency to a packge that ships a PDF, and can then try to open that with libpoppler, and check a few basic properties with itdebian/tests/atk1.0-dev_test debian/tests/build"12:30
pittierk, what was that12:30
smartboyhwpitti, yes I get it...12:30
pittismartboyhw: sorry, weechat failure12:31
dkesselpitti: i still wonder why you get a different error message12:31
pittidkessel: so I suggest to do bzr mv debian/tests/atk1.0-dev_test debian/tests/build12:31
pittidkessel: as this is the atk1.0 package, there is no doubt which package you are testing :)12:31
pittidkessel: yeah :( I'm on raring, you are on precise; as I said autopkgtest on precise still has a number of bugs, that might be the problem12:32
pittidkessel: perhaps you can try "wget http://archive.ubuntu.com/ubuntu/pool/main/a/autopkgtest/autopkgtest_2.2.3ubuntu1_all.deb"12:32
pittidkessel: and then "sudo dpkg -i autopkgtest_2.2.3ubuntu1_all.deb"12:32
pittidkessel: the current versino should work just fine on precise12:33
pittidkessel: ah no, I'm talking gibberish, sorry12:33
pittidkessel: if you created a raring VM, it'll use autopkgtest in that VM, not locally12:33
* dkessel running kernel upgrade :)12:34
smartboyhwpitti, ok i will change my focus to poppler-dev now12:35
dkesselpitti: can you try running it again? i fixed the file name and it still fails with "missing debian/control" here...12:36
pittidkessel: sure! running12:37
mvosilly question - I have my testbed now but how do I log into it to try to figure out how to fix the tests in a more interactive way12:37
pittimvo: what I usually do is "run-adt-test -sk ..."12:37
pittimvo: that will install all the deps, run the tests, and then keep the VM running, and print an ssh command to log into it12:38
mvoaha, nice12:38
=== Ursinha-afk is now known as Ursinha
pittimvo: or "run-adt-test -sl" and then do the apt-get source, install deps etc. yourself12:38
pittimvo: (-s is just for speed if you have lots of RAM; -k vs. -l is the important bit here)12:38
=== yofel_ is now known as yofel
pittibut -s rocks; it's great to see 200 MB of dependencies getting unpacked and configured in like 3 seconds12:39
smartboyhwpitti, the sad thing is: I can't seem to think of any packages that includes a PDF file in mind:P12:39
mvosweet12:39
pittidkessel: Fortschritt! http://paste.ubuntu.com/1429597/12:39
pittismartboyhw: grep '\.pdf' /var/lib/dpkg/info/*.list12:40
dkesselpitti: i guess i have to get interactive too...12:41
pittidkessel: so cups-filter's /usr/share/cups/data/default-testpage.pdf should do12:41
pittidkessel: your debian/tests/control depends on libglib2.0-dev, but you want libatk1.0-dev :)12:42
pitticopy & paste FTW12:42
smartboyhwpitti, hmm the poppler website is very short of documentation:P12:42
pittidkessel: you did create a raring VM, not a precise one, right?12:42
dkesseloopsie12:43
dkesselpitti: yes, a raring vm12:43
pittismartboyhw: file:///usr/share/doc/libpoppler-glib-dev/html/poppler/PopplerDocument.html#poppler-document-new-from-file12:44
pittismartboyhw: this looks quite reasonable12:44
pittismartboyhw: i. e. one call to load a file and get a PopplerDocument12:45
pittismartboyhw: then maybe check file:///usr/share/doc/libpoppler-glib-dev/html/poppler/PopplerDocument.html#poppler-document-get-n-pages for the expected number of pages12:45
smartboyhwpitti, OK12:45
pittismartboyhw: and that should actually be enough for a c/l/r test12:46
smartboyhwpitti, OK12:46
pittismartboyhw: then add a dependency to cups-filters for /usr/share/cups/data/default-testpage.pdf, and there you go :)12:46
smartboyhw:)12:46
mvopitti: the tests are running now, I keep you updated12:49
pittijibel: hm, right now jenkins runs udisks amd64 three times in parallel; comment est-ce possible?12:49
pittimvo: you got beyond the "run xapian-update" thingy?12:50
jibelpitti, ce n'est pas possible, it's a UI bug12:50
dkesselpitti: it should work now - but i can't verify because of the error in the VM...12:50
* pitti turns the crank on dkessel's branch12:50
dkessel*sigh*12:51
jibelit uses a blinking ball for all the jobs with the same name in the latest builds panel12:51
pittijibel: yes, but I see it on three different slaves on the left side12:51
pittialderamin, aldebaran, and wazn12:52
pittidkessel: Bazinga!12:52
pittidkessel: thank you for having shopped at Ubuntu QA Labs Inc. Please collect your free beer at the counter now!12:53
pittidkessel: so I'll merge and upload this, and commit it to Debian too12:53
jibelpitti, on the left side, there is 1 for amd64, 1 for i386 and a virtual job with a role of controller for jenkins internal mechanics and which will consolidate the results of all the architectures12:53
dkesselpitti: yay! thanks for the help - I'll have lunch before the beer though :)12:55
jibelI restarted udisk because of this hashsum mismatch error again12:56
pittijibel: ah, thanks; I was about to restart it because of the hash sum error, and saw that it was already running12:57
jibelI don't know why it happens soooo frequently12:57
pittiah, c'est vert a nouveau!12:57
* pitti donne une accolade à udisks212:58
pittidkessel: I add -Wall -Werror for extra nitpickyness, if you don't mind13:02
smartboyhwUh I give up..... (/me really needs to go to revise C)13:02
pittijibel: hm, is it still creating new jobs properly? I fixed pango1.0's XS-Testsuite header, and it's in raring already, but not in jenkins13:03
dkesselpitti: sure, do that. i'll be back after lunch :)13:04
pittidkessel: nah, I'm doing it while merging; just a FYI13:04
jibelpitti,  1.30.1-1ubuntu1? let me check13:04
pittijibel: oui13:04
jibelsometimes lillypilly is lagging a bit13:04
smartboyhwpitti, I give up...13:06
smartboyhwI really like manual testing more:P13:06
mvopitti: well, I need to run it manually, but that I can fix easily so far two test failures13:06
mvo(and what looks like a hang :/13:07
mvo(one releated to not having network it seems)13:08
jibelpitti, the mirror on lillypilly is a bit behind and only knows about 1.30.1-113:15
pittijibel: ah ok, so it's just that; thanks for checking!13:15
jibeldkessel, atk1.0 2.7.2-0ubuntu2 \o/13:16
jibelcongrats13:16
zygahey mvo, pitti :)13:24
pittihey zyga, how are you?13:24
zygapitti: fine, enjoying my free time :)13:25
zygalots of holiday added up13:25
pittioh, nice; enjoy!13:25
dkesseljibel: yay, my first code contribution to OSS :)13:39
dkesselso... next package ... who will it be...13:39
pittidkessel: poppler? :-)13:41
pittidkessel: what I suggested to smartboyhw a while ago, with poppler-document-new-from-file() and checking some properties13:41
dkesselpitti: ok, i can give it a try13:44
jibelpitti, dholbach or anyone could you review https://code.launchpad.net/~jibel/apt-clone/adt-fixes/+merge/13970213:45
pittilooking13:49
pittijibel: did you already test it in run-adt-tes?13:50
jibelpitti, I did13:50
jibelwith --user=ubuntu13:50
jibelit fails as root13:50
pittireplied13:51
jibelpitti, thanks, added a comment in r1913:55
jamespageo/13:56
pittijibel: ah, perhaps we can also fix the tests to write to stdout?13:56
pittijibel: I usually use13:57
pittiunittest.main(testRunner=unittest.TextTestRunner(stream=sys.stdout, verbosity=2))13:57
jibelpitti, this is better indeed. fixing13:57
pittiah, there goes a new green "pango1.0" dot13:59
jibelhey jamespage14:03
jamespagehey jibel14:03
jibelI noticed, dovecot, cyrus, keystone for example have dep8 tests but no testsuite header14:03
jibeljamespage, maybe it's worth having a look14:04
jamespagejibel, those sounds like some easy wins!14:04
jamespagepreparing my test bed now!14:04
pittioh, ubuntu-drivers-common failure detects an actual regression in bcmwl-kernel-source14:04
jibelpitti, if I set stream=sys.stdout I still have the following warning on stderr14:06
jibelWARNING:root:can't add notification-daemon (pkg notification-daemon not marked upgrade)14:06
jibelWARNING:root:can't add notify-osd (pkg notify-osd not marked upgrade)14:06
pittijibel: ah; no idea about them; so perhaps leave your >&2 in place for now?14:07
jibelpitti, yes, I didn't find where they come from14:07
smartboyhwGod's sake my internet bandwidth is REALLY SLOW today14:08
* smartboyhw reminds himself to do all the cadence testing tmr14:08
jibelanother easy target in main: html2text14:09
dholbachhum14:17
dholbachhttps://jenkins.qa.ubuntu.com/search/?q=raring-adt seems broken14:17
dholbachit just shows 21 test-cases14:17
dholbachhttps://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/ has something like 6014:17
* pitti adds another green gdk-pixbuf bullet14:17
* dholbach hugs pitti14:17
jibeldholbach, 6514:18
jamespagejibel, pitti - is there a way that I can hack the testbed image to use a proxy?14:19
dholbachjibel, ah yes14:19
pittijamespage: you can login with "run-adt-test -sl", then set up the proxy, then run "sudo ./run-adt package"14:19
pittijamespage: (for testing)14:20
pittijamespage: if your test itself wants to set up a proxy, it's got full root privs14:20
pittijamespage: (if you set Restrictions: needs-root)14:20
jamespagepitti, no - I just sit on the end of a sucky internet connect and have a relatively well populated local squid-deb-proxy14:20
pittijamespage: oh, I see14:20
pittiso prepare-testbed should grow a --mirror option14:21
pittijamespage: ah, wait, proxy not mirror14:21
jibeljamespage, in prepare-testbed you can add an apt-proxy directive to the cloud-config script14:22
pittijamespage: so running "http_proxy=... prepare-testbed ..." doesn't work?14:22
jibelor apt_proxy whatever it is called14:22
pittijibel: I'm a bit confused about http://10.98.0.1:8080/view/Raring/view/AutoPkgTest/job/raring-adt-setup-testbed/52/14:24
pittijibel: the job is red, but all 8 subtests are green14:25
jibelpitti, the provisioning failed on alderamin/i386 because a port was already in use, I forced a rebuilt of the failing image instead of everything14:27
jibelin this case the status is not propagated to the master job14:27
pittijibel: so that'll just fix itself tomorrow then14:29
* jamespage recreates his testbed14:32
jamespagejibel, pitti: thanks for that tip - hopefully that will make things a bit quicker :-)14:39
jibelpitti, a trivial one https://code.launchpad.net/~jibel/mawk/xs-testsuite tested with adt-run-test14:58
jibelI don't know why I cannot propose a merge14:59
pittiok, u-d-common and bcmwl should be sorted out now15:03
pittijibel: looking15:06
pittijibel: peut-être que c'est un upstream branch15:07
pittijibel: is it against an UDD packaging branch?15:07
pittijibel: can you please refer to debian bug 692662 in the changelog? and then upload15:08
ubot5Debian bug 692662 in src:mawk "mawk: missing (XS-)Testsuite: autopkgtest header in source stanza" [Wishlist,Open] http://bugs.debian.org/69266215:08
* dkessel run-adt-tests his poppler test15:09
pittijibel: oh, need sponsoring? je peux le faire15:09
pittidkessel: *daumendrueck*15:09
dkesselpitti: "no such file or directory: '.debian/control' ....... again15:10
pittidkessel: but ".debian" looks suspicious indeed15:11
pittiit should be ./debian or debian but not .debian15:11
pittidkessel: how do you run this exactly?15:11
dkesseloh... i typed. it ... spelling error on my side15:11
pittirun-adt-test -sb  lp:~d-kessel/ubuntu/raring/atk1.0/autopkgtest atk1.015:11
pittithat's what I ran15:11
pittiyou probably need a -r raring15:12
dkessel./bin/run-adt-test -r raring -b lp:~dkessel/ubuntu/raring/poppler/autopkgtest15:12
dkesseli'll paste the error log15:12
dkesselah... d-kessel maybe?15:13
jibelpitti, I added a ref to debian bug 692662, and it should probably go directly there instead of ubuntu15:13
ubot5Debian bug 692662 in src:mawk "mawk: missing (XS-)Testsuite: autopkgtest header in source stanza" [Wishlist,Open] http://bugs.debian.org/69266215:13
pittijibel: fine to upload IMHO; it's very likely to get fixed with the next debian upload anyway, so we can sync it back15:13
* pitti looks at samba415:14
pittijibel: ah, did you upload? I thought you weren't core-dev15:16
jibelpitti, no I didn't15:16
jibeland I am not a core dev15:16
pittiJ'ai voir ton changement à pad15:16
jibelah sorry15:17
pittij'ai vu15:17
jibelreverting15:17
pittijibel: I can upload it15:17
jibelI also readded apt-clone because it is not uploaded15:17
pittijibel: you can push those to lp:~jibel/ubuntu/raring/pkgname/autopkgtest (i. e. to a distro branch)15:18
pittithen you can MP15:18
pitti(but don't worry about this for that one)15:18
pittijibel: done both15:20
dkesselhm... how could i have stopped run-adt-test from building the package?15:21
dkesselpoppler takes a while to build :/15:21
jibelpitti, danke schön!15:21
pittidkessel: specify "poppler" as an additional argument at the end15:22
pittidkessel: it's the difference between "-b branch" and "-b branch pkgname"15:22
pittiah, samba4 est très facile15:26
pittidkessel: want me to run a branch for you?15:26
dkesselpitti: i had a missing dependency, i am now trying to run my branch again...15:45
dkesselpitti: i guess my test just passed15:52
pitti\o/15:52
pittidkessel: how did you get around the failure?15:52
dkesseli can't really tell...15:53
dkesselpitti: want to review https://code.launchpad.net/~d-kessel/ubuntu/raring/poppler/autopkgtest ?15:54
pittidkessel: running15:55
dkesselpitti: i used -Wall and -Werrors this time :)15:55
zygaballoons: hey15:55
zygaballoons: would you mind if the hw cert team used this channel for all public discussions?15:56
pittidkessel: I think you should replace libpoppler-dev, libglib2.0-dev with libpoppler-glib-dev15:56
dkesselok15:56
pittidkessel: actually no, you don't use poppler-glib, but just libpoppler-dev15:56
pittidkessel: so drop the glib test dep, as you don't use it15:56
pittidkessel: and your pkg-config calls libs poppler-glib which won't be there without libpoppler-glib-dev15:57
dkesselpitti: *confused*15:58
pittidkessel: so, your code uses the poppler API; your pkg-config call wants poppler-glib; and your test dependency pull in poppler and glib15:58
pittimake up your mind :)15:58
pittidkessel: in fact, if you want to write two tests, one for poppler and one for poppler-glib (with respective pkg-config and dependencies), that's even better15:59
pittioh hm, libpoppler-dev doesn't have header files16:00
pittithse are in libpoppler-private-dev16:00
dkesselyup16:01
dkesselpitti: that's why i went and searched for poppler.h ;)16:01
pittidkessel: so I'm a bit confused what pulls in libpoppler-glib-dev16:01
dkesselthat is where i found poppler.h16:02
pittiyes, but why does it get installed?16:02
pittiooh16:02
pittihttp://bazaar.launchpad.net/~d-kessel/ubuntu/raring/poppler/autopkgtest/revision/12516:02
pittiI was only looking at r12416:02
pittidkessel: so yes, libpoppler-dev and libglib2.0-dev shoudl go16:03
pittibut I can do that during merge16:03
pittidkessel: thanks! I'll upload this16:03
dkesselpitti: you're welcome. I am still not sure if my work saved anyone any time though ;)16:04
pittioh, it does16:04
pittiand also, I hope you had some fun with it and you learned something16:04
pitti+# Author: Martin Pitt <martin.pitt@ubuntu.com>16:05
pittidkessel: ^ you might want to fix that :)16:05
dkesselsure, I learned some stuff. And I think "two packages" was my goal for today :)16:06
dkesselooh :)16:06
dkesselI will :D16:06
pittithen that was a good day, I say :)16:06
pittidkessel: https://jenkins.qa.ubuntu.com/view/Raring/view/AutoPkgTest/job/raring-adt-atk1.0/16:07
balloonszyga, no of course not :-)16:07
balloonsit would be a good thing for people to see and know you16:07
zygaroadmr: it's set then16:08
zygaara: o/16:08
zygabrendand: :)16:08
roadmrzyga: awesome!16:08
zyga:)16:08
dkesselpitti: juhu, grüne lampen :)16:08
zygaone step closer to building a community16:08
dkesselpitti: author is fixed16:08
dkesselis this wiki page updated after the hackfest? https://wiki.ubuntu.com/QATeam/RequiredTests16:09
pittidkessel: danke16:09
dkesseli might do some more tests on my christmas holidays...16:09
jtaylordoes the jenkins instance only build from the archive packages or can one also let it use branches to avoid uploading a package for e.g. a faulty test?16:10
jibeldkessel, not completely up to date, I'll update it with today's effort16:10
pittijtaylor: only from the archive16:10
dkesseloh and i have another question... are there any packages which require tests written in java or c#?16:11
jtaylordkessel: don'T limit yourself to the list, there are plenty packages in universe that need love too :)16:12
pittiin general it doesn't matter which language the tests are written in16:12
pittibut scripts are considerably easier of course as they don't have huge dependencies and don't need to be compiled16:12
dkesseli understand16:13
jtaylorc# has an interpreter16:13
jtaylorwhich should make writting tests a bit easier16:14
jtaylorI think it even works with hashbangs16:14
dkesseljtaylor: yeah, but I don't think I could pick one package myself that may be important to anyone...16:15
dkesselI guess I will just check by here when I want to do something more :)16:18
dkesselalright, see you guys. It has been an interesting event.16:19
balloonsdkessel, thanks for hanging out with us!16:19
jibelmore green dots with ubuntu-drivers-common16:39
pitti\o/16:41
=== josepht_ is now known as josepht
pittiunfortuantely samba4 fails to build in a weird way, I'm fighting with that now16:41
jibelI'm on pbuilder and fighting with signatures :)16:48
jibel68 tests, 2 to go to 7016:50
pittidholbach, jibel: FYI, I need to leave in about 30 mins; in case you want to give an intro again, http://people.canonical.com/~pitti/tmp/intro.txt was what I had prepared16:51
dholbachpitti, awesome - have a great rest of your day!16:52
jibelpitti, great, thanks for your help and enjoy the evening!16:52
pittithanks!16:53
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== salem_ is now known as _salem
pittigood night everyone!17:25
jibelgood night pinky17:27
jibelpitti17:27
pittiuploaded a fix for the samba4 FTBFS, so hopefully that should go green, too17:27
jibelgreat way to end the day17:27
dholbachpitti, jibel: http://daniel.holba.ch/autopkgtests/ (I finally picked the right place to get the data about the number of raring test cases from :-))17:33
dholbachgetting closer to 70 :)17:33
=== _salem is now known as salem_
phillwballoons: are you about?19:27
balloonsphillw, indeed19:27
phillwI've got a bug with installer, but a weird one that seems to affect only KVM running raring installs... as KVM is okay with p & Q I'm struggling to work out what to file it against?19:28
balloonsyou can cite ubiquity if you wish, but include kvm too19:29
balloonsdid you try the new version in the ppa?19:29
balloonsnot sure it landed in raring yet19:29
balloonsI didn't check19:29
balloonskvm I mean19:29
phillwI'm running KVM on qua19:29
phillwquanatal19:29
balloonsahh19:29
balloonsthen you haven't got the new stuff19:29
phillwKVM in Q happily installs L, P & Q as VM's... on when trying to install R do I get the video corruption19:30
phillws/on/only/19:30
balloonsohh19:31
balloonssorry I misunderstood your question19:31
balloonsyes, blame ubiquity.. haha19:31
balloonshave a look first though19:32
phillwI do recall an issue with video corruption a while back. but thought it had been resolved.19:32
balloonsthere is the blank screen bug already filed19:32
phillwthis is not blank... just corrupt.19:32
phillwI'll re-assign it to ubiquity, I had it against lubuntu-artwork, but it also affects xubuntu - so deffo not lubuntu fault :)19:33
phillwballoons: hmm, not a ubiquity bug :/19:40
phillwvideo corruption still exists after installing via alternate.19:40
balloonshmm corruption when?19:40
phillwlook like an X bug?19:40
balloonsyes.. video corruption is not the installer19:40
balloonswell, we can pinpoint it more perhaps19:41
balloonsi guess xorg is fine19:41
phillwVery odd bug... the application windows work fine...19:41
balloonsit might be plymouth19:41
phillwbackground is corrupt, and when installing from desktop the world-map where you choose where you are is corrupt.19:42
=== salem_ is now known as _salem
balloonsok, so might be a compiz / ubiquity bug19:47
balloonsdoes it do that no matter how you install it?19:47
balloonsaka, install now, or boot into desktop, then launch installeR/19:47
balloonsthey are different!19:48
phillwballoons: I battled through a desktop installation and get the corruption in the end product. alternate is less painful to install, but the resultant system is the same.19:50
phillwbug 1088692 has now got some screen shots19:51
ubot5Launchpad bug 1088692 in ubiquity (Ubuntu) "Screen corrupt when installing 13.04 using KVM" [Undecided,New] https://launchpad.net/bugs/108869219:51
balloonskk19:51
balloonshello letozaf_19:51
letozaf_hello :)19:51
letozaf_what are you guys doing ?19:51
phillwletozaf_: bug hunting and there is an automated hack-fest going on as well19:52
letozaf_I guess I am late for the hack-fest19:55
phillwletozaf_: shouldn't be, I believe that jibel is covering now :)19:57
phillwballoons: if you can have a look & a think. I'll be be back in 1 hour. Thanks.19:59
balloonsletozaf_, yes, also working on docs20:00
* SergioMeneses im back20:00
balloonshave you seen the ubuntu.com/community page?20:00
SergioMeneseshey hey guys!20:00
balloonshello SergioMeneses, I owe you an email still20:00
letozaf_I'm looking at in now20:01
SergioMenesesballoons, perfect! Im working on lococouncil things but when I have time enough I see it :D20:01
balloonswell, it's missing a quality page.. and as part of a drive to get all the pages updated, we have a pad: http://pad.ubuntu.com/communitywebsite-contribute-quality20:01
SergioMenesesI was reading dpm's email about the new documents, it sounds really nice20:01
balloonsfull details are on the wiki page: https://wiki.ubuntu.com/CommunityWebsite20:02
SergioMenesesballoons, Im working on another http://pad.ubuntu.com/communitywebsite-help-meeting-locos20:02
balloonsI've started putting some stuff on there, but I'd like to get some of you folks a pass a editing it too20:02
balloonsSergioMeneses, excellent!20:02
balloonsphillw, when you get back you should have a look as well20:02
balloons:-p20:02
* letozaf_ is reading20:03
SergioMenesesomg balloons said my name in his email, ty20:04
balloonsSergioMeneses, yw20:05
Noskcajhello, somehow my ibook is capable of being a computer so i am using it. unfortunatly i can do very little else as it has 376mb of ram20:15
letozaf_balloons: Well what can  I do to help ?20:15
balloonsNoskcaj, nice20:15
balloonsold machines are fun sometimes20:15
balloonsletozaf_, well, feel free to edit the pad or just comment on things in it20:16
Noskcajballoons, i dont believe you. i will joiin the pad20:16
balloonsIt's all my writing, and I haven't really attempted to edit it down yet20:16
balloonsThere's a secret inside the document.. Since it wanted links in the resources section, I thought I would make a new wiki page that could stay static and contain things of interest20:18
vkottililhi, some questions on autopkgtest, this is my first time20:20
balloonsvkottilil, sure20:20
vkottililwhere should I create debian/tests/control ?20:21
Noskcajhow do i scroll in the pad? it just opens and closes the chat bar20:21
jtaylorvkottilil: in the debian package source20:22
jtaylorvkottilil: obtained e.g. with apt-get source package20:22
balloonsNoskcaj, hmm.. my screen is too big, no scrollbar20:22
balloonslet's see20:22
balloonsugh, yea, I can't use the scrollbars20:22
balloonsI can scroll with my wheel or arrow pad20:22
vkottililjtaylor: thanks, i just completed ./bin/prepare-testbed -r raring amd6420:22
Noskcaji found a workaround, select the text and pull down20:23
balloonsyea, similar idea20:23
balloonspg up / pg down20:23
vkottililnext, I want to run the sample test scripts already posted on the wiki for glib2.020:24
balloonsvkottilil, ok, have you installed autopkgtest?20:25
balloonssudo apt-get install autopkgtest20:26
vkottililballoons, I thought prepare-testbed would do that?20:26
balloonsahh20:26
balloonsif your using the lp branch, it's much nicer20:27
balloonsprepare testbed will setup a vm to run tests20:27
balloonsonce it's setup, you can run the test with run-adt-test20:27
vkottililballoons: I am using lp branch - bzr branch lp:auto-package-testing20:28
balloonsok, are you following this? http://developer.ubuntu.com/packaging/html/auto-pkg-test.html20:28
balloonsif so, tell me where your getting stuck ;-)20:28
vkottililyes20:28
vkottilili finished ./bin/prepare-testbed -r raring amd64, next want to run the sample script already posted for glib2.020:30
balloonsok, so run this:20:31
balloons./bin/run-adt-test -r quantal -a amd64 libglib2.0-020:32
balloonsI *believe* that should work for you20:32
jtayloryou probably want raring20:32
balloonsbah20:32
balloons./bin/run-adt-test -r raring -a amd64 libglib2.0-020:32
balloonsdid we loose you vkottilil_ ?20:33
vkottilil_balloons:sorry, i lost the connection20:33
balloons./bin/run-adt-test -r raring -a amd64 libglib2.0-020:34
balloonsI believe that should work for you20:34
vkottilil_where should I put the script for glib2.0 to run it?20:35
jtaylorvkottilil_: the run-adt way would be to branch glib2.0, push your changes to your local lp space and use the -b option20:37
jtaylorvkottilil_: bzr branch lp:ubuntu/glib2.0; <edit, commit>; bzr push lp:~username/+junk/branchname; run-adt-test ... -b lp:~username/+junk/branchname glib2.020:38
vkottilil_ok, I am not changing any thing right now, just wanted to do the whole workflow to learn it, before making changes20:38
jtayloryou can run the script locally for development of the script20:39
vkottilil_ok - thats what i was looking at20:39
jtaylorthere is adt-run as mentioned in the wiki20:40
jtayloralso sadtrunner.py by jwilk20:40
jtaylorI use this awful thing for chroot tests http://paste.ubuntu.com/1430489/20:40
jtaylorhttps://bitbucket.org/jwilk/debian-misc/src/tip/sadt20:40
jtaylorits all just bikesheeding how to run the scripts, the script itself is what is important20:41
vkottilil_ok, great, I will look at these as a starting point;20:41
vkottilil_once I can run the already posted scripts, I can add more calls/apis from a pkg and try to run them20:42
=== toddyhb is now known as toddy
vkottilil_thank you jtaylor, balloons.20:45
balloonsty vkottilil_ .. best of luck..20:48
vkottilil_sure, thanks20:49
=== micahg_ is now known as micahg
phillwballoons: I'm back :) Don't worry about links and notes from todays hack-fest... I have it all logged to review once I've sorted out why I cannot test Raring with KVM....21:08
balloonsphillw, no worries.. come join the fun on the pad:21:09
balloonshttp://pad.ubuntu.com/communitywebsite-contribute-quality21:09
balloonsif you haven't seen it, feedback and editing please21:09
jtaylorcan tests be symlinks to other tests?21:11
phillwballoons: I'm there :)21:13
jtaylore.g. to reuse tests for alternatives dependencies21:13
balloons:-)21:15
phillwballoons: I can confirm that CentOS is also not affected by bug 1086974 Have you any further thoughts on what I should log it against?22:02
ubot5Launchpad bug 1086974 in libguestfs (Ubuntu) "libguestfs: error: cannot find any suitable libguestfs supermin" [Undecided,Fix released] https://launchpad.net/bugs/108697422:02
balloons?22:03
balloonswrong bug phillw ?22:03
phillwoops.. that is my other one!22:04
phillwbug 108869222:05
ubot5Launchpad bug 1088692 in ubiquity (Ubuntu) "Screen corrupt when installing 13.04 using KVM" [Undecided,New] https://launchpad.net/bugs/108869222:05
SergioMenesesballoons, phillw you have done a great job http://pad.ubuntu.com/communitywebsite-contribute-quality22:08
balloonsphillw, lol22:08
balloonsok, so on this bug, 108869222:09
balloonshttps://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/108869222:09
ubot5Launchpad bug 1088692 in ubiquity (Ubuntu) "Screen corrupt when installing 13.04 using KVM" [Undecided,New]22:09
balloonsyour on raring, what video and drivers?22:09
balloonsohh you see the same corruption on xubuntu?22:09
balloonscent os isn't the same kernel22:10
balloonsdoes quantal have the same issue?22:10
phillwballoons: yes, that is why I removed it being lubuntu only.22:10
balloonsand vice versa.. does running kvm on quantal (installing raring) work?22:10
phillwL, O & Q run perfectly. Only R is affected.22:11
phillwand 'P'22:11
balloonsyes.. but that's when the host os is raring22:13
phillwballoons: the host is Quantal.22:13
balloonswhat about when the host os is quantal or precise?22:13
* balloons rattles head22:13
balloonsok, try host os raring, installing raring22:13
phillwI have not installed raring, as the idea of the lesson I'm to hold is that you can test raring on a machine running Quantal?22:14
balloonsyes.. good stuff22:14
balloonsanyways, I guess that one is on me to try then22:15
phillwI will install a raring 'real' area, but it does fly in the face of using VM's to test if you cannot!22:15
phillwThere is deffinately something odd with raring.22:16
phillwI can get raring to install with the quantal version (from synaptic) of virtualbox.22:19
balloonswell, it's just to cover all the bases22:19
balloonsI know kvm had some stuff done to it22:19
balloonsso my guess is the new package works fine22:19
phillwballoons: it has had a lot done... mainly due to ubuntu realising that KVM is at the heart of cloud computing :D22:19
balloonsanyways, we'll know it a moment22:20
phillwwhich as Canonical are a platinum partner is "slightly" embaressing :)22:20
balloonsnew cd is almost synced22:20
balloonsok, kvm'd with raring22:26
balloonsinstall seems fone22:27
balloonsohh..22:27
balloonsthere it is22:27
balloons:-p22:27
phillwballoons: there 'what' is?22:28
balloonsthe bug22:28
balloonsi'll be adding some screenshots22:28
phillwthank heavens for that! I even re-installed my entire system as I'd been 'playing' with KVM owing to the bug I pasted up earlier.22:29
phillwso, a click on 'affects me' and a note stating it is present in raring would really help :D22:29
balloonsalready doing my friend22:30
phillwnow, do we have any idea of what to report it against?22:30
balloonsI hate to ping xnox on this, but he will likely be able to tell us more22:33
phillwFor all I know, it could be clash with gtk2 & gtk3... it's certainly like nothing I've seen before.22:35
=== fader_` is now known as fader_
phillwballoons: ssh -X with a speed of 76Kb/s is painful... but I think a worthwhile exercise to try raring on a full centos version of KVM23:21
balloonshaha23:21
balloonsfull speed ahead23:22
phillwIt's on my dedicated server.... it would be much faster for you to do it!23:22
phillwit has 100 Mb/s backbone.... it's like wading through treacle :(23:23
phillwballoons: you're too young to remember bulletin boards when we were running at 300 b/s23:27
balloons2400 baud was the first for me23:28
balloonsI used 14.4k/28.8k for awhile, then 56k for a long time23:29
phillwooh, we had 300 or, if lucky the 75/1200 was just being supported. But... happy days. In those days people wrote really 'tight' code.23:29
phillwhere in the lovely countryside I get not much more than 56K .... too many miles of copper to the exchange.23:30
phillwI must have a session some time with you so you can set up stuff on the server. It's doing a really good job for teams.23:32
balloonsI too have find the niceities of a always on, high speed server23:35
balloonsI don't have fast or slow connection.. honestly 70k isn't slow.. but by today's standards it definitely is23:35
phillwballoons: for any things using 'X' it is painful, for downloading iso's..... well it is :'(23:36
phillwIt would be faster for me to get on a couple of buses, travel to my Dad's works, download it and catch the bus back.23:37
jtaylorhurray finally also managed to get a test done23:39
phillwjtaylor: congratulations! You see, they are not *that* scary :)23:40
jtaylorphillw: that is not scary? http://paste.ubuntu.com/1430814/ ;)23:41
jtaylor(its not the one I forwarded right now, thats a lot nicer)23:41
jtaylorbug 695881 is what I did today23:42
ubot5Launchpad bug 414976 in Mudlet "duplicate for #695881 STR-TAB should change Tabs" [Wishlist,Fix released] https://launchpad.net/bugs/41497623:42
jtaylordebian bug 69588123:42
ubot5Debian bug 695881 in python-numpy "python-numpy: add autopkgtests" [Wishlist,Open] http://bugs.debian.org/69588123:42
phillwjtaylor: when you are writing stuff, it seems scary. I am a fiend for making 2 comment lines per line of code... but that's so when I look at the code 2 years later, it tells me what on earth was in my mind when I wrote it :P23:43
jtaylorphillw: yeah, that particular one is still in development, I'll comment it before the upload23:43
jtaylorthe symlink crazyness is due to the package not installing the tests and python relative imports preventing just copying the tests from the source23:44
phillwjtaylor: your older self will thank you for doing so.... on that matter, you'll just have to trust me :)23:44
phillwI look back at some of the 'one off' sections of code I've written and really could not follow it without the comments.23:46
jtaylorthe wiki could probably use a python dep8 test example23:48
jtaylorvery many python packages can be tested the same way23:48
jtaylore.g.: https://github.com/neurodebian/pandas/blob/debian/debian/tests/unittests23:50
jtaylorjust I'd now add pys=${pys:-$(...)} so it can be reused in debian/rules too23:50
phillwjtaylor: I'm not a python person, I'm PHP, but as python / perl / php can all achieve similar results when 'chatting' to MySQL it is fortunate that they all start in 'P' for LAMP.23:51
phillwjtaylor: but, as for commenting your code?... http://forum.phillw.net/viewtopic.php?f=5&t=8023:52

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!