Skip to content
Snippets Groups Projects
Verified Commit 8c7b8d60 authored by Robin Candau's avatar Robin Candau
Browse files

Document tests failing if an instance of protonmail-bridge is running in the test env

parent 47a7bb59
No related branches found
No related tags found
No related merge requests found
......@@ -8,6 +8,11 @@ See, for instance: <https://github.com/ProtonMail/proton-bridge/releases/tag/v3.
Make sure to verify that new upstream releases are not tagged as "Pre-release" before packaging them.
Note that such "pre-releases" are filtered out in the nvchecker integration (as it specifically looks for releases tagged as "latest").
## Tests failing if a protonmail-bridge instance is already running in the check() environment
`protonmail-bridge` tests are expecting ports 1143 & 1144 (default and fallback ports for IMAP) and ports 1025 & 1026 (default and fallback ports for SMTP) to be free for some specific tests scenarios.
If those ports are already in use by any other service(s) (e.g. there's already a running protonmail-bridge instance on those default ports in your build / test env), tests will fail.
## Rebuild on Qt6 minor / major releases
`protonmail-bridge` has to be rebuilt against `Qt6` minor and major releases (patch releases are fine), otherwise it won't start. See [this](https://gitlab.archlinux.org/archlinux/packaging/packages/protonmail-bridge/-/issues/2) bug report.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment