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

Want to understand better why native extensions are failing on CircleCI #24

Closed
kigster opened this issue Dec 3, 2019 · 3 comments
Closed
Assignees
Labels
outdated ruby:native-extensions Issues related to native extensions written in C
Milestone

Comments

@kigster
Copy link
Contributor

kigster commented Dec 3, 2019

I managed to get CircleCI build passing for the https://github.com/bazelruby/ruby-monorepo repository, but only after I removed rubocop and other gems that depended on gems needing native extensions. I am able to install rubocop and run it on CI via a BASH script, but not via Bazel.

Here is one example CI build that failed installing a gem with native extension:
https://app.circleci.com/jobs/github/bazelruby/ruby-monorepo/40

The actual error is this:

ake "DESTDIR="
compiling adj_matrix.c
gcc: error trying to exec 'cc1': execvp: No such file or directory
make: *** [Makefile:245: adj_matrix.o] Error 1
@kigster kigster added the ruby:native-extensions Issues related to native extensions written in C label Dec 3, 2019
@yugui
Copy link
Contributor

yugui commented Dec 3, 2019

Is this issue already fixed in master?

If otherwise, I'd like to know the url of the circleci build which is failing with rules_ruby's develop branch.

@yugui yugui assigned kigster and unassigned yugui Dec 3, 2019
@kigster
Copy link
Contributor Author

kigster commented Dec 3, 2019

So, rubocop depends on a gem with a native extension. The build passed after I removed rubocop from the gemfile and installed it manually.

Here is the build that failed while rubocop was still in the gemfile:

https://app.circleci.com/jobs/github/bazelruby/ruby-monorepo/40/parallel-runs/0/steps/0-105

The failing gem is jarro_winkler

@kigster kigster assigned yugui and unassigned kigster Dec 3, 2019
@kigster kigster added this to the M-0.2 milestone Dec 5, 2019
@kigster
Copy link
Contributor Author

kigster commented Jan 4, 2020

It appears that changing JVM args to increase memory fixes this issue, and native extension are able to be built. This + removing env -i.

@kigster kigster closed this as completed Jan 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
outdated ruby:native-extensions Issues related to native extensions written in C
Projects
None yet
Development

No branches or pull requests

2 participants