-
Notifications
You must be signed in to change notification settings - Fork 387
Address test failures and remove some xfails #2114
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
Conversation
greglucas
commented
Dec 13, 2022
- Add an xfail when parsing bad XML for the two recent tests that are failing now.
- owslib 0.20 was released over two years ago now and fixed some of the reasons for test failures so we can remove some xfails that should always pass.
It seems our circleCI build is fundamentally broken? |
0e6e2bb
to
eb1b17c
Compare
I'm not sure what happened there... I think it is back now. |
This release fixed some broken tests that we were xfailing, so we can remove the xfails as well.
eb1b17c
to
55aa87a
Compare
There is no winning with our test suite :) Appveyor is now failing on an unrelated test. |
@@ -191,7 +191,6 @@ def world_file_extent(*args, **kwargs): | |||
return extent, pix_size | |||
|
|||
|
|||
@pytest.mark.xfail(reason='MapQuest is unavailable') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is the test failing on AppVeyor?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahh, yes, thanks for catching that! I don't think this is the right xfail. I think it was failing on all Windows installs due to the path separator in the path. Just pushed a new commit to see if that does it.