Bug#1028111: r-cran-clock: autopkgtest failure on 32bit
The 'bug fix' applied to the _previous_ version of CRAN package clock, namely
a somewhat 'wild' sed patching of a single ie
# Ignore single test for i386 architecture. This is a workaround for bug
#1024828 of r-cran-igraph
if [ "$hostarch" = "i386" -o "$hostarch" = "armel" -o "$hostarch" = "armhf" ] ;
then
sed -i -e '152d' -e '151d' testthat/test-posixt.R
fi
now creates a syntax error on these very architectures (as the upstream file
presumably changed). Here is the corresponding part of one of the logs
(armel at
https://ci.debian.net/data/autopkgtest/testing/armel/r/r-cran-clock/36601943/log.gz)
80s > library(testthat)
80s > library(clock)
80s >
80s > test_check("clock")
132s Error in parse(con, n = -1, srcfile = srcfile, encoding = "UTF-8") :
132s test-posixt.R:1372:0: unexpected end of input
132s 1370: })
132s 1371: })
132s ^
132s Calls: test_check ... doTryCatch -> lapply -> FUN -> source_file -> parse
132s Execution halted
133s autopkgtest [08:19:23]: test run-unit-test: ---]
133s autopkgtest [08:19:23]: test run-unit-test: - - - - - - - - - - results -
- - - - - - - - -
133s run-unit-testFAIL non-zero exit status 1
Obviously if we ambush upstream code and corrupt then tests we impose will
fail.
This has fairly large repurcussions across other packages include some of mine.
If nobody else steps up I plan to address this by no longer 'hot-fix
patching' (and thereby corrupting) test-posixt.R but (at least for now)
simply skipping tests of test-posixt.t. The regular maintainers may find
time to investigate what parts of the test file work for armel, armhf, i386.
Dirk
--
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
Bug#1028111: r-cran-clock: autopkgtest failure on 32bit
Control: severity -1 important The two failing tests were excluded for the three affected architectures. While the problem is not really fixed (and thus the bug remains open) the severity is lowered to "important" to enable testing migration. Kind regards Andreas. -- http://fam-tille.de
Processed: Re: Bug#1028111: r-cran-clock: autopkgtest failure on 32bit
Processing control commands: > tags -1 upstream Bug #1028111 [src:r-cran-clock] r-cran-clock: autopkgtest failure on 32bit Added tag(s) upstream. > forwarded -1 https://github.com/r-lib/clock/issues/312 Bug #1028111 [src:r-cran-clock] r-cran-clock: autopkgtest failure on 32bit Set Bug forwarded-to-address to 'https://github.com/r-lib/clock/issues/312'. -- 1028111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028111: r-cran-clock: autopkgtest failure on 32bit
Control: tags -1 upstream
Control: forwarded -1 https://github.com/r-lib/clock/issues/312
I've forwarded the issue to the upstream issue tracker.
Kind regards
Andreas.
Am Sat, Jan 07, 2023 at 03:02:04AM +0200 schrieb Adrian Bunk:
> Source: r-cran-clock
> Version: 0.6.1-1
> Severity: serious
>
> https://tracker.debian.org/pkg/r-cran-clock
>
> Issues preventing migration:
> ∙ ∙ autopkgtest for r-cran-clock/0.6.1-1: amd64: Pass, arm64: Pass, armel:
> Regression ♻ , armhf: Regression ♻ , i386: Regression ♻
>
>
> ...
> > test_check("clock")
> [ FAIL 2 | WARN 29 | SKIP 252 | PASS 1146 ]
>
> ══ Skipped tests
> ═══
> • On CRAN (252)
>
> ══ Failed tests
>
> ── Failure ('test-posixt.R:151'): can group by
> year/month/day/hour/minute/second ──
> date_group(z, "year") (`actual`) not identical to `expect` (`expected`).
>
> actual | expected
> [1] "-1-12-31 23:56:02" - "0-01-01" [1]
> [2] "0-12-31 23:56:02" - "1-01-01" [2]
> [3] "1-12-31 23:56:02" - "2-01-01" [3]
> [4] "2-12-31 23:56:02" - "3-01-01" [4]
> [5] "3-12-31 23:56:02" - "4-01-01" [5]
> ── Failure ('test-posixt.R:152'): can group by
> year/month/day/hour/minute/second ──
> date_group(z, "year", n = 3) (`actual`) not identical to expect[c(1, 1, 1, 4,
> 4)] (`expected`).
>
> actual | expected
> [1] "-1-12-31 23:56:02" - "0-01-01" [1]
> [2] "-1-12-31 23:56:02" - "0-01-01" [2]
> [3] "-1-12-31 23:56:02" - "0-01-01" [3]
> [4] "2-12-31 23:56:02" - "3-01-01" [4]
> [5] "2-12-31 23:56:02" - "3-01-01" [5]
>
> [ FAIL 2 | WARN 29 | SKIP 252 | PASS 1146 ]
> Error: Test failures
> Execution halted
> autopkgtest [16:10:54]: test run-unit-test: ---]
> autopkgtest [16:10:55]: test run-unit-test: - - - - - - - - - - results - -
> - - - - - - - -
> run-unit-testFAIL non-zero exit status 1
> ...
> ___
> R-pkg-team mailing list
> r-pkg-t...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team
--
http://fam-tille.de
Bug#1028111: r-cran-clock: autopkgtest failure on 32bit
Source: r-cran-clock
Version: 0.6.1-1
Severity: serious
https://tracker.debian.org/pkg/r-cran-clock
Issues preventing migration:
∙ ∙ autopkgtest for r-cran-clock/0.6.1-1: amd64: Pass, arm64: Pass, armel:
Regression ♻ , armhf: Regression ♻ , i386: Regression ♻
...
> test_check("clock")
[ FAIL 2 | WARN 29 | SKIP 252 | PASS 1146 ]
══ Skipped tests ═══
• On CRAN (252)
══ Failed tests
── Failure ('test-posixt.R:151'): can group by
year/month/day/hour/minute/second ──
date_group(z, "year") (`actual`) not identical to `expect` (`expected`).
actual | expected
[1] "-1-12-31 23:56:02" - "0-01-01" [1]
[2] "0-12-31 23:56:02" - "1-01-01" [2]
[3] "1-12-31 23:56:02" - "2-01-01" [3]
[4] "2-12-31 23:56:02" - "3-01-01" [4]
[5] "3-12-31 23:56:02" - "4-01-01" [5]
── Failure ('test-posixt.R:152'): can group by
year/month/day/hour/minute/second ──
date_group(z, "year", n = 3) (`actual`) not identical to expect[c(1, 1, 1, 4,
4)] (`expected`).
actual | expected
[1] "-1-12-31 23:56:02" - "0-01-01" [1]
[2] "-1-12-31 23:56:02" - "0-01-01" [2]
[3] "-1-12-31 23:56:02" - "0-01-01" [3]
[4] "2-12-31 23:56:02" - "3-01-01" [4]
[5] "2-12-31 23:56:02" - "3-01-01" [5]
[ FAIL 2 | WARN 29 | SKIP 252 | PASS 1146 ]
Error: Test failures
Execution halted
autopkgtest [16:10:54]: test run-unit-test: ---]
autopkgtest [16:10:55]: test run-unit-test: - - - - - - - - - - results - - -
- - - - - - -
run-unit-testFAIL non-zero exit status 1
...
