mirror of
https://github.com/docker-mailserver/docker-mailserver.git
synced 2024-01-19 02:48:50 +00:00
b58165762a
With `reload` a change detection event during local testing can be processed in less than a second according to logs. Previously this was 5+ seconds (_plus additional downtime for Postfix/Dovecot to become available again_).
In the past it was apparently an issue to use `<service> reload` due to a concern with the PID for wrapper scripts that `supervisorctl` managed, thus `supervisorctl <service> restart` had been used. Past discussions with maintainers suggest this is not likely an issue anymore, and `reload` should be fine to switch to now 👍
---
**NOTE:** It may not be an issue in the CI, but on _**local systems running tests may risk failure in `setup-cli.bats` from a false positive**_ due to 1 second polling window of the test helper method, and a change event being possible to occur entirely between the two checks undetected by the current approach.
If this is a problem, we may need to think of a better way to catch the change. The `letsencrypt` test counts how many change events are expected to have been processed, and this could technically be leveraged by the test helper too.
---
**NOTE:** These two lines (_with regex pattern for postfix_) are output in the terminal when using the services respective `reload` commands:
```
postfix/master.*: reload -- version .*, configuration /etc/postfix
dovecot: master: Warning: SIGHUP received - reloading configuration
```
I wasn't sure how to match them as they did not appear in the `changedetector` log (_**EDIT:** they appear in the main log output, eg `docker logs <container name>`_).
Instead I've just monitored the `changedetector` log messages, which should be ok for logic that previously needed to ensure Dovecot / Postfix was back up after the `restart` was issued.
---
Commit history:
* chore: Change events `reload` Dovecot and Postfix instead of `restart`
Reloading is faster than restarting the processes.
Restarting is a bit heavy handed here and may no longer be necessary for general usage?
* tests: Adapt tests to support service `reload` instead of `restart`
* chore: Additional logging for debugging change event logs
* fix: Wait on change detection, then verify directory created
Change detection is too fast now (0-1 seconds vs 5+).
Directory being waited on here was created near the end of a change event, reducing that time to detect a change by the utility method further.
We can instead check that the directory exists after the change detection event is completed.
* chore: Keep using the maildir polling check
We don't presently use remote storage in tests, but it might be relevant in future when testing NFS.
This at least avoids any confusing failure happening when that scenario is tested.
|
||
|---|---|---|
| .. | ||
| mail_changedetector.bats | ||
| mail_disabled_clamav_spamassassin.bats | ||
| mail_dnsbl.bats | ||
| mail_fail2ban.bats | ||
| mail_fetchmail.bats | ||
| mail_fetchmail_parallel.bats | ||
| mail_hostname.bats | ||
| mail_lmtp_ip.bats | ||
| mail_pop3.bats | ||
| mail_postfix_inet.bats | ||
| mail_postscreen.bats | ||
| mail_privacy.bats | ||
| mail_quotas_disabled.bats | ||
| mail_smtponly.bats | ||
| mail_spam_junk_folder.bats | ||
| mail_special_use_folders.bats | ||
| mail_ssl_letsencrypt.bats | ||
| mail_ssl_manual.bats | ||
| mail_time.bats | ||
| mail_tls_dhparams.bats | ||
| mail_undef_spam_subject.bats | ||
| mail_with_imap.bats | ||
| mail_with_ldap.bats | ||
| mail_with_mdbox.bats | ||
| mail_with_postgrey.bats | ||
| mail_with_postgrey_disabled_by_default.bats | ||
| mail_with_relays.bats | ||
| mail_with_sdbox.bats | ||
| no_container.bats | ||
| open_dkim.bats | ||
| permit_docker.bats | ||
| security_tls_cipherlists.bats | ||
| sedfile.bats | ||
| setup-cli.bats | ||
| test_helper.bats | ||
| tests.bats | ||