-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
CI: SQL tests on py38 slow build #38429
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
Labels
CI
Continuous Integration
IO SQL
to_sql, read_sql, read_sql_query
Needs Discussion
Requires discussion from core team before further action
Comments
fangchenli
pushed a commit
to fangchenli/pandas
that referenced
this issue
Dec 21, 2020
jreback
pushed a commit
that referenced
this issue
Dec 21, 2020
meeseeksmachine
pushed a commit
to meeseeksmachine/pandas
that referenced
this issue
Dec 21, 2020
jreback
pushed a commit
that referenced
this issue
Dec 21, 2020
Co-authored-by: Fangchen Li <[email protected]>
this is closed by #38613 right? |
If we've decided to not test SQL on py38 slow, this can be closed. |
can u see how much slow sql tests we have - meaning are we testing slow sql in at least 1 build? |
luckyvs1
pushed a commit
to luckyvs1/pandas
that referenced
this issue
Jan 20, 2021
Co-authored-by: VirosaLi <2EkF8qUgpNkj>
We're testing SQL in GHA on Linux for PY3.8/3.9/3.10, so we have sufficient coverage now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
CI
Continuous Integration
IO SQL
to_sql, read_sql, read_sql_query
Needs Discussion
Requires discussion from core team before further action
In #38344, we found that SQL tests were not run on py38 slow build. Currently, we are testing SQL on py37-locale and py37-coverage. If that is enough, we could move py38-slow to Azure. Otherwise, we could add more builds for SQL.
The text was updated successfully, but these errors were encountered: