-
-
Notifications
You must be signed in to change notification settings - Fork 919
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
BF (codename "happy travis"): trying to address lints etc to make Travis green again #702
BF (codename "happy travis"): trying to address lints etc to make Travis green again #702
Conversation
I did keep some "bare" except with catch all Exception: , while tried to disable flake8 complaints where clearly all exceptions are to be catched
Codecov Report
@@ Coverage Diff @@
## master #702 +/- ##
==========================================
+ Coverage 92.83% 94.35% +1.51%
==========================================
Files 61 61
Lines 10152 10136 -16
==========================================
+ Hits 9425 9564 +139
+ Misses 727 572 -155
Continue to review full report at Codecov.
|
9a3fd7a
to
42e89cc
Compare
Travis is happy now, fighting with windows |
my question would be -- did hooks ever work on windows??? or tests were testing only that they "fail to work"? ;) |
the last succesful build on appveyor was https://ci.appveyor.com/project/Byron/gitpython/build/1.0.161 -- at that point there where no tests for succesful hooks execution. So AFAIK they never worked, and I am offloading that for future to #703 . In this one I will skip those tests tests to establish a reliable baseline for now |
Kudos to tour efforts and happy fighting ;-) Regarding hooks, at the time of #519 and for some months later all remaining test-cases were passing on Windows, e.g. https://ci.appveyor.com/project/ankostis/gitpython/build/1.0.433 BTW you may check if your recent efforts have fixed some of those long disabled TCs. |
@ankostis -- join the "fun"! but I think/hope I am "done" hooks -- as of https://ci.appveyor.com/project/ankostis/gitpython/build/1.0.433 you reference, there were no test for testing successful execution of a hook on windows . Thanks for the pointer to As for the 'check' -- someone should just check if there is a similar to travis |
But in the future (after we are green again), it would be nice if no PR was merged if tests fail... |
add36d5
to
4d851a6
Compare
woohoo -- some of the windows environments are green now! rebuilding to see if some spurious one didn't creep in. any immediate clue about what could be wrong in those anaconda windows ones @ankostis ? |
ok, @Byron , @ankostis et al, it is ready for the review. I will leave the appveyor crusade for later/someone else ATM (note a handy addition to .appveyor.yml) - at least some environments are in clear there as well, and travis is all green. Would be nice to establish the baseline of passing CI in master. |
I think it is not anaconda to blame but rather Cygwin's Git! For instance in |
Yikes |
|
Well... would be nice to get it reviewed/merged at this stage of success so that at least some baseline is established back again, and then tackle cygwin in a more dedicated PR ;) |
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's important to get at least one CI green.
@@ -139,7 +139,7 @@ def repo_creator(self): | |||
try: | |||
try: | |||
return func(self, rw_repo) | |||
except: | |||
except: # noqa E722 |
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.
How about except Exception:
like elsewhere?
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.
We could. But at this out-most level of handling execution, I thought to remain as "greedy" as possible. May be someone (among used dependencies) still manages to raise non-Exception "exceptions" up the chain from somewhere/somehow -- so I thought to remain catching them as well. In the other places it was more "specific" to not expect some complete weird stuff being thrown up. But if you insist, we could have it Exception here as well
@@ -296,7 +296,7 @@ def remote_repo_creator(self): | |||
with cwd(rw_repo.working_dir): | |||
try: | |||
return func(self, rw_repo, rw_daemon_repo) | |||
except: | |||
except: # noqa E722 |
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.
How about except Exception:
like elsewhere?
@yarikoptic Thanks so much for hanging into this! Especially your crusade to get the windows CI green is particularly brave!! @ankostis certainly has a tale to tell there, too! |
Thanks @Byron , I hope you will have a nice (and productive in all regards) vacation!
I usually (for other projects) "tag -s" releases locally, push the tags, create release out of them on github I am yarikoptic on pypi |
> pub rsa4096/A2DE235062DA33FA 2010-06-07 Yaroslav Halchenko (Yarik) <yoh@onerussian.com> > Primary key fingerprint: C5B9 05F0 E8D9 FD96 68FF 366F A2DE 2350 62DA 33FA As per #702 (comment)
@yarikoptic Thanks - I added you to the list of maintainers on PyPi and your key to the |
oh yeah, I would prefer not to release unless I really have to ;) so I am ok to stay in training for as long as it could be ;-) |
…travis BF (codename "happy travis"): trying to address lints etc to make Travis green again
> pub rsa4096/A2DE235062DA33FA 2010-06-07 Yaroslav Halchenko (Yarik) <yoh@onerussian.com> > Primary key fingerprint: C5B9 05F0 E8D9 FD96 68FF 366F A2DE 2350 62DA 33FA As per gitpython-developers#702 (comment)
Some minor RFings did creep in, hopefully I didn't change any logic (tests will show ;) ).