| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| disable-connect-timeout-test-on-s390x.patch | no | |||||
| disable-tests-that-require-internet.patch | no | |||||
| disable-vendored.patch | no | |||||
| disable-webpki-roots.patch | no | |||||
| remove-wasm.patch | no | |||||
| remove-windows.patch | no | |||||
| fix-test-file-not-found.patch | This tests changes the blocking_file_part test to use a different test file because Cargo.lock is not available in the autopkgtest environment. It also changes the asserts to make failures easier to debug and nails-down the content-type, so it can't cause supious failures. =================================================================== |
no | ||||
| remove-macos.patch | no | |||||
| fix-test-feature-requirements.patch | no | |||||
| disable-test-that-sometimes-fails-on-debci.patch | =================================================================== | no | ||||
| relax-dep.patch | diff --git a/Cargo.toml b/Cargo.toml index 0ce46d3..858aafd 100644 |
no | ||||
| update-brotli.patch | no | |||||
| tests-bypass-the-proxy-if-testing-DNS-override.patch | [PATCH] tests: bypass the proxy if testing DNS override If an explicit proxy is configured in the environment, then the request will go through it rather than actually resolving the domain. Either we're hitting the target domain on a weird port which will likely fail, or the proxy straight up denies that weird request. We're hitting this issue in the Ubuntu CI. Amazingly enough, the tests actually passed *once* there, although the exact circumstances that allowed this are still a bit of a mystery. |
Simon Chopin <simon.chopin@canonical.com> | yes | 2024-07-03 | ||
| tests-bypass-the-proxy-if-testing-timeouts.patch | [PATCH] tests: bypass the proxy if testing timeouts If an explicit proxy is configured in the environment, the timeout tests will actually go through it, and then the test results will depend on the proxy's performance, which can vary. Testing this is very simple: ``` export http_proxy="http://127.0.0.1:1234" cargo test timeout ``` We're hitting this issue in the Ubuntu CI. Further investigations after 892569e10b69d1a0e5db1f53202d1ebf09924fc1 seemed to point that **sometimes**, the proxy would be too slow (particularly on non amd64 architectures), leading to the tests to actually timeout and pass. |
Florent 'Skia' Jacquet <florent.jacquet@canonical.com> | yes | 2024-07-10 |