[00:44] <rbasak> https://jenkins.qa.ubuntu.com/job/trusty-adt-libapache2-mod-python/20/ ran and failed as a result of my apache2 upload. I got emailed. But I would expected it to have blocked proposed migration except that it didn't, and apache2 got through. What's wrong with my understanding of the process here?
[00:44] <rbasak> (I've just uploaded a fixed libapache2-mod-python)
[06:43] <pitti> Good morning
[06:46] <KI7MT> gm
[10:38] <jibel> pitti, I think I found the problem with autopkgtest of linux. The timeout occurs if copyupdown takes more than 300s
[10:39] <pitti> ooh! but that would only be 5 mins, I thought it timed out after an hour of building?
[10:39] <jibel> pitti, which is the case for linux because it tars/untars the kernel
[10:39] <pitti> jibel: since 2.3.7 there is --timeout-copy
[10:39] <jibel> pitti, yeah, but this 1h was a red-herring
[10:40] <pitti> jibel: I guess globally setting it to 1000 should be fine; we don't usually have "real" timeouts in that phase
[10:40] <pitti> at least I never ran into one
[10:41] <jibel> pitti, I'll do another test with 1000 and see if it passes, then I'll set it by default
[10:41] <jibel> that's also why it is not reproducible with smaller packages
[10:41] <pitti> indeed
[10:50] <jibel> pitti, actually that could be improved in VirtSubProc, if local and remote are on the same filesystem, then use rsync or cp instead of tar/untar
[10:51] <pitti> jibel: you think the tar pipelining is so much overhead? I had expected this to be I/O bound for the hard disk
[10:54] <jibel> pitti, for linux and libreoffice autopkgtest runs on hard disk
[10:55] <jibel> anyway, I'm trying with copy timeout set to 1000, and it will be good enough if it passes
[11:01] <davmor2> Morning all
[15:33] <slickymaster> afternoon all
[15:33] <teward> o/
[16:47] <fox__> Morning From Australia
[18:05] <elopio> balloons, jfunk: do we have a project for system instegration tests?
[18:05] <elopio> for example, where should we put a test that involves unity, unity-scope-click, online accounts and download manager?
[18:12] <jfunk> elopio: not that I know of off the top of my head, perhaps something you could bring up in our team meeting tomorrow?
[18:13] <jfunk> someone else might know
[18:13] <elopio> if there is none, I'll need to start one like tomorrow.
[18:14] <elopio> so, I'll note it down to discuss on the meeting.
[19:48] <balloons> buonasera Letozaf_
[19:48] <Letozaf_> balloons, buonasera
[19:49] <Letozaf_> balloons, I read mzanetti comment that the reminders app  tests fail on jenkins because there is no account configured
[19:50] <Letozaf_> balloons, I suppose you guys have to find out a work around for this
[19:50] <balloons> Letozaf_, right.. I was hoping to solve that today :-)
[19:50] <mzanetti> balloons: hi
[19:50] <mzanetti> balloons: what do you propose?
[19:50] <Letozaf_> balloons, would be great
[19:50] <Letozaf_> mzanetti, hello
[19:50] <mzanetti> Letozaf_: o/
[19:51] <balloons> mzanetti, Letozaf_ I  don't have a proposition.. but let's think aloud together
[19:51] <mzanetti> balloons: so there's to options:
[19:52] <mzanetti> balloons: mock _everything_ (in which case we'd be better off with qmltests)
[19:52] <balloons> your test assumes an account.. which I think needs to change. Ideally, we'd test the account creation
[19:52] <mzanetti> balloons: or inject an account config into jenkins
[19:52] <mzanetti> balloons: actually imo we should have both
[19:52] <balloons> right.. I would mock the account config and inject it
[19:52] <balloons> but we still need a creation test :-)
[19:52] <balloons> and an account we can mock
[19:53] <mzanetti> balloons: what do you mean with creation test?
[19:53] <balloons> there's also the issue of.. if we can, let's avoid pinging the evernote server to start with
[19:53] <balloons> a test to create the account.. Which might lie in online accounts
[19:54] <mzanetti> yeah. that belongs in there
[19:54] <mzanetti> so, we could deploy an account config with the tests package
[19:55] <mzanetti> nah... better to write a mock for the accounts-plugin
[19:57] <balloons> so what we've done in the past for this is to mock it and maniever the app db and files around before launching the app.. Then undoing it when we are done :-)
[19:57] <balloons> We can generate the config on the fly via code, or commit it and copy it to the proper place
[19:57] <balloons> again, depending on what it looks like, one or the other is the better answer
[19:58] <balloons> So, in this case, let's assume we're going to inject an account. What do we need to mock up? And shall we do it via code or committing files?
[20:00] <mzanetti> for integration tests I guess modifying the account's config would be way to go
[20:01] <mzanetti> all we request from the api is a list of accounts where each has a name and token
[20:01] <mzanetti> so we can place some token in there that we manually generate with the server
[20:03] <mzanetti> hmm... I guess the config is in here: ~/.config/libaccounts-glib/accounts.db
[20:04] <mzanetti> balloons: do you know how to do this?
[20:05] <balloons> mzanetti, yes.. I've got experience in mocking things :-)
[20:05] <balloons> I'll look around in the app db
[20:06] <balloons> I've got an account attached locally. I'll remove it and readd and see what it looks like
[20:07] <balloons> we can also ask ken
[20:07] <mzanetti> balloons: well, in ~/.config/libaccounts-glib/accounts.db there is a table Accounts with those values: 5|michael.zanetti@canonical.com|evernote|1
[20:07] <mzanetti> we'd need to insert that
[20:07] <mzanetti> then there must be some api key somewhere
[20:09] <mzanetti> yeah, in Services and Settings are some entries
[20:10] <mzanetti> but still haven't found the actual credentialsid
[20:10] <balloons> mzanetti, I'm asking ken before looking too hard :-)
[20:10] <mzanetti> ok... yeah... if you generate such an account the tests on jenkins should pass
[20:11] <balloons> perfect. That should be enough to get this onto ci
[20:27] <balloons> ok, so I've got some sql that more or less works
[20:37] <Letozaf_> balloons, mzanetti found this if it can help:  http://dev.evernote.com/doc/articles/authentication.php
[20:39] <balloons> does reminders store anything in .local/share/com.ubuntu.reminders-app?
[20:40] <balloons> we do have an issue with my idea.. apparmor I *think* is going to prevent us from modifying ~/.config/libaccounts-glib/accounts.db
[20:44] <balloons> Letozaf_, so I guess I'll work on a branch and have you remerge it after
[20:44] <Letozaf_> balloons, ok fine
[20:54] <KI7MT> Quick question about writing test cases and bugs. If we're going to work on a particular bug for writing up a test case, should we change the assigned too / status when we start working on the docs?
[20:55] <balloons> KI7MT, what do you means start working on the docs?
[20:55] <KI7MT> balloons, When we start writing the Test Case.
[20:56] <balloons> KI7MT, yes, feel free to assign yourself to the bug when you start working on it. When you are ready to merge you can link the mp to the bug report
[20:56] <KI7MT> balloons, ok thank you.
[20:56] <balloons> KI7MT, thank you! Do you need help getting started?
[20:56] <elfy> balloons: was writing that slowly - thanks :p
[20:58] <KI7MT> balloons, Well im sure I'll ahve some Q's at some point, but been using these test cases for yrs, so thought I'd have a crack at writing a few needed ones :-)
[20:58] <elfy> have fun KI7MT
[20:58] <balloons> KI7MT, you will be a natural
[21:05] <KI7MT> balloons, I knew I'd have question(s), I see there is a test script for format checking, I have not used it yet. Is there a way to test render the HTML as I see were not header / body / footer tags
[21:05] <KI7MT> *were not using
[21:05] <elfy> yea there is
[21:06] <balloons> :-) linky elfy ?
[21:06] <elfy> https://wiki.ubuntu.com/QATeam/ContributingTestcases/ManualStyleGuide/test_case_format_script
[21:06] <balloons> boom!
[21:06] <elfy> balloons: givvusachancebeenupforhours:p
[21:06] <KI7MT> Ding, I knew I should have run that script before asking the question.
[21:06] <elfy> :)
[21:15] <KI7MT> Ok, scripts works etc etc  .. how can I see the final version using the broswer ?
[21:17] <balloons> letozaf, so you can at least see where I'm going; lp:~nskaggs/reminders-app/add-test-mock-account
[21:17] <letozaf> balloons, ok thanks
[21:17] <balloons> KI7MT, feel free to open it in a browser, however without the css from the site it won't look the same
[21:19] <KI7MT> balloons, Yes, that's what I was after, the off-line method .. I guess I could grab the css and whip up a script just for sanity checking.
[21:19] <balloons> KI7MT, yea, you could do that.. could be useful
[21:20] <balloons> probably would be easy enough
[21:20] <balloons> let me help a bit
[21:20] <KI7MT> balloons, Simple heardoc should work but need to play with it a bot.
[21:20] <KI7MT> *bit
[21:21] <balloons> http://iso.qa.ubuntu.com/qatracker/testcases/1450/info
[21:21] <balloons> you could nab that and put in your own test :-)
[21:21] <balloons> letozaf, ohh I should warn you.. don't run that :-0
[21:22] <balloons> it will wipe your online accounts db.. no backups.. wip
[21:22] <balloons> do'h
[21:22] <letozaf> balloons, ok thanks, I guess I would have tried it at some point :D
[21:33] <letozaf> balloons, suppose that if I have to write autopilot tests for reminders app, after this  db implementation, I must do it on a VM or where I do not have online accounts
[21:33] <balloons> letozaf, I'll fix it so it doesn't do that
[21:33] <balloons> working on it now
[21:34] <balloons> it'll be like the others and swap the file in and out.. backup original, test with modded file, restore original
[21:34] <balloons> shouldn't cause issues I hope :-p
[21:35] <letozaf> balloons,  for me no matter,  even if I lose my online accounts, I can put them back in :)
[21:35] <balloons> so it works, but the tests still fail because the account isn't valid I think
[21:38] <letozaf> balloons, valid because you have no Evernote account or because of the autentication token
[21:38] <balloons> no evernote account.. I used a fake name
[21:38] <balloons> let me try with my real account, but mocked
[21:44] <KI7MT> :-) Another question, what's the word on word-wrapping 80col ? It would appear wr is not used at all?
[21:45] <balloons> KI7MT, no, we don't force word wrapping at 80.. unless I'm mistaken
[21:45] <balloons> in which case I'd hide in shame
[21:46] <KI7MT> Ok thanks ...
[21:50] <letozaf> balloons, going to bed, be back tomorrow :) buona notte !
[21:50] <balloons> buona notte letozaf
[21:50] <balloons> grazi
[21:50] <letozaf> balloons, grazie a te :)
[21:50] <letozaf> balloons, (means thank you)
[23:26] <KI7MT> For writing tests cases, after Installation for instance, if we want to add a few tests to check basic functionality after login, do the tests themself belong in the install test case or are they separate test case files?
[23:53] <balloons> KI7MT, we have seperate tes sets for those. for install tests we focus on install
[23:54] <balloons> check out the packages folder :-)
[23:54] <KI7MT> balloons, yes, I found a few and seen how it's flowing. Thanks