Yes it has :).
On 19.03.2015 13:30, David Cheney wrote:
It is clear that we need blocking CI jobs for Windows and CentOS --
has this been added to the Nuremberg agenda ?
On Thu, Mar 19, 2015 at 10:24 PM, Gabriel Samfira
gsamf...@cloudbasesolutions.com wrote:
On 19.03.2015 12:07, Michael
It is clear that we need blocking CI jobs for Windows and CentOS --
has this been added to the Nuremberg agenda ?
On Thu, Mar 19, 2015 at 10:24 PM, Gabriel Samfira
gsamf...@cloudbasesolutions.com wrote:
On 19.03.2015 12:07, Michael Foord wrote:
Do all tests pass (or skip) on Windows now? Do we
Hi folks,
A branch I landed yesterday broke all the upgrade tests. This was a
branch that added a new login version.
Since 1.23 writes the environment UUID to the agent config, I had
wrongly assumed that it would all be good.
This has now been rectified with commit b56d0a30
Tim,
You can find logs for several upgrade jobs at
http://reports.vapour.ws/releases/2464
Sadly, logs for some jobs are missing and we can work to improve this but
there are log links available if you hover your mouse over the links in the
Last Build column for the following test jobs:
On 19 March 2015 at 15:48, Nate Finch nate.fi...@canonical.com wrote:
Wayne and I (and Horacio for some of the time) wasted a few days trying to
figure out a problem with the watcher we'd created. Turns out, the problem
was a missing 's':
On 19 March 2015 at 15:48, Nate Finch nate.fi...@canonical.com wrote:
Wayne and I (and Horacio for some of the time) wasted a few days trying to
figure out a problem with the watcher we'd created. Turns out, the problem
was a missing 's':
Hey Aaron,
I was unable to replicate the huge number of errors regarding temporary files
already existing. Can you make sure you %TMP% directory is clean when you start
testing? If its a fresh instance, it should have no files in %TMP%.
Or have the testing job simply clean the entire directory
That would we awesome! I was thinking along the same lines.
-eric
On Thu, Mar 19, 2015 at 8:51 AM, Gabriel Samfira
gsamf...@cloudbasesolutions.com wrote:
That is actually a great idea :). We can try and do this in Nuremberg next
month ;). We have some tooling to do an unattended install. We
Thanks for bringing this up. And thanks to Bogdan (and anyone else
involved) for writing up that great walkthrough! I had expected it to
be more complicated. I'm going to be running the unit tests on
windows from now on. :) I'm sure I've broken then a bunch in the last
couple weeks.
What
https://github.com/jijeshmohan/janus
Disclaimer: I haven't looked at this too closely.
Came across this the morning. If we want to maintain test-doubles, this
looks like a nice, declarative, way to specify mock responses from a local
server.
-
Katherine
--
Juju-dev mailing list
# juju-core 1.22.0
A new stable release of Juju, juju-core 1.22.0, is now available.
This release replaces 1.21.3.
## Getting Juju
juju-core 1.22.0 is available for utopic and backported to earlier
series in the following PPA:
https://launchpad.net/~juju/+archive/stable
Windows and OS X
https://github.com/juju/juju/issues/1880
Adam Stokes brought this up in the cross team call today. Evidently it's
actually a (really really old) Ubuntu bug, but of course it affects Juju
when deploying on Ubuntu. This seems like the sort of thing that really
should be fixed by Ubuntu, but if we
I ran into a similar type of issue recently. I discussed very briefly with
John M. and William, and I think a good thing to do would be to hide the
generic RegisterResource method, and only expose methods which take the
interface types. This would convert these types of issues from runtime to
13 matches
Mail list logo
