[12:04] <gary_poster> hey benji: you working on getting "resolved" landed in go?
[12:04] <bac> hi rogpeppe1, have you had a chance to review my deploy branch?
[12:05] <rogpeppe1> bac: hiya. not yet. i'm actually taking a swap day today, but i might be able to take a look anyway...
[12:05] <bac> rogpeppe1: ok, it would be nice to get it completely resolved, especially since it is in trunk already.
[12:05] <rogpeppe1> bac: ok
[12:06] <gary_poster> frankban, I moved unexpose up to project 1 :-) I will review in a sec.  frankban bac teknico I could use two reviews of https://codereview.appspot.com/7741043
[12:06]  * bac looks
[12:06] <gary_poster> card is in review land at top of board
[12:08] <gary_poster> Makyo, frankban I mentioned the difficulty in landing the annotation branch to Mark Ramm as an opportunity for process improvement and I think he will run with it, at least for a bit.
[12:13] <teknico> gary_poster, is there anything I can read about purpose and usage of an in-memory juju environment?
[12:16] <gary_poster> teknico, not pre-written, no.  The primary initial usage will be in the charm store for 13.04: people will use this as an in-browser "improv" rather than having everyone actually connect to some shared or not-shared server process.  We also think it will be interesting for testing, and we think we need it to implement the presentation (and perhaps creation or editing) of bundles and generally allowing an import that
[12:16] <gary_poster>  someone can look at before actually deploying.
[12:21] <teknico> gary_poster, thanks. so is it going to mimic the behavior of both pyjuju and gojuju, and then be kept in sync with both?
[12:23] <gary_poster> teknico, the component here is intended to be raw behavior, irrespective of py or go.  It should need to change little, except for big conceptual changes like changing no longer subscribing to all changes.  We will have py and go "wire protocols" that will speak to this component, and yes, they will mimic and be kept in sync.  The expectation is that keeping pyjuju in sync right now will be cheap, and we will only k
[12:23] <gary_poster> eep go juju in sync if it is actuvely helping our testing.
[12:24] <gary_poster> s/like changing no/like changing to no/
[12:24] <benji> gary_poster: yep, that's my first priority
[12:24] <gary_poster> cool thanks benji 
[12:32] <bac> gary_poster: the daily call time sprung forward, correct?
[12:33] <teknico> right, what's the UTC time for the call?
[12:33] <teknico> uhm, reitveld barfs with "Can't parse the patch to chunks" on app/assets/javascripts/js-yaml.min.js , ok
[12:34] <gary_poster> bac, yeah, that worked for everyone yesterday, but I'm happy to wait to switch until Europe moves if anyone prefers (teknico?).  If we do move forward, the UTC time is 1430
[12:34] <bac> teknico: that is a new file so there is no diff
[12:34] <gary_poster> teknico, ok.  that's a minified version of packaged code, so I don't think it needs review.  Project is https://github.com/nodeca/js-yaml
[12:34] <bac> teknico: you can see it by using the first link
[12:35] <teknico> bac, yes, I saw it in the lp diff anyway
[12:36] <teknico> gary_poster, I didn't get what the alternative time is for the call, as opposed to 14:30 UTC
[12:36] <gary_poster> teknico, the old time, which was 1530, right?
[12:36] <teknico> I'm fine with 14:30 UTC, btw
[12:36] <gary_poster> ok thanks
[12:36] <teknico> gary_poster, oh, ok
[12:41]  * benji prepares his vast collection of DST-supporting lawmaker voodoo dolls.
[12:41] <rick_h_> hatch: around this morning? Still fighting valueChange and curious if you have a sec to take a peek.
[12:43]  * teknico lunches
[12:56] <gary_poster> rick_h_, he'll probably be around in 5 or 10 minutes
[12:56] <rick_h_> gary_poster: thanks
[13:35] <hatch> rick_h_: yup back to work today
[13:45] <bcsaller_> hatch: when you get a sec we should check the logs on the CI charm install again, seeing issues there
[13:47] <rick_h_> hatch: otp, but want to bug you about the valueChange test in https://code.launchpad.net/~rharding/juju-gui/search-widget/+merge/152737
[13:51] <hatch> bcsaller_: yeah I saw your email - was just grabbing the creds, do you want me to reply with them?
[13:51] <bcsaller_> hatch: sounds good
[13:51] <hatch> did DST change today?
[13:53] <rick_h_> hatch: sunday 
[13:53] <gary_poster> hatch, Sunday :-)
[13:53] <gary_poster> hatch, not for you yet?
[13:53] <gary_poster> hatch, US has gotten excited about DST lately--we start early and end late
[13:53] <gary_poster> Canada may not have gotten in on the fun
[13:54] <gary_poster> Maybe you switch on the 30th like Europe?
[13:55] <hatch> gary_poster: Saskatchewan doesn't observe DST
[13:55] <gary_poster> hatch, better watch out, benji might move up there
[13:55] <hatch> it's one of the few things the whole prov can agree on :P
[13:55] <gary_poster> :-)
[13:56] <hatch> lol - not a lot of southerners can handle the winters ;)
[13:56] <gary_poster> yeah, costa rica might be a better option to escape DST...
[13:57] <gary_poster> so anyway hatch, is it still OK to have a call in 34 minutes?  And will your starting time be typically in 4 minutes?
[13:57] <benji> now that sounds like a plan
[13:57] <hatch> gary_poster: yes and yes - I can probably work towards starting an hour earlier if it's needed
[13:57] <rick_h_> hatch: got time for a quick hangout?
[13:57] <hatch> gimme 5 just getting a few things setup
[13:58] <rick_h_> hatch: rgr
[13:58] <gary_poster> hatch, great.  Only start an hour earlier if you want to.  Let me know if you decide to, but for now I'll assume that you will start as before, in 2 minutes
[14:04] <hatch> rick_h_: ok in guichat?
[14:04] <rick_h_> hatch: sec
[14:14]  * bac purges cobzr from system.  \o/
[14:15] <hatch> rick_h_: gota hate it when fresh eyes look at something and pick out the problem within seconds eh? ;)
[14:16] <teknico> bac, oh, nice. :-) what are you using instead, the pipes bzr plugin? did thumper put out the write up he mentioned at the sprint?
[14:16] <bac> teknico: yes, they are in the doc directory of juju-core
[14:16] <rick_h_> hatch: works for me. Better something simple I didn't see vs doing it completely wrong or trying to make it do something it can't
[14:16] <bac> both bazaar-*.txt docs are worth reading
[14:16] <hatch> very true very true
[14:17] <rick_h_> hatch: but yea, I should propose some changes to the docs that note that though. You'd think it'd be pretty much bold'd 
[14:18] <hatch> yeah that has come up so many times in the chats but nobody has ever updated the docs
[14:18] <hatch> heh
[14:18] <hatch> is there a company address book that I can download into thunderbird so it will autocomplete the emails?
[14:19] <gary_poster> yes hatch, looking
[14:19] <hatch> thanks, my search fu was failing me
[14:19] <rick_h_> hatch: https://wiki.canonical.com/AddressBook?action=show&redirect=LDAP
[14:20] <gary_poster> yeah that
[14:21] <hatch> eggcelent
[14:21] <hatch> I think I might dual boot this computer into Ubuntu instead of VMing, after a week on my laptop the VM lag is driving me bonkers :)
[14:27] <gary_poster> jujugui, call in 2 in guichat
[14:30] <gary_poster> benji, pingy ping ping ping
[14:31] <benji> gary_poster: coming
[14:43] <Makyo> frankban, Getting broken diffs in the 'Support unexpose' code review (error: old chunk mismatch).  Can you try reproposing, maybe after merging with trunk?
[14:43] <frankban> Makyo: sure
[14:47] <frankban> Makyo: done
[14:47] <Makyo> frankban, Thanks.
[14:47] <Makyo> Works now.  Review.
[14:47] <Makyo> ...reviewing.
[14:48] <goodspud> Apologies for not attending. I've been caught up in discussions
[14:51] <gary_poster> np goodspud.  Everything ok?
[14:52] <goodspud> gary_poster, all is good in the world
[14:52] <gary_poster> :-) cool
[14:52] <goodspud> gary_poster, and thanks for your comments on the user testing findings
[14:53] <gary_poster> welcome goodspud.  I also commented on an older one from jovan2 that I had missed but it was just to try to clarify.  I maybe should have been more helpful
[14:54] <gary_poster> but hopefully it was at least somewhat helpful :-)
[14:54] <goodspud> It's always helpful, even if it challenges us or raises new questions
[14:55] <gary_poster> :-)
[14:55] <goodspud> gary_poster, actually we hate it when people challenge us.
[14:56] <goodspud> We are always right damn it!
[14:56] <goodspud> :)
[14:56] <gary_poster> of course!
[14:56] <rick_h_> all bow!
[14:56] <gary_poster> :-)
[14:56] <goodspud> Actually there is nothing better than seeing a designer react when someone doesn't like their work
[14:56] <goodspud> It's quite funny
[14:56] <gary_poster> lol
[14:56] <hatch> gary_poster: Ben now has all of the information that was in my head that he needed to continue on solo - what would you like me to move onto next?
[14:57] <gary_poster> hatch, there's nothing to help on with the CI/Windows stuff--it
[14:57] <gary_poster> 's just wrapping up on both sides?
[14:58] <frankban> thanks for the reviews Makyo and bac
[14:59] <hatch> gary_poster: yeah there is a deployment bug but now that Ben can get into the slave and the instances I'm sure he'll be able to get that going pretty soon
[14:59] <hatch> *famous last words*
[14:59] <hatch> :)
[14:59] <gary_poster> hatch and IE is working otherwise?
[14:59] <gary_poster> all tests passing and suchlike?
[15:00] <hatch> well right now we can't run the tests - but they will need some adjustment once they are back up and running
[15:00] <hatch> saucelabs times out if they run to long
[15:00] <hatch> so we'll need to split them up because IE is slower than the rest of the browsers
[15:00] <gary_poster> hatch, you can run those locally, yeah?  Let's talk on guichat, that will be faster :-)
[15:03] <rick_h_> goodspud: joining the hangout?
[15:13] <gary_poster> benji, you applied for the juju-gui saucelabs account to be open source, right?
[15:13] <benji> gary_poster: right (or that was my intent; your question raises doubts)
[15:14] <gary_poster> ack benji 
[15:17] <gary_poster> benji it is, all good thx
[15:17] <benji> cool
[15:30] <gary_poster> bcsaller_, could you join hatch and me in guichat please?
[15:32] <rick_h_> jcsackett hatch if you get a few min can you look over https://codereview.appspot.com/7519044/ ? See the notes in the comments to help explain why a couple things are the way they are
[15:41] <hatch> yup
[16:11] <hatch> rick_h_: this._events.push() is sure ugly...we should pool our brains at some point and come up with a better solution - don'tyathinks?
[16:11] <rick_h_> hatch: yea, I had thought about a wrapper like this.addEvent()
[16:11] <rick_h_> and sticking that on Y.Widget, but didn't go that far yet
[16:11] <rick_h_> maybe an extension! :)
[16:12] <rick_h_> Y.WidgetEventCleaner
[16:12] <hatch> haha yeah I'd like to almost see that as part of event
[16:12] <hatch> Luke is rewriting event in his spare time so maybe I can chat with him about adding something along those lines
[16:12] <rick_h_> hatch: hmm...you'd have to get it into the Widget destructor though so not sure how that would work 
[16:13] <rick_h_> it seems you'd just be able to auto/pretty up the Widget side. 
[16:13] <hatch> good point.... a base extension then
[16:13] <hatch> because view, widgetm and plugin would bennefit from it
[16:13] <rick_h_> ugh, not sure...guess I'd have to see how that would work
[16:13] <hatch> yeah I have no idea
[16:13] <hatch> :)
[16:13] <rick_h_> I only thought so far as a wrapper around _event since I agree it's fugly
[16:14] <hatch> and doesn't minify very well
[16:14] <rick_h_> meh, gzip ftw ;P
[16:19] <gary_poster> hey hatch, what's your charm branch?  I want to see if something I have merges cleanly
[16:20] <hatch> ~hatch/charms/precise/juju-gui/trunk
[16:20] <gary_poster> thank you
[16:20] <hatch> that's from memory :) sorry for the lack of link
[16:20] <gary_poster> heh,np
[16:25] <hatch> rick_h_: review done - just a few small things
[16:26] <rick_h_> hatch: thanks for the feedback. 
[16:31] <hatch> rick_h_: oh - I wasn't sure exactly where the notes about the events applied to so I just made the comments anyways :)
[16:32] <rick_h_> hatch: yea everything looks all good. 
[16:34] <hatch> my laptop has an expansion slot thats 3.5cm x 0.5cm - anyone have any idea what it's called?
[16:35] <hatch> I'm wondering if I can get a display port card so I can use my laptop as my daily computer
[16:35] <hatch> ExpressCard
[16:35] <hatch> hah - figures, right after I ask I find it :D
[16:39] <hatch> looks like I'd have to do a ExpressCard USB3>DisplayPort now that sounds like a driver nightmare
[16:54] <gary_poster> therve, hi.  we have a release of juju-gui with landscape bits.  https://ec2-50-17-161-4.compute-1.amazonaws.com/ is example with landscape annotations (that I plan to shut down soon ;-) ).  password is "admin" but I don't think you'll need it.  You may want to use our ~juju-gui charm (juju deploy cs:~juju-gui/precise/juju-gui) rather than the default charmers now; we have a merge pending, and have some other change
[16:54] <gary_poster> s coming.
[16:55] <therve> gary_poster, cool, looking
[16:57] <therve> gary_poster, there are some additional bits in the URL, I don't know if it's your tests data: computers/criteria/environment:env0/computers/criteria/service:mediawiki[...]
[16:58] <gary_poster> oh, the doubled up bits
[16:58] <gary_poster> looking
[16:59] <gary_poster> when everything is artificial it's hard to notice that :-/
[17:00] <gary_poster> therve, I think it is the data: annotations are being produced according to the pre-Kapil approach and our code is working with the post-Kapil approach
[17:00] <gary_poster> that is, our fake annotations are old, but gui code is new
[17:00] <therve> gary_poster, ok. we'll see how it goes with the real deployment then :) thanks
[17:01] <gary_poster> cool therve.  I look forward to hearing, and we'll jump on fixes if needed.
[17:02]  * gary_poster declares that url as no longer open. :-) messing with some other things there now.
[17:04] <hatch> gary_poster: the changes you made to lbox would those have come down in the PPA?
[17:04] <gary_poster> hatch they are in our (gui) trunk.  it is just an lbox config
[17:04] <gary_poster> in a .lbox file
[17:04] <hatch> ohh ok
[17:05] <gary_poster> therve confirmed it is the old data, fwiw
[17:13] <hatch> I can't seam to propose bcsaller_'s branch because it's saying there is no diff
[17:13] <gary_poster> hatch, branch of which?
[17:13] <hatch> the ie-cuts branch
[17:13] <gary_poster> charm or gui
[17:13] <hatch> gui
[17:13] <gary_poster> looking
[17:14] <hatch> you may have just got an email that shows a 0 diff too
[17:14] <hatch> :/
[17:14] <hatch> oh
[17:14] <gary_poster> hatch, you are trying to propose ititself
[17:14] <hatch> it's trying to merge itself
[17:14] <hatch> :)
[17:14] <gary_poster> yeah that :-)
[17:15] <hatch> so I need to branch trunk, merge ie-cuts then propse that?
[17:15] <gary_poster> hatch, try merging trunk
[17:15] <gary_poster> that would be easiest
[17:15] <gary_poster> and probably best
[17:15] <hatch> alright I'll try that
[17:27] <hatch> rick_h_: did you forget to add the input.focus() in charm-search.js ?
[17:27] <hatch> your comment says that you added it but it's not there :)
[17:28] <rick_h_> hatch: looking, sec
[17:30] <rick_h_> hatch: bah, pushing up now.
[17:30] <hatch> :D
[17:30] <rick_h_> hatch: actually will add a test for that as well so that I don't miss it again.
[17:31] <hatch> that sounds good
[17:31] <gary_poster> hatch, I saw your ie-cuts mp, cool.  will review in a minute.  that's a pair branch so you only need 1.
[17:31] <hatch> gary_poster: yeah the propose got all messed up, so I'm trying again
[17:31] <gary_poster> for your charm branch, I have a change I'd like to either make after you or with you
[17:31] <gary_poster> lp:~gary/charms/precise/juju-gui/bug1117896
[17:31] <gary_poster> hatch, oh!
[17:31] <gary_poster> ok
[17:31] <gary_poster> I won't look at it then, nm :-)
[17:32] <gary_poster> hatch, for charm branch do you want me to propose the combined branch, to take that off your plate?  We could probably all then look at stuff and approve it and move on :-)
[17:32] <gary_poster> I just verified that it worked
[17:32] <gary_poster> with staging and building
[17:33] <gary_poster> and default
[17:33] <hatch> rick_h_: there is one issue with focusing though - if the user has something else focused and then all of a sudden that input is in focus they may be all 'wtfyo where my focus go?'
[17:33] <hatch> gary_poster: sure that would work
[17:33] <gary_poster> ok
[17:33] <hatch> unless bcsaller_ has made any changes to it ?
[17:33] <hatch> besides logs that is
[17:33] <rick_h_> hatch: right, so the comes about by something in the UI thinking that the search needs to be udpated. If they click on smoething that does that (category link) the UI will change around anyway.
[17:33] <hatch> rick_h_: gotcha - just wanted to point that out
[17:34] <hatch> :)
[17:34] <rick_h_> hatch: yea, ideally I'd not have to focus first, but I think it's a good trade off and if I'm wrong we'll tweak it another way
[17:34] <hatch> gary_poster: ok the patch set two diff'd properly in codereview
[17:34] <gary_poster> ok cool
[17:35] <hatch> rick_h_: yeah I would like some way to trigger the valuechange without focus, but I"ve wanted that for a long long time heh
[17:36] <rick_h_> hatch: I'll probably have to tweak things as it is once I tie in autocomplete into that search input
[17:37] <rick_h_> but works for the moment
[17:38] <hatch> oh yeah for sure - I was just mentioning in general - requiring a focus creates issues when a manual value set should also trigger it
[17:39] <hatch> in $project~1 I had that issue
[17:49] <hatch> gary_poster: did you propose the combined branch? I haven't received an email yet
[17:49] <gary_poster> hatch, I had some escapades of my own, but it is here (no rietveld): https://code.launchpad.net/~gary/charms/precise/juju-gui/bug1117896/+merge/152973
[17:51] <hatch> ahh gotcha :)
[17:52] <sinzui> bac, anyone, we have a juju-core branch. Who do we ask and where to get a review?
[17:52] <BradCrittenden> sinzui: ask in #juju-dev
[17:53] <sinzui> thanks
[17:53] <bac> sinzui: you'll need two reviews that say *exactly* "LGTM".  no other combination of english words or characters are accepted
[17:53] <bac> "this is the most awesome branch ever and i demand you land it now" does not count
[17:54] <sinzui> bac, yep, We've been through that
[17:54] <bac> sinzui: the reviewers over there are pretty good about watching their email and handling reviews without bugging htem
[17:54]  * sinzui now type lgtm, r=m, just fucking land it
[18:13] <hatch> gary_poster: looks good - although I think the print's under first_path_in_dir() probably aren't needed - I am pretty sure we only added those for debugging
[18:13] <hatch> 192, 195, 197, 198
[18:16] <hatch> taking lunch
[18:59] <gary_poster> hatch, ack thanks, will remove
[19:02] <hatch> I'm pretty sure the changes to the charm require our changes to deploy_charm_for_testing.py to function
[19:02] <hatch> so hopefully ben is making headway on that deployment issue
[19:05] <gary_poster> hatch, other way around.  deply_charm....py needs the charm.
[19:05] <hatch> oh...right, that's what I meant
[19:05] <hatch> :)
[19:05] <hatch> my head is just full of circular references
[19:05] <hatch> pretty soon I'll run out of ram and explode
[19:06] <gary_poster> :-)
[19:06] <bac> gary_poster: where you going to bump the WIP limit on 'story 1'?
[19:07] <bac> not 'where' but 'were'
[19:07] <gary_poster> bac I got cold feet, but yes,  done.
[19:07] <gary_poster> well, saving
[19:07] <gary_poster> now it is done
[19:07] <bac> k, thx
[19:08] <bcsaller_> hatch: The tests are running again, I've been looking into the IE failures, I still see timeouts
[19:09] <hatch> oh ok I was just about to start on that using EC2
[19:09] <hatch> glad you poped in :D
[19:09] <hatch> what was the issue with the deployment?
[19:09] <gary_poster> hatch, you can land the ie fixes branch I think
[19:09] <gary_poster> if the branch was in a pair then we only need one review
[19:10] <hatch> sounds good
[19:10] <benji> gary_poster: any preferences for my next card?
[19:11] <gary_poster> benji, cool that you landed the go thing.  I think I'd vote for you working on the go stuff: implementing existing go commands in JS, or working on additional go commands
[19:13] <benji> sounds good
[19:14] <Makyo> That destroy-service branch was so much easier than the addunits one.  Should've started with that.
[19:14] <hatch> bac: do you have your ubuntu vm disk shared with osx?
[19:15] <bac> hatch: no
[19:15] <hatch> ahh ok, I wasn't sure if you were actually working in ubuntu or osx
[19:15] <bac> u
[19:15] <bac> i think gary used to do the other a long time ago
[19:19] <gary_poster> hatch it is a pain because of file permissions and changed owners and such.  I ended up mounting nfs in OS X and it was ok.
[19:20] <hatch> ahh ok that's what I was thinking of doing - I am trying to find the best @home dev env with my current hardware
[19:20] <gary_poster> I liked the nfs solution pretty well, actually
[19:20] <gary_poster> getting it set up was a bit of a pain but not too bad iirc
[19:21] <hatch> things like email might be a little bit of an issue
[19:21] <hatch> so that might have to stay in the VM
[19:21] <gary_poster> hatch, I actually used server Ubuntu only
[19:21] <gary_poster> I did everything else in OS X
[19:21] <gary_poster> and forwarded ports and such
[19:21] <gary_poster> that was the annoying part
[19:22] <hatch> ahh
[19:22] <gary_poster> sometimes I just mucked with my /etc/hosts filein OS X
[19:22] <gary_poster> that sometimes worked ok too
[19:24] <hatch> I hate spending time making things work instead of being productive
[19:24] <hatch> heh
[19:24] <gary_poster> yeah
[19:24] <hatch> maybe I'll make my own 'ubuntumini' :P
[19:25] <hatch> looks like dual booting them now isn't has hard as it once was
[19:27] <hatch> could pick one of these up http://www.newegg.ca/Product/Product.aspx?Item=N82E16856102001
[19:27] <hatch> it has a tbolt port
[19:59] <hatch> so should I write this documentation in markup?
[20:00] <hatch> markdown
[20:00] <gary_poster> heh
[20:00] <hatch> :)
[20:00] <gary_poster> hatch, where are you going to write it?  The charm uses markdown, the gui uses ReST, and the wiki uses...something that I forget
[20:01] <gary_poster> hatch, so if you want to write the main docs in markdown, I guess you ought to decide that the charm is the best place to write the docs :-)
[20:01] <gary_poster> then you could add links in the other places
[20:01] <hatch> I'm writing it in a google doc but then I'll likely save it into the gui as that's likely where people would be initing the tests from
[20:01] <gary_poster> Yeah
[20:01] <gary_poster> ReST should be target them
[20:02] <gary_poster> We consume them and make a site with them
[20:02] <gary_poster> hatch, basics are simple. http://docutils.sourceforge.net/docs/user/rst/quickstart.html
[20:02] <hatch> ReST was a very pooly chosen acronym haha
[20:03] <hatch> alrighty rest it is
[20:04] <gary_poster> cool
[20:58] <hatch> am I to keep to an 80 char limit in rst files? Does the parser know not to break the lines in the middle of a sentence ?
[21:00] <benji> hatch: yes (or 79, like the more refined among us) and yes
[21:01] <hatch> ok so I don't or do need to leave a space at the end?
[21:01] <benji> Here's a reST quick reference: http://docutils.sourceforge.net/docs/user/rst/quickref.html
[21:01] <gary_poster> don't
[21:01] <benji> nope, no space at the end of lines
[21:01] <hatch> maybe I'll do 78 just to be extra refined :P
[21:02] <gary_poster> r
[21:02] <gary_poster> e
[21:02] <gary_poster> f
[21:02] <gary_poster> i
[21:02] <gary_poster> n
[21:02] <gary_poster> e
[21:02] <gary_poster> d
[21:02] <hatch> lol 
[21:32] <hatch> bcsaller_, when is your EOD now?
[21:32] <hatch> 32 mins ago? :)
[21:33] <bcsaller_> hatch: still going 
[21:34] <hatch> oh alright - things going ok with the tests? I saw that the deploy worked so that's good :)
[21:35] <bcsaller_> hatch: yes, that all seems to be working again, but I haven't figured out why the other isn't working still
[21:35] <bcsaller_> and it still takes a long time to try something
[21:36] <hatch> well...why don't you manually set up the canonistack instance from the jenkins slave and then manually fire off the selenium tests?
[21:36] <hatch> that way you can avoid the instance setup time
[21:37] <hatch> I know that we ran into issues with the deploy leaving things around - but if you ssh into the canonistack instance you 'should' be able to avoid that
[21:37] <hatch> if I am thinking correctly
[21:40] <hatch> jcsackett, review completed
[21:40] <bcsaller_> hatch: yeah, I was thinking that as well. I'm also thinking of adding to the wait_for primitive to support a retry count
[21:47] <rick_h_droid> jcsackett ping
[21:48] <rick_h_droid> sinzui when you do the hangout with can you invite me manually? on the mobile side atm. 
[21:48] <sinzui> yes
[21:48] <rick_h_droid> thanks
[22:05] <rick_h_droid> sinzui are we on
[22:05] <rick_h_droid> ? 
[22:06] <sinzui> I'm just pinging huw
[22:06] <rick_h_droid> k
[23:03] <hatch> bcsaller_, were you able to get the sauce labs tests to run locally on your machine? Without going through EC2 or Canonistack? 
[23:04] <hatch> I remember you mentioning something about it but I'm not sure what the result was :)
[23:09] <hatch> gary_poster, bcsaller_ first draft http://bazaar.launchpad.net/~hatch/juju-gui/ci-documentation/view/head:/docs/continuous-integration.rst
[23:19] <gary_poster> Great start hatch, thank you!  Perfect
[23:20] <gary_poster> I will look at it more closely tomorrow