-
Notifications
You must be signed in to change notification settings - Fork 3.9k
ARROW-3659: [CI] Fix Travis matrix entry 2 documentation to use gcc #2878
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
Conversation
|
Can somebody help looking into what is going on with the code coverage? I'm not sure how it is supposed to work. |
|
This is a known issue, we were trying to get clang to work with the coverage in my recent PR but didn't figure it out |
|
I'm AFK today but @pitrou may have an idea |
|
Ah ok, thanks! |
|
I don't think we care much about the compiler here, so I'd just rename the CI entry to reflect that it uses gcc, not clang (there are other entries using clang anyway). What do you think? |
|
Ok, I replaced it with gcc (4.9 actually to make it compatible with gandiva for #2822) and it should be ready to merge. |
| # - ARROW_TRAVIS_PYTHON_BENCHMARKS=1 | ||
| - CC="clang-6.0" | ||
| - CXX="clang++-6.0" | ||
| - MATRIX_EVAL="CC=gcc-4.9 && CXX=g++-4.9" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why MATRIX_EVAL?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
because CC and CXX get exported before Travis re-exports them according to the build matrix (see the JIRA issue printout).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(the other build matrix entries do it the same way)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Uh, I see, thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI: We can find the MATRIX_EVAL technique in Travis CI document: https://docs.travis-ci.com/user/languages/c/#gcc-on-linux
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
Codecov Report
@@ Coverage Diff @@
## master #2878 +/- ##
==========================================
- Coverage 87.63% 87.55% -0.09%
==========================================
Files 412 412
Lines 64048 64048
==========================================
- Hits 56130 56076 -54
- Misses 7846 7898 +52
- Partials 72 74 +2
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI is green.
I'll merge this.
This is a little subtle and is needed because of the order in which Travis evaluates the command line variable definitions (see the JIRA issue).
I also needed to remove a warning due to this: cython/cython#2269
We might be able to bring the warning back once we can depend on cython with cython/cython#2669