-
-
Notifications
You must be signed in to change notification settings - Fork 216
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
Timeout with version >= 8 #943
Comments
The timeout will be increased,we learned that girl sometimes takes up to 25s,which exceeds the 20 |
I suggest to remove the timeout or make it configurable/removable via an environment variable. The git commands can sometimes be quite slow, which may largely depend on the system (for example when using Windows, VMs, or Docker containers). |
…-on-github fix #943: extend default timeout to account for github ci issues
Unfortunately, the new error message is |
@anakin87 can the issue be sidestepped by involving hg before invoking the build step? |
@RonnyPfannschmidt thanks for the help... I'm not an expert, but my impression is that I can do very little, If I am talking nonsense, please correct me and give me a suggestion... |
@anakin87 hg root is a command that takes less than a second,if it happens in your environment then sometimes just running the command can fix the issue wrt delay |
Hello!
This issue is similar to #913.
Background
Our package (
farm-haystack
) depends on an unmaintained package:seqeval
, which usessetuptools_scm
.seqeval
has the following configuration for setup (see setup.py):setup configuration
Error
As of the release of
setuptools_scm
8.0,the installation of
seqeval
started to randomly fail on GitHub CI (usingwindows-latest
).Error message
The problem seems related to the recently introduced timeout of 20 seconds (#808).
It would be great if you could help or suggest a workaround...
The text was updated successfully, but these errors were encountered: