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
Would you be interested in a PR that fixes CI for coilmq?
CI builds are not running anymore because this project (as far as I can tell) isn't yet configured to have CI run on travis-ci.com. travis-ci.org no longer does builds.
Unfortunately, the builds would fail even if they were running on the new travis-ci site. I forked coilmq to work on #29 and enabled travis-ci for the fork. My results look pretty much the same as when CI ran most recently against your repo for #28.
Pinning the fakeredis dependency to an earlier version may fix the problem with the python 2.7 build failures. Or, it may require listing a package multiple times in one of the requirements files and adding different environment markers to each. For example, fakeredis < X.Y.Z; python_version <= '2.7' and fakeredis >= X.Y.Z; python_version > '2.7'. If a quick fix like these can't be made to work, I could set you up with tox -- a little more involved but, IMHO, very worthwhile.
The text was updated successfully, but these errors were encountered:
Thanks so much, Eric. I love that someone has taken interest in this
science project :). Feel free to take this in whatever direction you think
makes sense.
Would you be interested in a PR that fixes CI for coilmq?
CI builds are not running anymore because this project (as far as I can tell) isn't yet configured to have CI run on travis-ci.com. travis-ci.org no longer does builds.
Unfortunately, the builds would fail even if they were running on the new travis-ci site. I forked coilmq to work on #29 and enabled travis-ci for the fork. My results look pretty much the same as when CI ran most recently against your repo for #28.
Pinning the fakeredis dependency to an earlier version may fix the problem with the python 2.7 build failures. Or, it may require listing a package multiple times in one of the requirements files and adding different environment markers to each. For example,
fakeredis < X.Y.Z; python_version <= '2.7'
andfakeredis >= X.Y.Z; python_version > '2.7'
. If a quick fix like these can't be made to work, I could set you up with tox -- a little more involved but, IMHO, very worthwhile.The text was updated successfully, but these errors were encountered: