Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot build ruby runtime #31

Closed
rabbah opened this issue Aug 17, 2019 · 7 comments
Closed

cannot build ruby runtime #31

rabbah opened this issue Aug 17, 2019 · 7 comments

Comments

@rabbah
Copy link
Member

rabbah commented Aug 17, 2019

Travis is failing with:

mv: cannot stat 'incubator-openwhisk-runtime-go-golang1.11-1.13.0-incubating': No such file or directory

The command '/bin/sh -c curl -L "$PROXY_SOURCE" | tar xzf -   && mkdir -p src/github.com/apache   && mv incubator-openwhisk-runtime-go-golang1.11-1.13.0-incubating      src/github.com/apache/incubator-openwhisk-runtime-go   && cd src/github.com/apache/incubator-openwhisk-runtime-go/main   && CGO_ENABLED=0 go build -o /bin/proxy' returned a non-zero code: 1

Sat Aug 17 04:40:44 UTC 2019: Command 'docker build -t actionloop-ruby-v2.6 /home/travis/build/apache/openwhisk-runtime-ruby/core/ruby2.6ActionLoop' failed with exitCode 1, no more retries left, aborting...

:core:ruby2.6ActionLoop:distDocker FAILED

:core:ruby2.6ActionLoop:tagImage

Sat Aug 17 04:40:44 UTC 2019: Executing 'docker tag actionloop-ruby-v2.6 whisk/actionloop-ruby-v2.6:latest'

Error response from daemon: No such image: actionloop-ruby-v2.6:latest

Sat Aug 17 04:40:44 UTC 2019: Command 'docker tag actionloop-ruby-v2.6 whisk/actionloop-ruby-v2.6:latest' failed with exitCode 1, 2 retries left, retrying...

Sat Aug 17 04:40:44 UTC 2019: Executing 'docker tag actionloop-ruby-v2.6 whisk/actionloop-ruby-v2.6:latest'

Error response from daemon: No such image: actionloop-ruby-v2.6:latest

Sat Aug 17 04:40:44 UTC 2019: Command 'docker tag actionloop-ruby-v2.6 whisk/actionloop-ruby-v2.6:latest' failed with exitCode 1, 1 retries left, retrying...

Sat Aug 17 04:40:44 UTC 2019: Executing 'docker tag actionloop-ruby-v2.6 whisk/actionloop-ruby-v2.6:latest'

Error response from daemon: No such image: actionloop-ruby-v2.6:latest

Sat Aug 17 04:40:44 UTC 2019: Command 'docker tag actionloop-ruby-v2.6 whisk/actionloop-ruby-v2.6:latest' failed with exitCode 1, no more retries left, aborting...

:core:ruby2.6ActionLoop:tagImage FAILED

@sciabarracom do you know how to fix this?

@sciabarracom
Copy link
Contributor

sciabarracom commented Aug 17, 2019

Yes I mentioned on the mailing list this problem, we need a new release of the sources of the go-runtime with action loop. In the meanwhile I can work around building straight from git. I prepare a PR for this.

@sciabarracom
Copy link
Contributor

check PR#33

@sciabarracom
Copy link
Contributor

Hm the build now it is failing for a reason related to akka.

Detected possible incompatible versions on the classpath. Please note that a given Akka version MUST be the same across all modules of Akka that you are using, e.g. if you use [2.5.22] all other modules that are released together MUST be of the same version. Make sure you're using a compatible set of libraries. Possibly conflicting versions [2.5.3, 2.5.22, 2.5.7] in libraries [akka-cluster-metrics:2.5.3, akka-protobuf:2.5.22, akka-actor:2.5.22, akka-slf4j:2.5.22, akka-remote:2.5.7, akka-cluster:2.5.7, akka-distributed-data:2.5.3, akka-stream:2.5.22, akka-stream-testkit:2.5.22, akka-cluster-tools:2.5.3]

Can you suggest a fix?

@dgrove-oss
Copy link
Member

I thought I got a successful build in #30 that fixed this. Been on vacation. I will take a look once I'm unburied...

@rabbah
Copy link
Member Author

rabbah commented Aug 22, 2019

I don't know how these tests passed in the past - the stdout sentinel is currently only emitted when the server is shutdown and so all the tests which check for the stdout sentinel fail.

@dgrove-oss
Copy link
Member

The github settings for this repo are not right; allowing merges without successful travis runs. Guess we should not ask infra to fix that until we actually can get a clean run though..

@rabbah
Copy link
Member Author

rabbah commented Aug 22, 2019

Yep I noticed and was using it to our advantage right now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants