On 13/05/17 02:00, [email protected] wrote:
----------------------------------------------------------------------
Message: 1
Date: Fri, 12 May 2017 18:41:19 +1000
From: Brian May <[email protected]>
To: [email protected]
Subject: [melbourne-pug] Mysql Server has gone away
Message-ID: <[email protected]>
Content-Type: text/plain
Hello,
For my personal Django based project, I am getting random test failures
on Travis, e.g.:
https://travis-ci.org/brianmay/spud/jobs/231462150
OperationalError: (2006, 'MySQL server has gone away')
The usual culprit for the message - that the server closed its
connection due to idle time out and we didn't reconnect as we were
suppose to - doesn't seem to be applicable for a sequence of automated
tests - most if not all requiring db access.
If I click restart job, it almost certainly will succeed.
I only seem to have problems with MySQL. I am inclined to disable the
mysql tests, on the assumption that is is brokenness inside Django mysql
drivers or mysql.
First I thought I would check here.
Regards.
Hey Ben,
Are you able to check if you're reaching the connection limits somehow?
It might be that you're exhausting the pool. That's the first thing I
would try; increase the pool size to see if it has any effect and that
would tell me how to proceed in finding the problem.
I usually advise that people stay away from mysql due to negative
personal experience. Or you might be right that there's something broken
within the driver. But unless your tests are doing some black magic, an
error like this(connection issue so everyone using mysql would face) is
likely to have a simpler explanation.
--
Regards,
Alaa Salman
+61413852057
http://www.codedemigod.com
_______________________________________________
melbourne-pug mailing list
[email protected]
https://mail.python.org/mailman/listinfo/melbourne-pug
