Skip to content

Some burn-dataset tests fail on Windows #946

Closed
@Luni-4

Description

Describe the bug

Running all burn-dataset tests through the Windows CI, we get two errors for some of them:

failures:

---- dataset::sqlite::tests::sqlite_writer_write stdout ----
thread 'dataset::sqlite::tests::sqlite_writer_write' panicked at 'Failed to set completed: PersistDbFile(Error { error: Os { code: 32, kind: Uncategorized, message: "The process cannot access the file because it is being used by another process." }, handle: Handle { id: 3, _marker: PhantomData<gix_tempfile::handle::Writable> } })', burn-dataset\src\dataset\sqlite.rs:791:32
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

---- dataset::sqlite::tests::sqlite_writer_write_multi_thread stdout ----
thread 'dataset::sqlite::tests::sqlite_writer_write_multi_thread' panicked at 'Should set completed successfully: PersistDbFile(Error { error: Os { code: 32, kind: Uncategorized, message: "The process cannot access the file because it is being used by another process." }, handle: Handle { id: 2, _marker: PhantomData<gix_tempfile::handle::Writable> } })', burn-dataset\src\dataset\sqlite.rs:839:14


failures:
    dataset::sqlite::tests::sqlite_writer_write
    dataset::sqlite::tests::sqlite_writer_write_multi_thread

test result: FAILED. 16 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.14s

error: test failed, to rerun pass `-p burn-dataset --lib`
error: process didn't exit successfully: `target\debug\xtask.exe run-checks std` (exit code: 101)
Error: Process completed with exit code 1.

For now, tests have been ignored on Windows in search of a possibile solution

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions