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

Zach Badgett commented on BEAM-7788:
------------------------------------

Issue is caused by the Jenkins workspace being reused, the (attempted) update 
to Go modules exposed it by showing what happens when read-only files are being 
created. There are two ways fix this: by cleaning up the workspace entirely, or 
ensuring all read-only files are writable (which I did in 
[https://github.com/apache/beam/pull/9096]). I personally believe cleaning up 
the workspace is the proper way to handle it, but I know the only reason it 
would be reused is to speed up run times by not needing to clone the repository 
again. If we clear the workspace we can still optimize the git clone by doing a 
shallow clone (maybe a depth of ~5 incase any process uses previous commits or 
1 if no one sees an issue with not having history).

> Go modules breaking precommits?
> -------------------------------
>
>                 Key: BEAM-7788
>                 URL: https://issues.apache.org/jira/browse/BEAM-7788
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-go, testing
>            Reporter: Udi Meiri
>            Priority: Major
>
> Lots of errors like:
> {code}
> 01:32:36  > git clean -fdx # timeout=10
> 01:32:38 FATAL: Command "git clean -fdx" returned status code 1:
> 01:32:38 stdout: 
> 01:32:38 stderr: warning: failed to remove 
> sdks/go/.gogradle/project_gopath/pkg/mod/[email protected]/zpages/example_test.go
> ... [lots of files listed]
> {code}
> Examples:
> https://builds.apache.org/job/beam_PreCommit_Python_PVR_Flink_Commit/3886/consoleFull
> https://builds.apache.org/job/beam_PreCommit_Python_PVR_Flink_Commit/3884/consoleFull
> https://builds.apache.org/job/beam_PreCommit_JavaPortabilityApi_Commit/3790/consoleFull
> https://builds.apache.org/job/beam_PreCommit_JavaPortabilityApi_Commit/3788/consoleFull
> cc: [~lostluck]



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to