Skip to content
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

A few questions related to appveyor #22

Closed
lelit opened this issue Aug 12, 2017 · 3 comments
Closed

A few questions related to appveyor #22

lelit opened this issue Aug 12, 2017 · 3 comments

Comments

@lelit
Copy link
Contributor

lelit commented Aug 12, 2017

Trying to get binary wheels built, tested and deployed from ci.appveyor.com, most of the things are going smoothly, except:

  1. In the appveyor log there are several fatal: BUG: setup_git_env called without repository messages in row, each taking as long as a whole minute to appear, just after cibuildwheel starts: is this something related to the tool, some bad setting on my side, or simply something I should not care about?
  2. Even if the CIBW_TEST_COMMAND appears in log (see here for the configuration), the command does not seem to be executed (on GNU/Linux the test suite takes several tens of seconds, I cannot believe that Windows can be so much faster 😈), nor it does produce some output
  3. The final twine upload exits with an error, even though it actually uploaded the win32 and win_amd64 wheels

Do you have any hint on how I could solve any of above?

Thank you in advance!

@joerick
Copy link
Contributor

joerick commented Aug 13, 2017

Hey there @lelit!

  1. fatal: BUG: setup_git_env called without repository

Git isn't used directly by cibuildwheel, so this must be coming from an invocation of git by pip, perhaps. It seems to be something that's occurred in a recent version of Git, and if I'm reading that thread right it's actually pretty harmless.

2 CIBW_TEST_COMMAND does not seem to be executed

That's strange, not something I've seen before. The config looks okay to me, perhaps add some verbosity to that command to see if you can see what's going on.

3 twine upload exits with an error

Windows thinks any output on stderr means the command failed, so that's why it looks bad. Actually the command succeeded so there's no need to worry :). Might be worth logging that as a bug on the twine repo (switching the log messages to stdout on Windows).

@joerick joerick closed this as completed Aug 13, 2017
@lelit
Copy link
Contributor Author

lelit commented Aug 13, 2017

Ok, thank you!

@lelit
Copy link
Contributor Author

lelit commented Aug 14, 2017

About the second point, the verbosity was already set to “detailed” in the appveyor's project settings, but that didn't make any difference wrt to what is logged in the console. For example, neither the output of python --version appears in the log.

Anyway, I realize this is most probably not related to cibuildwheel, so I will try to understand the issues without boring you :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants