[00:29] thomi: when you have a moment would you mind casting your eyes over this quickly? https://code.launchpad.net/~veebers/autopilot/logging-binary-attachments-1336109/+merge/225098 === alexabreu is now known as alex-abreu|off === vrruiz_ is now known as rvr [19:33] barry: did you get my email? [19:58] thomi: i did, responding now [19:58] barry: awesome - wasn't sure what address to use. [19:59] thomi: they all end up in the same place :) [19:59] ahhh ok [19:59] thomi: they just take different paths to get here [19:59] I was looking for a non-work address, but I guess at least this way you can filter based on the target address :) [19:59] anyway, sorry about the schedule switch-aroo [19:59] thomi: no worries. you can always use my at python dot org address too [20:00] barry @ ? [20:00] thomi: yeppers [20:00] will try and remember that for next time :) [20:00] * barry has *a lot* of email addresses :) [21:22] barry: got a second? [21:26] thomi: sure [21:27] barry: so I'm having some odd problems with virtualenvs, python 34, and testing... [21:27] in my setup.py, I do 'tests_require=[dep_a, dep_b] [21:28] I create a virtualenv with 'virtualenv -p python3 ve' . ve/bin/activate [21:28] then try and run the tests with: python setup.py test [21:28] I see it downloading all my test dependencies, but then the tests fail to run. Digging a little deeper, they fail to run because they cannot import the test dependencies! [21:28] but I can see them being downloaded, and they all create *.egg files in . [21:29] am I missing something? I thought 'python setup.py test' was 'just supposed to work' [21:29] thomi: yeah, it should work [21:30] are you sure it's not failing on some other explicit dependency that's not defined in tests_require? [21:30] hmmm [21:30] oh, one thing you can do, fire up your venv's python and try to import those deps at the >>> prompt [21:30] sometimes, there are cascading errors that end up looking like ImportError but really are caused by something else [21:31] yeah I get ImportErrors there as well [21:31] then, try to import the test modules [21:31] it looks like they're not being installed to the virtualenv correctly [21:31] thomi: so what if you manually pip install them into the venv? [21:31] then it seems to re-download and install them [21:31] yeah, it's doing all that work all over again :( [21:32] thomi: are you on utopic? [21:32] barry: no, trusty [21:32] thomi: well, at least i know that my virtualenv wheel stuff isn't affecting you :) [21:33] but you can't run pyvenv-3.4 either [21:33] (just to see if there's something weird with the venvs) [21:33] if I manually 'pip install ...' all the deps then 'python setup.py test' works [21:34] thomi: do you have a branch? i could try it on utopic [21:34] sure, let me upload [21:35] barry: lp:~canonical-ci-engineering/uci-engine/nfss [21:35] barry: change to the nf-stats-service directory [21:36] thomi: trying. btw, i'm still working on that stack of packages. it's a dark and twisty maze [21:36] well... if you feel like that, I'm glad I'm not attempting to do it :) [21:38] it's insane. dozens of uploads to debian. syncs to ubuntu. plus ubuntu-only packages that block -proposed promotions. jeebus. [21:38] oh thomi you will love this: [21:38] ---------------------------------------------------------------------- [21:38] Ran 5 tests in 0.001s [21:38] [21:38] :( [21:38] that makes me sad! [21:38] why doesn't it work here? [21:39] thomi: nfc. let me see if i have a trusty system laying around [21:41] * barry fires up his trusty vm [21:56] thomi: well, on my trusty vm, it seems like the psycopg dep isn't too happy [21:56] oh? [21:56] you need to install libpq-dev or something [21:56] * barry tries [21:56] yeah - libpq-dev [21:58] hmmm [21:58] ./psycopg/psycopg.h:31:22: fatal error: libpq-fe.h: No such file or directory [21:58] #include [21:58] ^ [21:58] compilation terminated. [21:58] hmm [21:58] [21:59] I get this: http://pastebin.ubuntu.com/7733589/ [22:00] yeah, it seems really unhappy about that header file, even though it's there in /usr/include/postgresql! [22:00] oh, maybe that's not on -I [22:01] why would that be the case on 14.10 but not 14.04 [22:01] i will try to install the pacakge and use --system-site-packages [22:02] barry: it's odd, on my system I don't get that message, it just seems to... stop... [22:03] well, even --system-site-packages isn't very happy [22:03] so i can't get even as far as you've gotten :( [22:05] barry: ahh well, don't worry about it [22:06] barry: I can work around this for now, it's not such a big deal [22:06] I was hoping you'd say "oh yeah, you need to do X" [22:06] thomi: yeah, sorry, i tried :) [22:06] thanks for your help :) [22:06] "help" :) [22:07] sure, at least now I know that I was doing the right thing [22:07] and that the problem is elsewhere [22:07] yep [23:19] Hi, I assume autopilot works on desktop? My very simple tests fails/crashes because it cannot find "MainView" [23:19] josharenson, what do you mean? [23:21] balloons, I have a click app that I created in Ubuntu-sdk. There is a file called "run" in app/tests/autopilot (presumably auto-gened by the SDK) [23:22] balloons, when I run "run", it starts my app, and the test errors out almost instantly with the following error [23:22] StateNotFoundError: Object not found with name 'MainView'. [23:22] My application definitely has a MainView object [23:22] josharenson, sorry I'm literally walking out the door atm... I'll respond when I return if no one else does [23:23] ha ok [23:23] thanks [23:23] josharenson, look at the core apps for examples that work [23:23] that should help [23:23] lp:ubuntu-clock-app for instance