jcoffey-dev is traveling from Thursday 1 October through Sunday 4 October. Issues and pull requests are welcome, and will get an answer after that. Thanks for your patience.
automation::automation_tests failed at tests/src/automation/dns.rs:200 on main. It failed identically on main from before today's merges, with the same digest.
Cause. The expected zone was copied from upstream v0.16.22 (7dae9b2).
Its _ua-auto-config TXT record carries d= = SHA-256 of the account-configuration (PACC) document.
That document's provider name is types::brand!(), which the rebrand (89665de) changed.
So the server's digest (ZZ35…) is right; the test still expected upstream's (9X2m…).
Fix. Update the expected digest; notice header added to the file. Nothing else in the zone differed.
Checked on the laptop: with the ufw rule that lets the stalwart-test-acme network reach the host, the whole automation suite passes:
ACME, including #93's reschedule check (the first time it has run);
DKIM;
DNS;
RFC 2136.
notice-check passes.
`automation::automation_tests` failed at `tests/src/automation/dns.rs:200` on main. It failed identically on main from before today's merges, with the same digest.
**Cause.** The expected zone was copied from upstream v0.16.22 (`7dae9b2`).
- Its `_ua-auto-config` TXT record carries `d=` = SHA-256 of the account-configuration (PACC) document.
- That document's provider name is `types::brand!()`, which the rebrand (`89665de`) changed.
- So the server's digest (`ZZ35…`) is right; the test still expected upstream's (`9X2m…`).
**Fix.** Update the expected digest; notice header added to the file. Nothing else in the zone differed.
**Checked on the laptop:** with the ufw rule that lets the `stalwart-test-acme` network reach the host, the whole automation suite passes:
- ACME, including #93's reschedule check (the first time it has run);
- DKIM;
- DNS;
- RFC 2136.
`notice-check` passes.
The automation suite's DNS test compared the published zone with one
copied from upstream v0.16.22. Its _ua-auto-config record carries a
SHA-256 of the account-configuration (PACC) document, and that document
names the provider as the brand, which the rebrand changed. The digest
the server publishes is right; the expected zone still held upstream's.
With the new digest the whole automation suite passes: ACME (including
the not-due reschedule check), DKIM, DNS and RFC 2136. It had been
failing at this point on main since the rebrand.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
automation::automation_testsfailed attests/src/automation/dns.rs:200on main. It failed identically on main from before today's merges, with the same digest.Cause. The expected zone was copied from upstream v0.16.22 (
7dae9b2)._ua-auto-configTXT record carriesd== SHA-256 of the account-configuration (PACC) document.types::brand!(), which the rebrand (89665de) changed.ZZ35…) is right; the test still expected upstream's (9X2m…).Fix. Update the expected digest; notice header added to the file. Nothing else in the zone differed.
Checked on the laptop: with the ufw rule that lets the
stalwart-test-acmenetwork reach the host, the whole automation suite passes:notice-checkpasses.