You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The mysql-operator tests are failing since canonical/mysql-operator#192 was merged, which removes the requirements.txt file from that repo and puts dependencies in pyproject.toml. Presumably they'll be doing the same with the other db charms soon too, so we need to find a workaround. Example failure:
> sed -i -e "/^ops[ ><=]/d" -e "/canonical\/operator/d" -e "/#egg=ops/d" requirements.txt
> echo -e "\ngit+$GITHUB_SERVER_URL/$GITHUB_REPOSITORY@$GITHUB_SHA#egg=ops" >> requirements.txt
> shell: /usr/bin/bash -e {0}
sed: can't read requirements.txt: No such file or directory
The text was updated successfully, but these errors were encountered:
benhoyt
added a commit
to benhoyt/operator
that referenced
this issue
Aug 3, 2023
* Only try to edit `requirements.txt` if it exists
* If `requirements.txt` does not exist, then assume that the requirement is in `pyproject.toml` and edit that instead
* Enable the integration tests with `mysql-operator` and `mysql-k8s-operator` again
* Remove the `static-charm` tox runs from the DB workflow, as none of the DB operators have one defined
* Pin `tox` to anything compatible with 4.2
Fixes#987.
The mysql-operator tests are failing since canonical/mysql-operator#192 was merged, which removes the
requirements.txt
file from that repo and puts dependencies inpyproject.toml
. Presumably they'll be doing the same with the other db charms soon too, so we need to find a workaround. Example failure:The text was updated successfully, but these errors were encountered: