Dear maintainer(s),

Your package has an autopkgtest, great. However, because of the failure
"caused" by golang-testify, I looked into the history of your
autopkgtest [1] and I noticed it fails regularly. In all the logs I
looked at the error is the same, it happens on multiple architectures,
but I haven't seen it on amd64.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Paul

[1] https://ci.debian.net/packages/g/golang-go.opencensus/testing/arm64/

https://ci.debian.net/data/autopkgtest/testing/arm64/g/golang-go.opencensus/11227933/log.gz


=== RUN   Test_Worker_MultiExport
    worker_test.go:216: Mismatched value (want &{2}, got 1) for &{[{a
true}] [{2021-03-23 03:41:31.469410257 +0000 UTC m=+1.006722755 1}]
2021-03-23 03:41:31.469373227 +0000 UTC m=+1.006685725} in "/VF1"
    worker_test.go:221: Mismatched value (want &{7.500000}, got
2.000000) for &{[] [{2021-03-23 03:41:31.469410257 +0000 UTC
m=+1.006722755 2}] 2021-03-23 03:41:31.469374877 +0000 UTC
m=+1.006687375} in "/VF2"
--- FAIL: Test_Worker_MultiExport (0.00s)

Prevented from emailing control@bugs.debian.org directly because of
https://github.com/roundcube/roundcubemail/issues/6438#issuecomment-835782075

debian patch skip_flaky_test.patch skips the flaky test in 0.22.4-2

Hence downgrading severity to normal.

Ignores the problem, doesn't actually fix it, so not closing the bug.