Databases
StackOverflow2013
Postsdbo
POHudson CI can't reach MySQL Server
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHudson CI can't reach MySQL Server
    text
    copied!<p>I have multiple unit tests that have to connect to a MySQL Server to retrieve or modify data (I know this is more like integration tests, but let's not dive into that for now). The full suite of NUnit tests pass with no issues both in NUnit GUI and in NUnit console.</p> <p>I am now automating our build process using Hudson Continuous Integration. As part of that I introduced this batch command that will invoke NUnit console to execute the tests just after building the full solution:</p> <pre><code>"C:\Program Files (x86)\NUnit 2.5.10\bin\net-2.0\nunit-console.exe" /framework:net-4.0 Tests\MyTestProject\bin\Debug\MyTestProject.dll /xml=MyTestProject.dll.xml /config:Debug exit 0 </code></pre> <p>It should just work but what I get is this exception for all the tests tha connect to the database server:</p> <p><strong>MySql.Data.MySqlClient.MySqlException : Unable to connect to any of the specified MySQL hosts.</strong></p> <p>So Hudson just can't reach the MySQL Server, even when the connection string is the same as if I executed the tests manually. Hudson and the server are in the same machine by the way, which is actually my dev box for now. Also, the few tests that do not need the database will pass with no problems.</p> <p>Why Hudson can't reach the MySQL Server?</p> <p><strong>UPDATE:</strong> Not all tests are failing, but only the tests that use a connection string that require Shared Memory, like this:</p> <pre><code>server=localhost;user id=root;pooling=false;persist security info=true;connection reset=true;allow user variables=true;password=;protocol=sharedmemory; shared memory name=MYSQL </code></pre> <p>Tests that do not include sharedmemory successfully pass.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload