I believe Martin has been investigating updating the bot to support all of
our shared code. I certainly agree with this sentiment, but I'd rather not
train people to be in the habit of just clicking the button if we can get
the bot running soon.
John
=:-
On Thu, Jul 24, 2014 at 9:57 AM, Tim
Forgot to replay-all
Forwarded Message
Subject: Re: Please run the tests
Date: Thu, 24 Jul 2014 16:49:27 +1000
From: Ian Booth ian.bo...@canonical.com
To: Tim Penhey tim.pen...@canonical.com
The Jenkins jobs to test before landing all the Juju sub reps are almost ready.
So it
So, we have some intermittently failing tests in state/watcher.
The tests fail when the machine on which they are run is heavily loaded.
The watcher infrastructure essentially polls every 5 seconds the txns.log
collection to see what new transactions have been written and turns any new
On Thu, Jul 24, 2014 at 12:59 AM, roger peppe roger.pe...@canonical.com
wrote:
On 23 July 2014 11:51, John Meinel j...@arbash-meinel.com wrote:
Casey is the one to talk to. I'm not sure if he was just trying to be
conservative, but he did intentionally not want to pun the types. I
think he
On 25/07/14 03:26, Gustavo Niemeyer wrote:
Hey Ian,
On Thu, Jul 24, 2014 at 4:03 AM, Ian Booth ian.bo...@canonical.com wrote:
However, doing a session.Copy() each time the transaction log collection is
queried (every 5 seconds) causes a number of test failures when the host
machine
is
On Fri, Jul 25, 2014 at 1:02 AM, Ian Booth ian.bo...@canonical.com wrote:
We've transitioned to using Session.Copy() to address the situation whereby
Juju
would create a mongo collection instance and then continue to make db calls
against that collection without realising the underlying
That said, the goal is of course not to make the developer's life
miserable. All the driver wants is an acknowledgement that the error
was perceived and taken care of. This is done trivially by calling:
session.Refresh()
So in Juju now, we use session.Copy() which calls Refresh()
