Scanner IOException: Could not delete file '/tmp/ort-DefaultWorkingTreeCache16779531845304394453/test/fixtures/testdir5' #8987
Assignees
Labels
bug
Issues that are considered to be bugs
downloader
About the downloader tool
scanner
About the scanner tool
Comments
schvvarzekatze
added
bug
|
Some questions:
|
sschuberth
added
downloader
|
I have added parts of the necessary information. Unfortunately the tmp directory is cleared as soon as the job ist processed. So we will retry the run with a sleep. |
sschuberth
added a commit
that referenced
this issue
Aug 14, 2024
This is supposed to help debugging issues like [1]. [1]: #8987 Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.org>
|
I've created #8989 to help with debugging this issue. Can you run again with that PR merged? |
|
Thank you then I will rebuild a docker image as soon as that PR is merged and rerun the ort scan. |
sschuberth
added a commit
that referenced
this issue
Aug 14, 2024
This is supposed to help debugging issues like [1]. [1]: #8987 Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.org>
|
Hello @sschuberth: |
|
@schvvarzekatze I don't see any of the new debug logging in there. Note that you explicitly have to run ORT with |
|
Thank you. I tried it another time with --debug but the logs still look the same. I do not find
|
|
The |
|
I just tried it but with a local run (as all logging results could not be collected on gitlab). The error is the same anyway. |
|
Note to myself: The new debug logs now indicate that the problem probably is the non-UTF8 filename in https://github.com/fshost/node-dir/tree/master/test/fixtures/testdir5. |
sschuberth
added a commit
that referenced
this issue
Sep 3, 2024
Leverage Kotlin's `Path.deleteRecursively()` extension function which on the JVM uses the `Path` API to delete files and directories. That function also does not follow symbolic links on deletion. Fixes #8987. Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.org>
sschuberth
added a commit
that referenced
this issue
Sep 3, 2024
Leverage Kotlin's `Path.deleteRecursively()` extension function which on the JVM uses the `Path` API to delete files and directories. That function also does not follow symbolic links on deletion. Fixes #8987. Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.org>
sschuberth
added a commit
that referenced
this issue
Sep 4, 2024
Leverage Kotlin's `Path.deleteRecursively()` extension function which on the JVM uses the `Path` API to delete files and directories. That function also does not follow symbolic links on deletion. Fixes #8987. Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.org>
sschuberth
added a commit
that referenced
this issue
Sep 4, 2024
Leverage Kotlin's `Path.deleteRecursively()` extension function which on the JVM uses the `Path` API to delete files and directories. That function also does not follow symbolic links on deletion. Fixes #8987. Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.org>
sschuberth
added a commit
that referenced
this issue
Sep 4, 2024
Leverage Kotlin's `Path.deleteRecursively()` extension function which on the JVM uses the `Path` API to delete files and directories. That function also does not follow symbolic links on deletion. Fixes #8987. Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.org>
sschuberth
added a commit
that referenced
this issue
Sep 5, 2024
Leverage Kotlin's `Path.deleteRecursively()` extension function which on the JVM uses the `Path` API to delete files and directories. That function also does not follow symbolic links on deletion. Fixes #8987. Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.org>
sschuberth
added a commit
that referenced
this issue
Sep 5, 2024
Leverage Kotlin's `Path.deleteRecursively()` extension function which on the JVM uses the `Path` API to delete files and directories. That function also does not follow symbolic links on deletion. Fixes #8987. Signed-off-by: Sebastian Schuberth <sebastian@doubleopen.org>
|
Thank you, with the fix the scan runs sucessfully again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The scan step exits with error after file archives for all packages are created.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
All steps are processed sucessfully and reports generated.
Console / log output
Add console and / or log output that shows the error and additional context.
No screenshots of plain text please, to keep text searchable.
Environment
Output of the
ort requirementscommand:Or manually specify:
And specify (relevant parts of) your ORT configuration (
config.yml):Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: