Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. Can you
please investigate the situation and fix it? I copied some of the output
at the bottom of this report.

The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing.

More information about this bug and the reason for filing it can be
found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-oxhttp/62571088/log.gz

  69s failures:
  69s
  69s ---- client::tests::test_https_get_ok stdout ----
  69s
  69s thread 'client::tests::test_https_get_ok' panicked at
src/client.rs:423:9:
  69s assertion `left == right` failed
  69s   left: [116, 101, 120, 116, 47, 104, 116, 109, 108]
  69s  right: [116, 101, 120, 116, 47, 104, 116, 109, 108, 59, 32, 99,
104, 97, 114, 115, 101, 116, 61, 85, 84, 70, 45, 56]
  69s stack backtrace:
  69s    0: rust_begin_unwind
  69s    1: core::panicking::panic_fmt
  69s    2: core::panicking::assert_failed_inner
  69s    3: core::panicking::assert_failed
  69s    4: oxhttp::client::tests::test_https_get_ok
  69s    5: core::ops::function::FnOnce::call_once
  69s note: Some details are omitted, run with `RUST_BACKTRACE=full` for
a verbose backtrace.
  69s
  69s
  69s failures:
  69s     client::tests::test_https_get_ok
  69s
  69s test result: FAILED. 49 passed; 1 failed; 0 ignored; 0 measured; 8
filtered out; finished in 0.26s
  69s
  69s error: test failed, to rerun pass `--lib`
  69s error: 1 target failed:
  69s     `--lib`
  69s autopkgtest [22:27:42]: test rust-oxhttp:@: -----------------------]

The formatting of the assertion failure message is less than ideal
[116, 101, 120, 116, 47, 104, 116, 109, 108] is 'text/html'
and [116, 101, 120, 116, 47, 104, 116, 109, 108, 59, 32, 99,
104, 97, 114, 115, 101, 116, 61, 85, 84, 70, 45, 56] is
'text/html; charset=UTF-8'

It looks like the immediate cause of this failure is that the
behaviour of the web server at example.com changed.

but build-time tests should not be trying to access stuff
on the internet in the first place.