Skip to content
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

Test data updates to fix test failures #192

Merged
merged 2 commits into from
Jan 2, 2024
Merged

Test data updates to fix test failures #192

merged 2 commits into from
Jan 2, 2024

Conversation

kitterma
Copy link
Contributor

@kitterma kitterma commented Jan 2, 2024

Currently we have multiple test failures with pycares 4.4.0 with c-ares 1.24. Two of the three are unrelated to the new c-ares version:

For test_query_txt_chunked, the jobscoutdaily.com SPF record changed, so the expected result is wrong. I think it still has the relevant attributes for the test case.

For test_query_ptr, there's no longer a PTR record at 8.8.8.8, so the test failed with pycares (correctly) reported an error. It looks like any address with a PTR record will meet the requirements for the test, so I replaced it with the address of one of Google's mail servers.

I'll submit a separate PR for the change related to the newer c-ares.

Scott K

@saghul saghul merged commit 54310ff into saghul:master Jan 2, 2024
20 checks passed
@saghul
Copy link
Owner

saghul commented Jan 2, 2024

Thank you!

@kitterma
Copy link
Contributor Author

kitterma commented Apr 3, 2024

The jobscoutdaily.com SPF record changed again, so this now fails again:

jobscoutdaily.com. 21600 IN TXT "v=spf1 A MX " "include:emailcampaigns.net include:spf.dynect.net include:ccsend.com include:_spf.elasticemail.com ip4:67.200.116.0/24 ip4:74.199.198.0/24 " " ~all"

When I have time, I'll try to submit an updated PR, but it may be awhile.

@kitterma
Copy link
Contributor Author

kitterma commented Apr 3, 2024

Or not. Now I'm not sure what's going on.

@kitterma
Copy link
Contributor Author

kitterma commented Apr 3, 2024

So, it looks like they changed it a few months ago and then recently changed it back, so I think we're fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants