[
https://issues.apache.org/jira/browse/SUREFIRE-2136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17649211#comment-17649211
]
Slawomir Jaranowski commented on SUREFIRE-2136:
-----------------------------------------------
It is a checker in upload GitHub Action:
{code}
Error: Artifact path is not valid: /this is: a test_surefire-1617/log.txt.
Contains the following character: Colon :
Invalid characters include: Double quote ", Colon :, Less than <, Greater than
>, Vertical bar |, Asterisk *, Question mark ?, Carriage return \r, Line feed \n
The following characters are not allowed in files that are uploaded due to
limitations with certain file systems such as NTFS. To maintain file system
agnostic behavior, these characters are intentionally not allowed to prevent
potential problems with downloads on different file systems.
{code}
> UmlautDirIT: Revert special paths with colon in it to regular ones after test
> -----------------------------------------------------------------------------
>
> Key: SUREFIRE-2136
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2136
> Project: Maven Surefire
> Issue Type: Improvement
> Reporter: Andreas Pabst
> Priority: Major
>
> On Linux the UmlautDirIT creates two directories with colons in them in the
> surefire-its/target directory:
> - 'this is: a test_surefire-1617'
> - 'local repo for: SUREFIRE-1617'
> These directories cause issues when Github actions try to upload artifacts in
> case of a build failure.
> As [~sjaranowski] suggested in the mailing list, these directories should be
> renamed to regular directory names after the test.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
