Skip to content

Conversation

@pcmoritz
Copy link
Contributor

@pcmoritz pcmoritz commented Oct 31, 2018

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

@pcmoritz
Copy link
Contributor Author

Can somebody help looking into what is going on with the code coverage? I'm not sure how it is supposed to work.

@wesm
Copy link
Member

wesm commented Oct 31, 2018

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

@wesm
Copy link
Member

wesm commented Oct 31, 2018

I'm AFK today but @pitrou may have an idea

@pcmoritz
Copy link
Contributor Author

Ah ok, thanks!

@pitrou
Copy link
Member

pitrou commented Oct 31, 2018

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?

@pcmoritz
Copy link
Contributor Author

Ok, I replaced it with gcc (4.9 actually to make it compatible with gandiva for #2822) and it should be ready to merge.

@pitrou pitrou changed the title ARROW-3659: Fix Travis matrix entry 2 to use clang instead of gcc ARROW-3659: [CI] Fix Travis matrix entry 2 to use clang instead of gcc Oct 31, 2018
@pcmoritz pcmoritz changed the title ARROW-3659: [CI] Fix Travis matrix entry 2 to use clang instead of gcc ARROW-3659: Fix Travis matrix entry 2 documentation to use gcc Oct 31, 2018
# - ARROW_TRAVIS_PYTHON_BENCHMARKS=1
- CC="clang-6.0"
- CXX="clang++-6.0"
- MATRIX_EVAL="CC=gcc-4.9 && CXX=g++-4.9"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why MATRIX_EVAL?

Copy link
Contributor Author

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).

Copy link
Contributor Author

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)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uh, I see, thanks.

Copy link
Member

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

@pcmoritz pcmoritz changed the title ARROW-3659: Fix Travis matrix entry 2 documentation to use gcc ARROW-3659: [CI] Fix Travis matrix entry 2 documentation to use gcc Oct 31, 2018
Copy link
Member

@pitrou pitrou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@codecov-io
Copy link

codecov-io commented Oct 31, 2018

Codecov Report

Merging #2878 into master will decrease coverage by 0.08%.
The diff coverage is n/a.

Impacted file tree graph

@@            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
Impacted Files Coverage Δ
go/arrow/math/int64_avx2_amd64.go 0% <0%> (-100%) ⬇️
go/arrow/memory/memory_avx2_amd64.go 0% <0%> (-100%) ⬇️
go/arrow/math/float64_avx2_amd64.go 0% <0%> (-100%) ⬇️
go/arrow/math/uint64_avx2_amd64.go 0% <0%> (-100%) ⬇️
go/arrow/math/float64_amd64.go 33.33% <0%> (-33.34%) ⬇️
go/arrow/math/int64_amd64.go 33.33% <0%> (-33.34%) ⬇️
go/arrow/math/uint64_amd64.go 33.33% <0%> (-33.34%) ⬇️
go/arrow/math/math_amd64.go 31.57% <0%> (-31.58%) ⬇️
go/arrow/memory/memory_amd64.go 28.57% <0%> (-28.58%) ⬇️
cpp/src/arrow/compute/kernels/cast.cc 91.27% <0%> (-0.04%) ⬇️
... and 3 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a56c009...d41c66c. Read the comment docs.

Copy link
Member

@kou kou left a 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.

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

Successfully merging this pull request may close these issues.

5 participants