[jira] [Commented] (AIRFLOW-7012) Travis CI + MySQL or Postgres + Python 3.7 fail most of the times
[ https://issues.apache.org/jira/browse/AIRFLOW-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054447#comment-17054447 ] ASF subversion and git services commented on AIRFLOW-7012: -- Commit 85465499074443fa98322051ca11f43c66242cc3 in airflow's branch refs/heads/master from Jarek Potiuk [ https://gitbox.apache.org/repos/asf?p=airflow.git;h=8546549 ] [AIRFLOW-7012] Split tests into providers/core to save memory (#7657) > Travis CI + MySQL or Postgres + Python 3.7 fail most of the times > - > > Key: AIRFLOW-7012 > URL: https://issues.apache.org/jira/browse/AIRFLOW-7012 > Project: Apache Airflow > Issue Type: Bug > Components: ci >Affects Versions: 2.0.0 >Reporter: Jarek Potiuk >Assignee: Jarek Potiuk >Priority: Major > Fix For: 2.0.0 > > > Seems that on Travis where we have MySQL + Postgres + Python 3.7 we have > often (but not always) failures resulting with "Lost connection to MySQL > server during query". Generally it seems to be connected to DNS lookup. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AIRFLOW-7012) Travis CI + MySQL or Postgres + Python 3.7 fail most of the times
[ https://issues.apache.org/jira/browse/AIRFLOW-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054446#comment-17054446 ] ASF GitHub Bot commented on AIRFLOW-7012: - potiuk commented on pull request #7657: [AIRFLOW-7012] Split tests into providers/core to save memory URL: https://github.com/apache/airflow/pull/7657 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Travis CI + MySQL or Postgres + Python 3.7 fail most of the times > - > > Key: AIRFLOW-7012 > URL: https://issues.apache.org/jira/browse/AIRFLOW-7012 > Project: Apache Airflow > Issue Type: Bug > Components: ci >Affects Versions: 2.0.0 >Reporter: Jarek Potiuk >Assignee: Jarek Potiuk >Priority: Major > > Seems that on Travis where we have MySQL + Postgres + Python 3.7 we have > often (but not always) failures resulting with "Lost connection to MySQL > server during query". Generally it seems to be connected to DNS lookup. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AIRFLOW-7012) Travis CI + MySQL or Postgres + Python 3.7 fail most of the times
[ https://issues.apache.org/jira/browse/AIRFLOW-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054430#comment-17054430 ] ASF GitHub Bot commented on AIRFLOW-7012: - potiuk commented on pull request #7657: [AIRFLOW-7012] Split tests into providers/core to save memory URL: https://github.com/apache/airflow/pull/7657 --- Issue link: WILL BE INSERTED BY [boring-cyborg](https://github.com/kaxil/boring-cyborg) Make sure to mark the boxes below before creating PR: [x] - [x] Description above provides context of the change - [x] Commit message/PR title starts with `[AIRFLOW-]`. AIRFLOW- = JIRA ID* - [x] Unit tests coverage for changes (not needed for documentation changes) - [x] Commits follow "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)" - [x] Relevant documentation is updated including usage instructions. - [x] I will engage committers as explained in [Contribution Workflow Example](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#contribution-workflow-example). * For document-only changes commit message can start with `[AIRFLOW-]`. --- In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md). Read the [Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines) for more information. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Travis CI + MySQL or Postgres + Python 3.7 fail most of the times > - > > Key: AIRFLOW-7012 > URL: https://issues.apache.org/jira/browse/AIRFLOW-7012 > Project: Apache Airflow > Issue Type: Bug > Components: ci >Affects Versions: 2.0.0 >Reporter: Jarek Potiuk >Assignee: Jarek Potiuk >Priority: Major > > Seems that on Travis where we have MySQL + Postgres + Python 3.7 we have > often (but not always) failures resulting with "Lost connection to MySQL > server during query". Generally it seems to be connected to DNS lookup. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (AIRFLOW-7012) Travis CI + MySQL or Postgres + Python 3.7 fail most of the times
[ https://issues.apache.org/jira/browse/AIRFLOW-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054384#comment-17054384 ] ASF GitHub Bot commented on AIRFLOW-7012: - potiuk commented on pull request #7654: [AIRFLOW-7012] Swap MySql for Postgres in Python 3.7 tests URL: https://github.com/apache/airflow/pull/7654 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Travis CI + MySQL or Postgres + Python 3.7 fail most of the times > - > > Key: AIRFLOW-7012 > URL: https://issues.apache.org/jira/browse/AIRFLOW-7012 > Project: Apache Airflow > Issue Type: Bug > Components: ci >Affects Versions: 2.0.0 >Reporter: Jarek Potiuk >Assignee: Jarek Potiuk >Priority: Major > > Seems that on Travis where we have MySQL + Postgres + Python 3.7 we have > often (but not always) failures resulting with "Lost connection to MySQL > server during query". Generally it seems to be connected to DNS lookup. -- This message was sent by Atlassian Jira (v8.3.4#803005)
