[jira] [Comment Edited] (BIGTOP-3174) ./gradlew repo-ind failed on Bigtop build slaves

["Evans Ye (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BIGTOP-3174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773204#comment-16773204 ] 

Evans Ye edited comment on BIGTOP-3174 at 2/20/19 5:12 PM:
-----------------------------------------------------------

https://github.com/apache/bigtop/pull/481
The idea is to switch to bigtop-ci/build.sh, which creates a docker container and copy bigtop dir inside for runtime execution.


was (Author: evans_ye):
https://github.com/apache/bigtop/pull/481
The idea is ti switch to bigtop-ci/build.sh, which creates a docker container and copy bigtop dir inside for runtime execution.

> ./gradlew repo-ind failed on Bigtop build slaves
> ------------------------------------------------
>
>                 Key: BIGTOP-3174
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-3174
>             Project: Bigtop
>          Issue Type: Sub-task
>          Components: build
>    Affects Versions: 1.3.0
>            Reporter: Evans Ye
>            Assignee: Evans Ye
>            Priority: Major
>             Fix For: 1.3.1
>
>
> While it was good running on Mac OS when developing BIGTOP-3009. This feature failed to run on Bigtop build slaves(Amazon Linux). The error log:
> {code}
> 16:56:51.685 [INFO] [org.gradle.cache.internal.DefaultCacheAccess] Creating new cache for fileHashes, path /bigtop-home/.gradle/4.3/fileHashes/fileHashes.bin, access org.gradle.cache.internae
> 16:56:51.686 [DEBUG] [org.gradle.api.internal.changedetection.state.InMemoryCacheDecoratorFactory] Creating in-memory store for cache /bigtop-home/.gradle/4.3/fileHashes/fileHashes.bin (max )
> 16:56:51.686 [DEBUG] [org.gradle.cache.internal.LockOnDemandCrossProcessCacheAccess] Acquiring file lock for file hash cache (/bigtop-home/.gradle/4.3/fileHashes)
> 16:56:51.687 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire exclusive lock on file hash cache (/bigtop-home/.gradle/4.3/fileHashes).
> 16:56:51.688 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] The file lock is held by a different Gradle process (pid: 8237, lockId: 5389536953551787496). Pinged owner at port 4175
> 16:56:52.770 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] The file lock is held by a different Gradle process (pid: 8237, lockId: 5389536953551787496). Pinged owner at port 417
> 16:56:53.822 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] The file lock is held by a different Gradle process (pid: 8237, lockId: 5389536953551787496). Pinged owner at port 417
> {code}
> I guess it is because Docker on Mac OS is running inside a hidden VM, which isolates the lock on file.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)