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

Beam JIRA Bot commented on BEAM-7789:
-------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it 
has been labeled "stale-P2". If this issue is still affecting you, we care! 
Please comment and remove the label. Otherwise, in 14 days the issue will be 
moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed 
explanation of what these priorities mean.


> :beam-test-tools project fails to build locally
> -----------------------------------------------
>
>                 Key: BEAM-7789
>                 URL: https://issues.apache.org/jira/browse/BEAM-7789
>             Project: Beam
>          Issue Type: Bug
>          Components: testing
>            Reporter: Anton Kedin
>            Priority: P2
>              Labels: stale-P2
>
> Running the release-verification build (global build of everything) in turn 
> triggers the build of the `beam-test-tools` project, which has some test 
> infrastructure scripts that we run on Jenkins. It seems to work fine on 
> jenkins. However running the build of the project locally fails: 
> https://scans.gradle.com/s/kqhkzyozbpiua/console-log#L6
> What seems to happen is the gradle vendoring plugin caches the dependencies 
> locally, but fails to cache simplelru.
> One workaround (based on ./gradlew :beam-test-tools:showGopathGoroot)
> {code}
> export GOPATH=$PWD/.test-infra/tools/.gogradle/project_gopath
> go get github.com/hashicorp/golang-lru/simplelru
> ./gradlew :beam-test-tools:build
> {code}
> It is able to find the `lrumap` and `simplelru` during the dependency 
> resolution step, and I can see it mentioned in couple of artifacts produced 
> by the `gogradle` plugin. But when it does `:installDepedencies` to actually 
> copy them to `vendor` directory, this specific package is missing. This 
> reproduces for me on a couple of different machines I tried, both on release 
> and master branches



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to