Skip to content

Test failure with duckdb 1.2.0 #64

@krlmlr

Description

@krlmlr

CRAN has reported, but I can't replicate, test failures with the upcoming duckdb 1.2.0.

https://win-builder.r-project.org/incoming_pretest/duckdb_1.2.0_20250214_192954/reverseDependencies/summary.txt

CRAN output:

    ══ Failed tests ════════════════════════════════════════════════════════════════
    ── Failure ('test-get-tools.R:36:3'): gb_sequence_get() works ──────────────────
    names(seq_dnabin_2) not equal to `id_2`.
    2/2 mismatches
    x[1]: "KF683087"
    y[1]: "AC092268"
    
    x[2]: "AC092268"
    y[2]: "KF683087"
    
    [ FAIL 1 | WARN 1 | SKIP 2 | PASS 138 ]
    Error: Test failures
    Execution halted

Test script (in a duckdb clone, with restez in a parallel directory):

#!/bin/sh

git clean -fdxq src
UserNM=true R CMD INSTALL . --no-byte-compile --quiet >/dev/null

R -q -e 'testthat::test_local("../restez", filter = "get-tools")'

The results seem the same, just in a different order. Do you now need an ORDER BY or an arrange()? Thanks!

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions