| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| fix-failing-test.patch | [PATCH] [spec] Mock MX resolution of example.org to nothing Mock MX DNS query to return nothing Now it returns ; <<>> DiG 9.10.6 <<>> mx example.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29253 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1220 ;; QUESTION SECTION: ;example.com. IN MX ;; ANSWER SECTION: example.com. 86085 IN MX 0 . ;; Query time: 359 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Mon Apr 13 16:11:11 EAT 2020 ;; MSG SIZE rcvd: 55 |
Hallelujah <hery@rails-royce.org> | no | 2020-04-13 | ||
| 0002-Skip-tests-relying-on-a-DNS-setup.patch | Skip tests relying on a DNS setup The tests skipped failed in Ubuntu infrastructure and it passed in Debian buildd and local chroots. Those tests rely on a DNS to perform some MX record lookups. As far as I can see in Debian and local chroots some DNS information is leaking and that is why the tests pass. I filed a bug upstream to see if they can try to mock the MX record lookup some way: https://github.com/hallelujah/valid_email/issues/107 |
Lucas Kanashiro <lucas.kanashiro@canonical.com> | not-needed | 2020-07-02 |