-
Notifications
You must be signed in to change notification settings - Fork 10
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
GenoCAE build fails due to upstream update #26
Comments
I got this to work at richelbilderbeek@0dc24d1 . Happily closing this Issue! |
richelbilderbeek
pushed a commit
to richelbilderbeek/GenoCAE
that referenced
this issue
Feb 14, 2022
richelbilderbeek
pushed a commit
to richelbilderbeek/GenoCAE
that referenced
this issue
Feb 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dear GenoCAE maintainers, hi Carl and Kristiina,
Thanks for GenoCAE and its tests using GitHub Actions, showing off how awesome it is!
However, upstream something has happened that cause the builds of all of my Python-dependent work to fail. Sadly, it happened to GenoCAE as well. As you are superior with Python, I hope you will help me/us :-)
Currently, the last GitHub Action trigger of the repo passed, which was (as of today) 5 days ago. That seems great! However, today this build fails. I figured this out by simpling forking this repo and trigger a rebuild. From the GitHub Actions log one can read:
The problem is obviously:
I have been trying all day to fix this, but I did not dare to meddle with
requirements.txt
. I will continue trying, yet I hope you will beat me fix this 😇The text was updated successfully, but these errors were encountered: