Source: r-cran-dplyr Version: 0.7.7-1 User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:r-cran-rlang
[X-Debbugs-CC: debian...@lists.debian.org, r-cran-rl...@packages.debian.org]
Dear maintainers,
With a recent upload of r-cran-rlang the autopkgtest of r-cran-dplyr
fails in testing when that autopkgtest is run with the binary packages
of r-cran-rlang from unstable. It passes when run with only packages
from testing. In tabular form:
pass fail
r-cran-rlang from testing 0.3.0.1-1
r-cran-dplyr from testing 0.7.7-1
all others from testing from testing
I copied some of the output at the bottom of this report. It seems the
autopkgtest check for exact strings in error messages and those messages
have changed.
Currently this regression is contributing to the delay of the migration
of r-cran-rlang to testing [1]. Of course, r-cran-rlang shouldn't just
break your autopkgtest (or even worse, your package), but it seems to me
that the change in r-cran-rlang was intended and your package needs to
update to the new situation. If needed, please change the bug's severity.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from r-cran-rlang should
really add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=r-cran-rlang
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-dplyr/1211130/log.gz
── 1. Failure: funs() gives a clear error message (#3368)
(@test-funs.R#28) ───
`funs(...)` threw an error with unexpected message.
Expected match: "`function(si) {\n mp[si]\n}` must be a function name
(quoted or unquoted) or an unquoted call, not `function`"
Actual message: "`function(si) {\n mp[si]\n}` must be a function name
(quoted or unquoted) or an unquoted call, not ``function``"
── 2. Failure: funs() gives a clear error message (#3368)
(@test-funs.R#36) ───
`funs(~mp[.])` threw an error with unexpected message.
Expected match: "`~mp[.]` must be a function name (quoted or unquoted)
or an unquoted call, not `~`"
Actual message: "`~mp[.]` must be a function name (quoted or unquoted)
or an unquoted call, not ``~``"
══ testthat results
═══════════════════════════════════════════════════════════
OK: 2724 SKIPPED: 11 FAILED: 2
1. Failure: funs() gives a clear error message (#3368) (@test-funs.R#28)
2. Failure: funs() gives a clear error message (#3368) (@test-funs.R#36)
Error: testthat unit tests failed
Execution halted
signature.asc
Description: OpenPGP digital signature
