[
https://issues.apache.org/jira/browse/YETUS-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16584913#comment-16584913
]
Yetus QA commented on YETUS-657:
--------------------------------
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
21s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
|| || || || {color:brown} master Compile Tests {color} ||
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} shellcheck {color} | {color:green} 0m
6s{color} | {color:green} The patch generated 0 new + 45 unchanged - 4 fixed =
45 total (was 49) {color} |
| {color:green}+1{color} | {color:green} shelldocs {color} | {color:green} 0m
2s{color} | {color:green} There were no new shelldocs issues. {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
0s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 0m 36s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/yetus:6c9c3d9 |
| JIRA Issue | YETUS-657 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12936168/YETUS-657.03.patch |
| Optional Tests | shellcheck shelldocs |
| uname | Linux 104f25794c2c 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14
08:53:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | nobuild |
| git revision | master / a32a651 |
| shellcheck | v0.4.6 |
| Max. process+thread count | 12 (vs. ulimit of 1000) |
| modules | C: . U: . |
| Console output |
https://builds.apache.org/job/PreCommit-YETUS-Build/772/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT http://yetus.apache.org |
This message was automatically generated.
> volumes on non-existent files creates a directory
> -------------------------------------------------
>
> Key: YETUS-657
> URL: https://issues.apache.org/jira/browse/YETUS-657
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
> Affects Versions: 0.8.0
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Blocker
> Fix For: 0.8.0
>
> Attachments: YETUS-657.00.patch, YETUS-657.01.patch,
> YETUS-657.02.patch, YETUS-657.03.patch
>
>
> It would appear that at some point docker's behavior has changed with regards
> to volumes and non-existent files.
> When running docker -v file:file:
> In 17.05 (ASF Jenkins), this creates a file and good to go.
> In 17.12 and 18.05, this creates a directory.
> In order to make this safe, there are multiple routes that could be
> approached:
> a) only mount directories
> b) make sure the file exists before the volume mount
> In all instances, the -v params for docker need to get audited to make sure
> things are working as expected. In particular, some of the reporting is
> known to be broken, thus making this a blocking bug.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
