I updated the wiki. The Start-BitsTransfer step downloaded the old archive.
The mongo-static.zip contains a statically built mongo with ssl enabled. I installed a system from scratch and after following the steps on the wiki, and got to mongo the result was: PS C:\Users\Administrator> .\mongod.exe --version db version v2.6.3 2015-04-03T11:56:04.678-0700 git version: 255f67a66f9603c59380b2a389e386910bbb52cb 2015-04-03T11:56:04.678-0700 OpenSSL version: OpenSSL 0.9.8r 8 Feb 2011 If its not too much trouble, can you give it another shot? (if you have a snapshot of a vanilla windows install and time of course) Cheers, Gabriel ________________________________ From: John Meinel [[email protected]] Sent: Wednesday, April 01, 2015 9:55 PM To: Gabriel Samfira Cc: [email protected] Subject: Re: Testing on windows The one I have says it was "Date Modified" 2015-03-22 and is 18,136KB in size. (mongo-static.zip is 6,934 KB). John =:-> On Wed, Apr 1, 2015 at 10:54 PM, John Meinel <[email protected]<mailto:[email protected]>> wrote: I did get it from the wiki, and the link said "static", however, it did still complain that I didn't have OpenSSL. Perhaps a build step was missed on the latest one and it wasn't noticed because the OpenSSL library was on the machine you were testing on? John =:-> On Wed, Apr 1, 2015 at 8:49 PM, Gabriel Samfira <[email protected]<mailto:[email protected]>> wrote: Hi John, OpenSSL was needed for mongo, but I have since recompiled mongo statically. So if you got the binary from the wiki, OpenSSL should no longer be needed as a mandatory dependency. I will not be able to try and reproduce the error today, but I will have a look at that particular test tomorrow. Cheers, Gabriel ________________________________ From: John Meinel [[email protected]<mailto:[email protected]>] Sent: Wednesday, April 01, 2015 1:46 PM To: Gabriel Samfira Cc: [email protected]<mailto:[email protected]> Subject: Re: Testing on windows ... I did end up getting some tests running (though I did get a "charm not found" failure). It did end up getting killed with "test ran to long" after 10 min. For those following along it was cmd/juju DeploySuite.TestUpgradeCharmDir<https://bugs.launchpad.net/juju-core/+bug/1439112> that failed. John =:-> So it seems the doc is slightly incomplete, but mostly there. John =:-> On Thu, Mar 19, 2015 at 5:40 AM, Gabriel Samfira <[email protected]<mailto:[email protected]>> wrote: Hello folks, It has come to my attention that there may be some confusion in regards to some Windows testing. There have been a couple of branches that have merged which break windows tests in juju-core. I would like to remind everyone that there is a guide available at: http://wiki.cloudbase.it/juju-testing that will help you set up a testing environment on Windows. Also, if there are any questions regarding Windows weirdness, please feel free to contact me on irc (gsamfira) or bogdanteleaga. We will be more then happy to help you navigate any Windows issues you might have. Kind regards, Gabriel -- Juju-dev mailing list [email protected]<mailto:[email protected]> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
