-
Notifications
You must be signed in to change notification settings - Fork 92
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
Github Actions - expand test matrix, unify coverage reports #207
Comments
asedeno
added a commit
to asedeno/xapian-haystack
that referenced
this issue
Sep 25, 2021
asedeno
added a commit
to asedeno/xapian-haystack
that referenced
this issue
Sep 26, 2021
asedeno
added a commit
to asedeno/xapian-haystack
that referenced
this issue
Sep 26, 2021
asedeno
added a commit
to asedeno/xapian-haystack
that referenced
this issue
Sep 26, 2021
claudep
pushed a commit
that referenced
this issue
Sep 26, 2021
PSzczepanski1996
pushed a commit
to PSzczepanski1996/xapian-haystack
that referenced
this issue
Jul 23, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With Travis, we were testing the following combinations:
Python: [3.6, 3.7, 3.8. 3.9]
Django: [2.2, 3.0, 3.1, 3.2]
Xapian: [1.4.9]
We've bumped Xapian up to 1.4.18, but dropped the rest of our coverage to just Python 3.6 and Django 2.2.
I don't know that we need to cover multiple Xapian versions right now. Expanding that will probably make sense in the face of a Xapian 1.6.x or 2.0.x. We should definitely expand the Python and Django coverage again, though we can drop Django 3.0.
If we grow the matrix of builds, we'll want to rework how coverage works again. We'll want to tell coveralls that parallel tests are in progress and when they're complete.
The text was updated successfully, but these errors were encountered: