-
Notifications
You must be signed in to change notification settings - Fork 209
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
Unit tests are failing #210
Comments
Why are the unit tests not running as part of the pull requests? Eg - #216 |
I think we broke several tests in #202 . We need to fix this. That PR was very necessary to fix concurrency issues, but it looks like we busted base/relative URL handling. |
@cristoper I don't know if you'd have a hot minute to check out the broken tests + relative URL handling? Did we just miss updating some places where we parse URLs to call your new function? |
Huh. I'll try to look into this soon -- feel free to ping me a reminder if you haven't heard from me next week. |
Thank you! Appreciate you @cristoper |
Thanks for noticing these failing tests, @JLugagne. The good news is they have revealed two bugs introduced with #202 and mmcdole/goxpp#9 that we can fix: The main problem is that goxpp's This also uncovered a bug in the way goxpp's The bad news is that, except for URL attributes in the root element, gofeed has not been correctly resolving URLs according to With the changes in both of the PRs above in place, |
Scratch that, I was not on the latest HEAD. There is still one RSS test that is failing since #220 (not related to the xml:base issues):
|
PR mmcdole#220 introduced a failing test for detecting images in the "content" element. It should instead be testing the "content:encoded" element. But that uncovered an issue with how extensions were being detected (the "content" namespace was being detected as an extension namespace). As a more robust way of checking for the "content" namespace, this PR exposes `shared.PrefixForNamspace()` as a public function so it can be used in the rss parser. This provides a solution to PR mmcdole#211 (and includes @JLugagne's test case from that PR). Once the fixes to xml:base handling in mmcdole#222 are merged, this should fix the remaining failing test reported in mmcdole#210.
PR mmcdole#220 introduced a failing test for detecting images in the "content" element. It should instead be testing the "content:encoded" element. But that uncovered an issue with how extensions were being detected (the "content" namespace was being detected as an extension namespace). As a more robust way of checking for the "content" namespace, this PR exposes `shared.PrefixForNamspace()` as a public function so it can be used in the rss parser. This provides a solution to PR mmcdole#211 (and includes a test based on @JLugagne's test case from that PR). Once the fixes to xml:base handling in mmcdole#222 are merged, this should fix the remaining failing test reported in mmcdole#210.
PR mmcdole#220 introduced a failing test for detecting images in the "content" element. It should instead be testing the "content:encoded" element. But that uncovered an issue with how extensions were being detected (the "content" namespace was being detected as an extension namespace). As a more robust way of checking for the "content" namespace, this PR exposes `shared.PrefixForNamspace()` as a public function so it can be used in the rss parser. This should also fix PR mmcdole#211 (and includes @JLugagne's test case from that PR). Once the fixes to xml:base handling in mmcdole#222 are merged, this should fix the remaining failing test reported in mmcdole#210.
PR #220 introduced a failing test for detecting images in the "content" element. It should instead be testing the "content:encoded" element. But that uncovered an issue with how extensions were being detected (the "content" namespace was being detected as an extension namespace). As a more robust way of checking for the "content" namespace, this PR exposes `shared.PrefixForNamspace()` as a public function so it can be used in the rss parser. This should also fix PR #211 (and includes @JLugagne's test case from that PR). Once the fixes to xml:base handling in #222 are merged, this should fix the remaining failing test reported in #210.
I think we are back to green thanks to @cristoper ! |
Expected behavior
Since v1.2.1, unit tests are broken, it seems to be the management of the tag's attribute xml:base.
Actual behavior
It seems that since you changed links management the local base isn't use if any but is it doesn't have one none are used .
Here are a very few outputs of the go test execution:
Steps to reproduce the behavior
run go test ./... from the root of the project on master or from tag v1.2.1
The text was updated successfully, but these errors were encountered: