[05:52] <pitti> thomi: hm, what's the official way to run an autopilot test in-tree now?
[05:52] <pitti> $ PYTHONPATH=. python -m autopilot.run run autopilot.tests.functional.test_introspection_features.IntrospectionFeatureTests.test_window_geometry
[05:52] <pitti> $ python3 -m testtools.run discover autopilot.tests.functional.test_introspection_features
[05:52] <pitti> both of these fail
[05:52] <pitti> and there is no bin/autopilot any more which DTRT
[05:52] <thomi> pitti: yes, that test fails, veebers found that today, and he's looking at it :)
[05:52] <thomi> pitti: DTRT?
[05:52] <pitti> thomi: no, I mean it doesn't even start running the tests
[05:53] <pitti> thomi: I wanted to see what's wrong with it as I recently touched it, but I don't know how to run a test
[05:53] <pitti> thomi: "autopilot" uses the system-installed ap, that doesn't work as it's way too old in trusty
[05:53] <pitti> I need to run it from within the tree
[05:53] <thomi> pitti: well, you don't need to set PYTHONPATH, but aside from that, what you're doing is correct
[05:54] <thomi> pitti: also, the system autopilot in trusty should work fine
[05:54] <thomi> pitti: I think maybe there's something funny happening on your system?
[05:54] <pitti> thomi: http://paste.ubuntu.com/6719045/
[05:54] <pitti> thomi:
[05:54] <pitti> $ autopilot run autopilot.tests.functional.test_introspection_features.IntrospectionFeatureTests.test_window_geometry
[05:54] <pitti>     from autopilot.testresult import AutopilotVerboseResult
[05:54] <pitti> ImportError: cannot import name AutopilotVerboseResult
[05:54] <pitti> ^ that's a change in trunk which isn't in trusty yet
[05:55] <thomi> pitti: oh wait - sorry - I forgot I built & installed it from source :-/
[05:55] <pitti> thomi: trusty has 20131125, that's fairly old
[05:55] <thomi> sorry :)
[05:55] <pitti> thomi: np; hence I wonder how to run it out of the tree now
[05:55] <pitti> thomi: i. e. the equivalent of bin/autopilot [...]
[05:55] <thomi> this works for me:
[05:55] <thomi> python3 -m autopilot.run run autopilot.tests.functional.test_introspection_features.IntrospectionFeatureTests.test_window_geometry
[05:55] <thomi> as does python 2
[05:56] <pitti> I get above pastebin error (AttributeError: 'module' object has no attribute 'functional')
[05:56] <thomi> http://pastebin.ubuntu.com/6719052/
[05:56] <pitti> with both py 2 and 3
[05:56] <thomi> O.0
[05:56] <thomi> and your CWD is inside the lp:autopilot checkout location?
[05:56] <pitti> thomi: yeah, that's the error I wanted to get and investigate
[05:57] <pitti> thomi: yes, I'm in the root dir of the lp:autopilot checkout
[05:57] <thomi> hmmmm
[05:57] <pitti> thomi: ok, but that's the official command?
[05:57] <pitti> then I'll investigate what's wrong with that
[05:57] <thomi> pitti: yeah
[05:57] <pitti> (we should add that to README)
[05:58] <pitti> thomi: even tox.ini says "autopilot run", which again uses the system installed ap, right?
[05:58] <thomi> pitti: no, because tox installs into a virtualenv
[05:58] <thomi> pitti: but the tox config is broken on trusty for some reaon
[05:58] <thomi> *reason
[05:58] <thomi> if you happen to find the problem.... you know what to do :)
[05:59] <pitti> thomi: yeah, I just wanted to make sure I'm actually using the right command this time; thanks
[05:59] <thomi> yeah. generally, 'tox <test_id>' should do what you want
[06:00] <pitti> aah!
[06:00] <pitti> $ sudo apt-get install python3-fixtures python-fixtures
[06:01] <pitti> of course that error message made it *absolutely clear* that the "fixtures" module was missing
[06:01] <thomi> isn't that a dependency on python-autopilot & python3-autopilot?
[06:01] <pitti> (not!)
[06:01] <pitti> thomi: it is apparently fairly recent (not in trusty yet)
[06:02] <pitti> thomi: anyway, the test_window_geometry WFM
[06:02] <thomi> pitti: the failures are specific to desktop configuration
[06:02]  * pitti looks at code to get some ideas what could go wrong
[06:02] <thomi> the test assumes that the desktop starts at 0,0
[06:03] <thomi> and also assumes that there's only one screen configured
[06:03] <thomi> and further assumes that applicaiton geomentry will always be wholly within the desktop area.
[06:03] <thomi> all in all, not a great test :)
[06:03] <pitti> I enabled my internal monitor, still works
[06:03] <pitti> I moved it to the left of my primary monitor, still works
[06:04] <pitti> (I tested these cases back then)
[06:04] <thomi> hmmm
[06:04] <pitti> but I guess it's related to that, I'll have a closer look and follow up to the bug
[06:04] <thomi> if you can't reproduce, then veebers or I can take a look - at least we have a reproducer already :)
[06:09] <pitti> thomi: followed up
[06:10] <pitti> thomi: so apparently I don't understand what the window geometry says, or there is actually a bug somewhere that it sometimes ends up being negative
[06:13] <thomi> yeah, me too
[06:13] <thomi> there's something screwy going on, for sure
[06:13] <thomi> anyway, I gotta go eat dinner.
[06:13] <thomi> might be on later, but probably not
[06:14] <thomi> talk to you tomorrow!
[06:17] <DanChapman> Good Morning
[06:28] <pitti> hey DanChapman
[06:28] <DanChapman> pitti hey :-) how are you?
[06:29] <pitti> DanChapman: I think only ints and strings are matched on the server (libautopilot-gtk/qt, inside the application) side; any other properties (like float) are matched on the client (i. e. autopilot) side
[06:29] <pitti> or more complicated selects
[06:29] <pitti> in those cases, the whole widget (set) is transmitted over D-BUS, and ap filters the result
[06:30] <pitti> DanChapman: quite fine, thanks! and you?
[06:34] <DanChapman> pitti, ahh  ok I see, that makes sense. I mentioned to jibel yesterday about how in the autopilot log of the failed tests that there is an "atk_object_set_parent: assertion 'ATK_IS_OBJECT (accessible)' failed" right before the segfault. COuld it be a Gtk/Atk bug causing our crashes?
[06:35] <DanChapman> pitti, awesome, Yes I'm really good thanks
[06:35] <pitti> DanChapman: in principle, yes; if something before that code corrupts the stack, then anything is possible
[06:36] <pitti> i. e. we need to find out what calls set_parent() and why it's calling that on an invalid object
[06:37] <pitti> DanChapman: oh, is that really an assertion failure, or a CRITICAL?
[06:37] <pitti> DanChapman: an assertion failure should terminate ubiquity, with SIGABRT
[06:38] <pitti> CRITICALs are merely printed out and then the program continues, unless you run ubiquity with G_DEBUG=fatal-criticals
[06:38] <DanChapman> pitti its a CRITICAL
[06:38] <pitti> that's useless for debugging where a critical happens, but of course inconvenient if there are lots of other criticals before that
[06:38] <pitti> sorry, s/useless/useful/
[06:54] <DanChapman> pitti, I see so it might not be that then, I just find it strange it being the last thing that occurs before the segafult.
[06:54] <pitti> DanChapman: oh, it certainly might be that
[06:54] <pitti> DanChapman: i. e. it's well worth investigating why that critical happens
[07:36] <elfy> morning
[11:35] <pitti> jibel: hm, wazn unhappy again? I already retried on i386, amd64 works fine (http://d-jenkins.ubuntu-ci:8080/job/trusty-adt-shotwell/ARCH=i386,label=adt/61/console)
[11:35]  * pitti logs in and check
[11:38] <pitti> jibel: indeed, I can reproduce with "./auto-package-testing/bin/run-adt-test -sU -a i386 shotwell"
[11:38] <jibel> pitti, there is no particular activity on this machine
[11:38] <pitti> with -a amd64 it works
[11:38] <jibel> pitti, I'll reprovision the base vm
[11:38] <pitti> broken i386 base image?
[11:39] <pitti> jibel: OOI, how do you do that? run prepare-testbed, or trigger the jenkins job?
[11:40] <jibel> pitti, either trigger the job trusty-adt-setup-testbed or run $HOME/auto-package-testing/bin/prepare-testbed -r trusty $ARCH
[11:40] <pitti> jibel: ok, I can do the latter (unless you already do)
[11:42] <jibel> pitti, it is running
[11:42] <pitti> jibel: I see you started prepare-testbed for amd64 (but that's the good one)
[11:42] <pitti> jibel: ack, thanks; I'll retry shotwell and spamassassin after that
[11:42] <jibel> pitti, I'll redo both
[11:42] <jibel> archs
[11:58] <jibel> pitti, vms have been rebuilt and shotwell is running on i386
[11:59] <pitti> that's http://d-jenkins.ubuntu-ci:8080/job/trusty-adt-shotwell/ARCH=i386,label=adt/61/console ?
[11:59] <pitti> looks fine
[11:59] <pitti> jibel: merci
[12:00]  * pitti kicks spamassassin, too
[15:03] <elopio> good morning QA.
[15:04] <knome> morning
[15:04] <cgoldberg> morning elopio
[15:11] <elfy> afternoon :p
[15:18] <balloons> xnox, ping
[15:18] <xnox> balloons: hey!
[15:19] <balloons> xnox, so playing with the emulator finally :-) I noticed a few things.. 1) It's REALLY slow for me 2) The core apps don't seem to be a part of the base image you are using
[15:20] <xnox> balloons: 1) emulator is slow, it's a single core 700 Mhz cpu 2) like what ?
[15:20] <balloons> I'm mostly concerned about #2. Should I need to install them? Your run script runs things like weather and calc, but they aren't on my image
[15:32] <xnox> balloons: i'm still confused what you are missing. my scripts as posted latest are to do automated autopilot testing.
[15:33] <xnox> balloons: for general instructions of using emulator see https://wiki.ubuntu.com/Touch/Emulator ; which is ./build-emulator-sdcard.sh & ./run-emulator.sh
[15:33] <xnox> balloons: you should have mostly everything as a normal device, with same sets of apps etc.
[15:33] <xnox> balloons: what's missing? what's different?
[15:44] <balloons> xnox, sorry, got dc'd for a min. I followed your instructions.. I'll try again from the top. The resulting images were simply missing the core apps and I don't know why
[15:44] <rvr> elopio: Good morning
[15:44] <balloons> browsing, dialer, friends.. all there.. no core apps like weather or calc tho
[15:45] <xnox> balloons: which instructions?
[15:45] <balloons> from your email
[15:45] <xnox> balloons: can you give me a link to the post?
[15:46]  * xnox sent many emails with different instructions.... =)
[15:46] <xnox> balloons: or title of the email post.
[15:46] <balloons> https://lists.launchpad.net/ubuntu-phone/msg05784.html
[15:46] <xnox> balloons: none of that should be used to "play with emulator" or "use it"
[15:47] <xnox> balloons: that's only for automated, hand-off, execution of autopilot tests.
[15:47] <balloons> I'm trying to run core apps tests.. I tried the steps to do that and it failed.
[15:47] <xnox> balloons: if you want to start emulator and use it, please see https://wiki.ubuntu.com/Touch/Emulator#Instructions
[15:48] <balloons> xnox, right.. I don't care about using the emulator, I was looking to reproduce test runs.. then run my own
[15:48] <xnox> balloons: do you have logs of the failures?
[15:48] <balloons> xnox, do you build the sdcard before you run your tests?
[15:48] <xnox> balloons: it does everything.
[15:49] <balloons> ok, that's what I did then..
[15:49] <balloons> if I provision again, will it wipe the old stuff..
[15:49]  * balloons looks
[15:50] <xnox> balloons: calculator autopilot tests can crash the emulator at the moment, what else have you tried. friends pass, dialer partioally passes. weather should be ok as well, let me run that one now.
[15:52] <balloons> xnox, after taking a boot to boot, the loop checking for unity status goes on forever.. that's how every test ended
[15:52] <balloons> anyways, trying again.. let's see what happens
[15:52] <rvr> elopio: https://bugs.launchpad.net/ubuntuone-credentials/+bug/1248576
[15:53] <xnox> balloons: i should add watchdog for that. basically sometimes some click hooks fail in the emulator and thus unity8 never starts =(
[15:53] <rvr> elopio: I'm getting a similar bug in another test. Did you discover why StateNotFoundError happens?
[15:54] <elopio> rvr: in that case, it seems QML doesn't find a module.
[15:54] <elopio> so the window is actually missing the component you are looking for.
[15:54] <elopio> take a look at the QML errors to see if that's your case.
[16:00] <balloons> xnox, ok, same thing happens. Here's the log: http://paste.ubuntu.com/6721438/
[16:01] <balloons> currently, the emulator displays unity with the intro screen
[16:01] <xnox> balloons: the log does tell you what's wrong.
[16:01] <xnox> balloons: "error: more than one device and emulator" over and over and over again =)
[16:01] <balloons> yes :-)
[16:02] <balloons> lol.. I do have a device plugged in
[16:02] <balloons> d'oh
[16:02] <xnox> balloons: maybe you want to fix that =) as raised in the email thread....
[16:02] <balloons> it was the tablet, didn't even notice.. I'm sorry
[16:11] <xnox> balloons: <testsuite errors="1" failures="0" name="" tests="15" time="613.245">
[16:11] <xnox> balloons: so weather app does work.
[16:12] <balloons> xnox, seems to be running.. is there an easy way to get logs, or should I simply redirect output?
[16:12] <xnox> balloons: just wait for it to finish.
[16:12] <xnox> balloons: you will have logs, as done by phablet-test-run in the "clientlogs/" folder at the end.
[16:12] <balloons> perfect, ty. I ran the full run-tests.sh so this looks like it's going to be quite a bit
[16:17] <xnox> balloons: and will most-lickely fail a lot and get your emulator stuck =)
[16:17] <balloons> hah.. maybe I should quite while I'm ahead
[16:18] <elfy> or be quiet or quit :p
[16:18] <elfy> good day to you  balloons :)
[16:19] <knome> hallo
[16:24] <balloons> howdy elfy and knome
[16:26] <knome> xubuntu people, they come in numbers
[16:27] <balloons> always in a pack :-)
[16:42] <elfy> balloons - we hunt in packs
[16:42] <elfy> slickymaster is sneaking round the back to catch you out
[16:43]  * balloons looks around nervously
[16:45] <pitti> hey balloons
[16:45]  * slickymaster thinks that balloons should always be afraid... very afraid
[16:46] <slickymaster> and looking over his shoulder
[16:46] <balloons> hey pitti
[16:47] <pitti> balloons: your prodding sufficiently convinced me about bug 1033932, I just committed a fix :)
[16:47] <balloons> oO pitti !
[16:47] <pitti> http://bazaar.launchpad.net/~apport-hackers/apport/trunk/revision/2746
[16:47] <balloons> that's excellent news!
[16:48] <pitti> I really wasn't aware that we have so many "crash on logout" cases; I almost never get those
[16:48] <balloons> last cycle was especially bad for me.. this cycle hasn't been so bad. not seen many
[16:49] <balloons> it seems like the longer I run the same install the more buildup I get, the more I see them :-)
[16:50] <balloons> so pitti plans to SRU this at all? This should hit trusty at least soon
[16:50] <pitti> balloons: let's let it bake in trusty for a bit; the bug has a precise task
[16:50] <pitti> balloons: yes, stgraber is working on fixing apport for containers, then we'll land this in trusty (by next week)
[16:50] <balloons> ofc.. not rushing anything out, heh ;-)
[16:51] <balloons> still, that's very good news. This should really help out trsuty
[17:04] <slickymaster> balloons, DanChapman, can I ping you guys in something offtopic?
[17:04] <DanChapman> slickymaster, sure :-)
[17:04] <balloons> indeed
[17:05]  * DanChapman waves to balloons 
[17:05]  * balloons waves back
[17:05] <slickymaster> I'm applying for ubuntu membership so I would like your testimonials if you think I'm worthy
[17:06] <slickymaster> balloons, DanChapman ^^^
[17:06] <DanChapman> slickymaster, I'd be more than happy too :-)
[17:07] <slickymaster> thanks, DanChapman. I sure appreciate it
[17:07] <slickymaster> DanChapman: my wiki page is https://wiki.ubuntu.com/slickymaster
[17:08] <DanChapman> slickymaster, cool I will get that done :-)
[17:08] <slickymaster> DanChapman: once again, thanls
[17:08] <slickymaster> *thanks
[17:28] <balloons> xnox, ok, so last question :-) If I wanted to run an arbitrary lp branch in the emulator, can I do it? If not, can we get it added?
[17:29] <xnox> balloons: there is no support for that at the moment, so patches welcome.
[17:29] <balloons> xnox, k, I'll give it a whirl
[17:29] <xnox> balloons: it will most-likely be patches to phablet-test-run
[17:29] <xnox> balloons: or options to run-test.sh
[17:30] <balloons> I want to let phablet-test-run do it.. so with that it should be simple on your end eh?
[17:30] <xnox> balloons: right, yeah anything that phablet-test-run supports is easy.
[18:08] <cgoldberg> slickymaster, nice work on wiki page.  I want to get mine together and apply also
[18:09] <slickymaster> thanks cgoldberg. I trully hope that you'll manage to be successful
[18:10] <slickymaster> cgoldberg: if you'll need any help, just ping me
[18:12] <DanChapman> jibel, you still about?
[18:13] <elfy> balloons: slickymaster is going for membership - he might not mention it to you ;)
[18:13] <balloons> elfy, indeed. I'm on it :-)
[18:13] <elfy> :p
[18:14] <cgoldberg> if most of my contributions to Ubuntu (besides being a fanatic user since Warty) are as a Canonical employee, do those count?
[18:15] <slickymaster> cgoldberg: I think elfy would be the best person to address that question
[18:15] <slickymaster> elfy: ^^
[18:16]  * elfy read the question and has no answer - balloons might have, being one 
[18:17] <elfy> not sure I could think of any reason why not - but I've never had anything to do with the membership boards
[18:17] <balloons> contributions are contributions :-) The keys are sustained contributions and testimony from people about said contributions :-)
[18:18] <elfy> that
[18:18] <cgoldberg> fair enough
[18:36] <DanChapman> xnox, does the size of a disk image affect whether you get the auto-resize options. I'm using a 40G win7.qcow2 image and I only have the options to erase it or 'something else'
[18:37] <xnox> DanChapman: auto-resize option is tricky, it depends on many things.
[18:39] <xnox> DanChapman: so first the drive needs to be big enough for two fit two OS, second the original OS needs to be "defragmented enough" to be able to shrink, then shrinking should be possible (so Windws may not be suspsended / hybernated / mix hybernated / quick start disabled), there should be enough primary partitions left if MBR is used (some OEM configurations use up all primary partitions).
[18:39] <xnox> DanChapman: so there are plenty of reasons why auto-resize may not be offered.
[18:39] <xnox> DanChapman: at the moment there is no good logging in ubiquity to log why autoresize was not available.
[18:40] <xnox> DanChapman: also we at times fail to detect Windows 7  / WIndows 8 which also leads ubiquity into believing there "is a large data partition of unknown stuff, not sure what to do with" [18:42] <popey> xnox: related: http://askubuntu.com/a/401543/612 - saw this on AU recently. check out the screenshot of his partitions..
[18:43] <xnox> popey: well bdmurray wants to remove all upgrade options from inside ubiquity =)
[18:44] <xnox> popey: as "upgrade manager is the only support option"
[18:47] <DanChapman> xnox, ok I see thanks, it seems this could be quite tricky to get an image to work with the ubiquity tests then. THis image has sda1 -> ntfs MBR and sda2 -> ntfs, It detects its windows 7 ok i'll try a larger disk image
[18:47] <popey> xnox: makes sense
[20:29] <balloons> Letozaf_, evening to you
[20:29] <Letozaf_> balloons, hello
[20:33] <Letozaf_> balloons, howzit ?
[20:33] <balloons> Letozaf_, getting into using the emulator to run tests
[20:34] <balloons> since it runs so much slower, it can show finicky tests
[20:34] <Letozaf_> balloons, but is it better to test on a device or on the emulator ?
[20:35] <Letozaf_> balloons, saw the email about emulator but was wondering to use it as I have a device
[20:35] <balloons> Letozaf_, device is much faster testing if you have it :-) But if I can't reproduce the issue, the emulator might be helpful
[20:36] <Letozaf_> balloons, so it's better to have it just in case of need
[20:36] <balloons> Letozaf_,right.. and for example I'm looking at these failures; http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-clock-app-autopilot/642628/ and http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/calendar-app-autopilot/
[20:36] <balloons> they seem to only happen on the slow maguro device
[20:38] <Letozaf_> balloons, oh I see, so if one does not have that device he can use the emulator to reproduce it
[20:38] <balloons> Letozaf_, potentially yes :-) That's the idea
[20:40]  * DanChapman has just come across 'indicator-pitti', haha BRILLIANT!
[20:41] <Letozaf_> balloons, well maybe I can try this emulator too, then :)
[20:42] <balloons> Letozaf_, give it a whirl: https://lists.launchpad.net/ubuntu-phone/msg05784.html
[20:42] <balloons> Just make sure you unplug any devices from your pc first
[20:42] <balloons> or it won't work and you'll scratch your head like me
[20:43] <balloons> it will take 5 mins or so to boot
[20:43] <Letozaf_> balloons, thanks for telling me, had my device attached just now :P
[20:44] <balloons> lol.. trust me I spent awhile confused
[20:48] <Noskcaj> DanChapman, lolwut. Was that his fanclub again?
[20:48] <Letozaf_> balloons, the emulator started, but suppose I will have to wait for it to boot
[20:49] <balloons> Letozaf_, yes, it takes a bit.. no worries
[20:49] <Letozaf_> balloons, ok
[21:02] <Letozaf_> balloons, I get a ubuntu-phablet login:  but no tests start :?
[21:05] <balloons> keep waiting
[21:05] <balloons> lol
[21:05] <Letozaf_> balloons, ok :)
[21:12] <balloons> Letozaf_, it work?
[21:13] <Letozaf_> balloons, I'm a bit confused.. after some logs on the screen got another ubuntu-phablet login: now
[21:13] <balloons> what did you run?
[21:13] <Letozaf_> balloons, but in the emulator screen is still black
[21:14] <Letozaf_> balloons, I ran ./scripts/run-tests.sh
[21:14] <balloons> run-all takes 1.5 hours
[21:14] <Letozaf_> balloons, what ?
[21:14] <balloons> yes, looks like it iterated
[21:14] <balloons> you can find the logs in the clientlogs subfolder of the directory
[21:14] <balloons> so, now to run something specific do it like this
[21:14] <Letozaf_> balloons, wow I better stop it and try to run just one test
[21:15] <Letozaf_> balloons, ok tell me
[21:15] <balloons> ./scripts/run-test.sh click com.ubuntu.calendar calendar_app
[21:15] <balloons> or even just one test: ./scripts/run-test.sh click com.ubuntu.calendar calendar_app.tests.test_monthview.TestMonthView.test_monthview_go_to_today_prev_year
[21:15] <balloons> that's a 10 min task, hah :-p
[21:16] <Letozaf_> balloons, but now first I must shut it down and restart it with that script, right ?
[21:16] <balloons> yep
[21:17] <balloons> just end the current process
[21:18]  * Letozaf_ is running the calendar test now
[21:23] <balloons> it fails :-)
[21:24] <Letozaf_> balloons, yes the emulator closed and got emulator-arm: no process found
[21:24] <Letozaf_> balloons, ended just now
[21:24] <balloons> ohh.. that's no good
[21:25] <Letozaf_> balloons, :( what a pitty was curious to see it
[21:25] <balloons> it can fail, it's still wip.. but I've had good success
[21:25] <balloons> try again
[21:25] <balloons> if the emulator itself died you mena
[21:25] <Letozaf_> balloons, ok
[21:25] <balloons> the test should run, just fail to pass is all
[21:25] <Letozaf_> balloons, I will try it again, didn't see anything on the emulator
[21:32] <Letozaf_> balloons, the test does not run on my box:
[21:32] <Letozaf_> Removing directory /tmp/tmplRjlEL
[21:32] <Letozaf_> + /home/letozaf/autopilot-tests/touch-emulator/scripts/run-autopilot-tests.sh -s emulator-5554 -a calendar_app.tests.test_monthview.TestMonthView.test_monthview_go_to_today_prev_year -Q -S
[21:32] <Letozaf_> error: device not found
[21:33] <balloons> weird
[21:33] <Letozaf_> balloons, my device is not attached to my PC :)
[21:35]  * Letozaf_ is trying agai
[21:35] <Letozaf_> again
[21:36] <balloons> :-)
[21:41] <Letozaf_> balloons, sorry same error :(
[21:46] <Letozaf_> balloons, it's late for me now, be back tomorrow
[21:46] <balloons> Letozaf_, sorry to hear that
[21:46] <balloons> thanks for trying.. but you got to see the run-all work I suppose :-)
[21:46] <balloons> so it's another option
[21:47] <Letozaf_> balloons, what, where ?
[21:47] <balloons> Letozaf_, the initial run output stuff
[21:47] <Letozaf_> balloons, how do I do that ?
[21:47] <balloons> check clientlogs
[21:47] <balloons> the 1.5 hour run you did.. run-tests :-)
[21:48] <Letozaf_> balloons, ooooh!
[21:48] <Letozaf_> balloons, well maybe tomorrow I will try that and start early :)
[21:49] <Letozaf_> balloons, bye see you tomorrow
[21:49] <balloons> Letozaf_, ciao