Skip to content

CI: Fix ci flake error #37938

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

Merged
merged 11 commits into from
Nov 18, 2020
Merged

Conversation

charlesdong1991
Copy link
Member

@charlesdong1991 charlesdong1991 commented Nov 18, 2020

@charlesdong1991 charlesdong1991 added the CI Continuous Integration label Nov 18, 2020
@charlesdong1991 charlesdong1991 added this to the 1.2 milestone Nov 18, 2020
@jreback
Copy link
Contributor

jreback commented Nov 18, 2020

hmm on master, ok thanks

@charlesdong1991
Copy link
Member Author

charlesdong1991 commented Nov 18, 2020

@jreback I think an issue needs to be created to address this, it is the second time this happened: basically flake8 check doesn't detect imported but unused cases in feature PR, only detect the error once PR being merged to master.

Have seen it in #37923 and in #37703 , so ci checks ran successfully in those feature PRs, but actually they should have detected this unused import.

@jreback
Copy link
Contributor

jreback commented Nov 18, 2020

hmm interesting, cc @MarcoGorelli

@jbrockmendel
Copy link
Member

when ive seen this in the past it has involved multiple PRs which independently are each correctly passed by flake8, only causing a problem when both are merged

@MarcoGorelli
Copy link
Member

MarcoGorelli commented Nov 18, 2020

when ive seen this in the past it has involved multiple PRs which independently are each correctly passed by flake8, only causing a problem when both are merged

I think this is the issue - in #37584 I got this exact error during the PR CI


IMO this makes the case for always asking to merge master rather than restarting CI jobs manually

@charlesdong1991
Copy link
Member Author

ehh, okay, i thought of this scenario as well, but just feel surprised to come across them twice recently

thanks @MarcoGorelli @jbrockmendel shall I close the issue?

@MarcoGorelli
Copy link
Member

I'll just dig through the logs to try to verify that that's actually what happened

Just for reference, the exact same command is run during CI for both PRs and builds from master:

pre-commit run --show-diff-on-failure --color=always --all-files

@charlesdong1991
Copy link
Member Author

charlesdong1991 commented Nov 18, 2020

i closed #37940

thanks for checking out! @MarcoGorelli

@MarcoGorelli
Copy link
Member

MarcoGorelli commented Nov 18, 2020

OK, got it - 3 days ago, Brock opened #37872 and #37865, both of which removed an instance of Label from pandas/core/indexes/period.py .

#37872 was merged first. Then, a couple of days later, #37865 was merged, without it having been updated with changes from master - so its own CI was still green, but when it was merged, both instances of Label were gone and the CI check turned red

@MarcoGorelli
Copy link
Member

Anyway, this looks right and passes relevant checks - merging so the CI checks are fixed

@MarcoGorelli MarcoGorelli merged commit a170e97 into pandas-dev:master Nov 18, 2020
@charlesdong1991 charlesdong1991 deleted the fix_ci_flake branch November 18, 2020 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants