-
Notifications
You must be signed in to change notification settings - Fork 28k
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
[BUILD] refactor dev/lint-python in to something readable #22994
Conversation
Test build #98656 has finished for PR 22994 at commit
|
Test build #98657 has started for PR 22994 at commit |
test this please |
Test build #98658 has started for PR 22994 at commit |
test this please |
Test build #98659 has finished for PR 22994 at commit
|
Test build #98661 has finished for PR 22994 at commit
|
test this please |
Test build #98662 has started for PR 22994 at commit |
Test build #98664 has started for PR 22994 at commit |
see the output from the following build to get the gory details of what's happening: i removed |
Test build #98665 has started for PR 22994 at commit |
test this please |
Test build #98666 has finished for PR 22994 at commit
|
test this please |
Test build #98667 has started for PR 22994 at commit |
Test build #98668 has started for PR 22994 at commit |
Test build #98669 has finished for PR 22994 at commit
|
test this please |
Test build #98673 has finished for PR 22994 at commit
|
I agree with this change in general. The current script is a total mess - I will try to help take a look when the tests pass. BTW, it would be awesome if PR description contains what this PR tries to fix later when the tests pass |
i have no idea why the tests aren't passing btw. :\ |
test this please |
1 similar comment
test this please |
Test build #98687 has finished for PR 22994 at commit
|
Test build #98688 has finished for PR 22994 at commit
|
test this please |
Test build #98733 has finished for PR 22994 at commit
|
alright, i think we're g2g. i'll squash my commits now before this is merged. |
author shane knapp <incomplete@gmail.com> 1541791117 -0800 committer shane knapp <incomplete@gmail.com> 1542135008 -0800 parent 6cd2348 author shane knapp <incomplete@gmail.com> 1541791117 -0800 committer shane knapp <incomplete@gmail.com> 1542134986 -0800 parent 6cd2348 author shane knapp <incomplete@gmail.com> 1541791117 -0800 committer shane knapp <incomplete@gmail.com> 1542134619 -0800 this is serious refactor add tracing fixing some problems print out a happy success message add underscore to flake8 executable definition adding quotes around passed variable to properly test adding more quotes around passed variable to properly test even more quotes i know which python we use now, removing debugging adding spaces around shell escapes apparently quoting these doenst work as advertised final round of cleanup and formatting removing set -x output readability more output cleanup more more output cleanup add tracing add underscore to flake8 executable definition adding quotes around passed variable to properly test even more quotes i know which python we use now, removing debugging apparently quoting these doenst work as advertised final round of cleanup and formatting removing set -x output readability extra space removed more output cleanup more more output cleanup
1f5c2f5
to
2a3a0e1
Compare
Test build #98790 has finished for PR 22994 at commit
|
(weird, github ate my last comment) @HyukjinKwon i think we're g2g for merging this in to master and backports. you want to do this, or should i? |
I haven't taken a look super closely but the idea looks itself okay. Is it urgent? if yes, yup. I don't object to go ahead right away. Otherwise, might be good to leave open for few days for review comments .. Let me leave some cc's for @srowen, @felixcheung, @holdenk .. |
nah, it's not urgent at all.
i also tested this locally by breaking various python scripts and
confirming that it caught errors as expected.
…On Tue, Nov 13, 2018 at 5:03 PM Hyukjin Kwon ***@***.***> wrote:
I haven't taken a look super closely but the idea looks itself okay. Is it
urgent? if yes, yup. I don't object to go ahead right away. Otherwise,
might be good to leave open for few days for review comments ..
Let me leave some cc's for @srowen <https://github.com/srowen>,
@felixcheung <https://github.com/felixcheung>, @holdenk
<https://github.com/holdenk> ..
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#22994 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABiDrPDJEYKTATyZjlJPnmGjllCBkTb5ks5uu2vFgaJpZM4YXXiK>
.
|
howdy howdy! i opened this nearly 2 weeks ago, and was wondering if i could get another set of eyeballs on it... |
I don't know this script well enough nor Python to really comment, but if it works, push it. |
okie dokie... this will be my first official push to the spark repo! :) |
gonna hold off on backporting until i inspect each branch independently. |
## What changes were proposed in this pull request? `dev/lint-python` is a mess of nearly unreadable bash. i would like to fix that as best as i can. ## How was this patch tested? the build system will test this. Closes apache#22994 from shaneknapp/lint-python-refactor. Authored-by: shane knapp <incomplete@gmail.com> Signed-off-by: shane knapp <incomplete@gmail.com>
This was merged to master (and branch-3.0). |
What changes were proposed in this pull request?
dev/lint-python
is a mess of nearly unreadable bash. i would like to fix that as best as i can.How was this patch tested?
the build system will test this.