Skip to content

UTF-16 scan test leaves its fixture open on Windows #8795

Description

@carloea2

What happened?

The encoding regression calls exhausted next() without observing hasNext == false, which closes the lazy reader. Windows then rejects deleting the still-open temporary file. Correct decoding should not fail during cleanup.

How to reproduce?

On Windows with JDK 17, run:

sbt "WorkflowOperator/testOnly org.apache.texera.amber.operator.source.scan.file.FileScanSourceOpDescSpec"

The unchanged suite records 13 passes and one cleanup failure. Related to the encoding test introduced in #8605.

Version/Branch

1.4.0-incubating-SNAPSHOT (main)

Commit Hash (Optional)

acc6dd1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions