-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TST: enable MySQL tests #6613
TST: enable MySQL tests #6613
Conversation
@jreback Is there a way to see if the tests are not skipped anymore on Travis? (because before they were) I just see 'Ran 4980 tests in 266.519s OK (SKIP=107)' Can I see which are the 107 skipped? |
go to the build |
ah yes, I see, the print_skipped. Thanks! And they are not skipped anymore, and passing! |
looks good |
also enabled on the windows builds..... merge when ready |
Nice! |
@jorisvandenbossche all good with me |
TST: enable MySQL tests
I got this to work on windows (and all tests pass). Oracle makes this EXTRA hard to download setup the server! postgres so much easier! |
I think you should catch these tests and skip secondarily these tests take a LONG time on windows! 150s!
|
Yes, catching the errors is on the to do list in #6292. For the time, I experienced it as very varying, but the last time I ran them on Windows (all sql tests), it was 26 s for 80 tests. I think one way to speed up the tests is maybe just making the connection and test tables once for one test class, and not for every test seperately (using |
Are there examples in the code base how the OperationalError can be catched in the tests? |
look in utils/testing.py at the |
Something funny going on... I though its only the MySQLAlchemy tests that take an exceptional amount of time, the other (and postgres) are pretty fast. I though tit was 0.8.3 that was not compiled with c-extensions (as I had originally did pip install), but I just installed the binaries of 0.9.3
|
@jreback What if you only run the PostgreSQLAlchemy tests? Are these faster than the MySQLAlchemy? |
It seems to be going faster after some runs of the tests, but now (on Windows) I get 25s for both PostgreSQL and MySQL tests, and 8-9 s for without MySQL. |
Postgres is fine about 10s on my machine that's why I am thinking its a setting on the MySQL server but nothing obvious it's just a stock setup |
Is it a problem for the test suite? (for testing on travis, that it takes to long)? For speeding up the tests, possible things to explore:
|
it's quite fast on Travis and since Postgres is fast I am thinking maybe it's some setting specific to MySQL seems really odd your suggestions are good but prob don't need to optimize the testing as a high priority |
PR to fix and enable the MySQL tests for the new sql functionality.
coerce_float
arg. This is now OK.We should maybe add somewhere in the sql docs an overview of the limitations of the type conversion.