-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
[AIRFLOW-4296][AIP-3-subtask-18] Remove py2 in ci process #5090
Conversation
This is already done and merged in master: |
@kaxil I rebase on master but PR-5019 and PR-5020 still failed. |
Restarted the CI |
Still failed, I try to fix it. |
@@ -19,7 +19,7 @@ | |||
|
|||
set -x | |||
|
|||
cd /usr/local/lib/python2.7/dist-packages/airflow && \ | |||
cd /usr/local/lib/python3.6/dist-packages/airflow && \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like this path should use python3.5
instead of python3.6
. Xenial LTS installs python3.5
unless we add a new PPA.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for catching. But I change base docker images to python:3.6-slim because we have a jira ticket in https://issues.apache.org/jira/browse/AIRFLOW-4210. And I think we should change our ci k8s as well.
59aa927
to
a4097bb
Compare
Add gcc because of failed in https://travis-ci.org/apache/airflow/jobs/520123725 |
a4097bb
to
9ccf73f
Compare
Codecov Report
@@ Coverage Diff @@
## master #5090 +/- ##
==========================================
- Coverage 77.23% 76.76% -0.48%
==========================================
Files 465 465
Lines 29837 29837
==========================================
- Hits 23046 22905 -141
- Misses 6791 6932 +141
Continue to review full report at Codecov.
|
1 similar comment
Codecov Report
@@ Coverage Diff @@
## master #5090 +/- ##
==========================================
- Coverage 77.23% 76.76% -0.48%
==========================================
Files 465 465
Lines 29837 29837
==========================================
- Hits 23046 22905 -141
- Misses 6791 6932 +141
Continue to review full report at Codecov.
|
CI green. But before merge I'd like to test if this change work in my personal repo https://github.com/zhongjiajie/airflow/tree/test_if_ci_work Travis CI log is here https://travis-ci.com/zhongjiajie/airflow/builds/108322089 I use this PR and cherry-pick #5020. submit https://github.com/zhongjiajie/airflow/tree/test_if_ci_work |
@zhongjiajie Still a sad CI :'( Can you rerun the job? |
Seem failed with un-related test https://travis-ci.com/zhongjiajie/airflow/jobs/192913602 |
https://travis-ci.com/zhongjiajie/airflow/builds/108333920 K8S ci pass, but postgre failed and I think the failed is un-related ======================================================================
46) ERROR: test_execution_limited_parallelism (tests.executors.test_local_executor.LocalExecutorTest)
----------------------------------------------------------------------
Traceback (most recent call last):
tests/executors/test_local_executor.py line 75 in test_execution_limited_parallelism
self.execution_parallelism(parallelism=test_parallelism)
tests/executors/test_local_executor.py line 61 in execution_parallelism
self.assertTrue(executor.event_buffer['fail'], State.FAILED)
KeyError: 'fail' And this postgre job sucess in https://travis-ci.com/zhongjiajie/airflow/builds/108322089 Should I restart the CI in my repo or just accept/review this PR |
@zhongjiajie can you restart the tests in your CI? Probably just a flaky test. |
@milton0825 I think is flaky test, but in job https://travis-ci.com/zhongjiajie/airflow/builds/108333920 we could found out K8S test job pass(we just want to prove K8S test pass). So I wonder if we could accept this PR |
lgtm |
Anything left to do on this? It looks good to me. |
PTAL @potiuk |
Yeah let's ship this as it blocks the PY2 deprecation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Hopefully I got to fix the last issue with multi-staging docker soon and we get rid of it altogether ;)
@potiuk Do you have the rights to merge PR now. I check my dev-email and notice you become committer. BTW Congratulations 👍 |
@potiuk Thanks for merging. |
@potiuk Notice that you don't change jira ticket status as RESOLVED, maybe you should take a look as #4966 (comment). FYI |
Yeah..I realised I have no necessary rights in JIRA yet. I am waiting for infra team to grant me the right. But I keep the list of tickets I merged so no worries ! Happy Easter :) |
Thanks @potiuk for picking this up. Happy Easter as well! 👍 |
Make sure you have checked all steps below.
Jira
Description
My PR #5020 CI failed, and the sample log https://api.travis-ci.org/v3/job/519213992/log.txt
And I found out we ci process still have py2, So remove
from __future__ import absolute_import
will cause error. This PR are try to fix this.Code Quality
flake8