-
Notifications
You must be signed in to change notification settings - Fork 40
Specify library version in Pipfile #1320
Comments
I've noticed that you don't have an integrated CI mechanism. Do you have plans to do that? This would definitely improve code quality as well as issues with libraries (at least the ones you can easily catch...). |
In the meantime, we have daily runs on hardware, which isn't perfect but is the best we can do at the moment. |
Well, it sounds like an extremely difficult task to be honest. Sounds like that you need to write another GUI Automating to test the GUI Automating tool 🤣 In all seriousness though, I mostly meant to test the whole bootstrap process and the library dependencies, in the lowest operating level possible, to ensure that everything works as expected and verify new versions. |
@wizofe That's a good idea and is probably achievable, since the problems we encounter happen later when the actual tests are running. |
I am encountering some errors when modifying the Pipfile and trying to do a
It seems to be a Critical Bug on Pipenv side: pypa/pipenv#2320 Update: |
2nd Update: After updating Pipenv to the latest version that has the fix for the error previously posted, we receive another error that has to do with all
|
I opened an issue on Pipenv side: pypa/pipenv#3187 |
Following up after the issue that was posted on Pipenv side (pypa/pipenv#3187), it seems that the errors have to do with the objective c wrappers (pyobjc libraries), and they suggested to open an issue on On my side I came up with a more clean solution that I think would benefit the project. And regarding the I cleaned up the @mwobensmith let me know what you think about the changes. They are ready for review on branch |
Thanks Matt ! Updated the branch and created a PR: https://github.com/mozilla/iris/pull/1454 |
Update: Changes were merged ! |
Adding a quick fix: https://github.com/mozilla/iris/pull/1455/files |
Code approved |
We should make sure that we lock down compatible library versions to known good releases, to avoid introducing regressions when a library has a bug.
We will then periodically run the project with current versions, and update this file when we are confident that there are no issues.
The text was updated successfully, but these errors were encountered: