Conversation
| - mkdir -p ~/.R | ||
| - echo 'CFLAGS=-g0'> ~/.R/Makevars # No -g because -g increases datatable.so size from 0.5MB to 1.5MB and breaches 'installed package size <= 5MB' note | ||
| - echo 'CXXFLAGS=-g0' >> ~/.R/Makevars | ||
| - echo 'CFLAGS=-g0 -O2 -fopenmp -Wall -pedantic -fstack-protector-strong -D_FORTIFY_SOURCE=2'> ~/.R/Makevars # -g0 because -g increases datatable.so size from 0.5MB to 1.5MB and breaches 'installed package size <= 5MB' note |
There was a problem hiding this comment.
these are the defaults flags, they were disabled when writing just -g0 to Makevars so adding them now
|
I added the 1.12.4 milestone, but then removed it because this isn't the package. So it might be wasteful to pollute the tag with non-package tasks. On the other hand we're using the milestone tag to mark what's going ahead now, or not. Maybe the rule should be if it's tagged CI then we shouldn't mark the milestone. |
Codecov Report
@@ Coverage Diff @@
## master #3880 +/- ##
=======================================
Coverage 99.42% 99.42%
=======================================
Files 72 72
Lines 13498 13498
=======================================
Hits 13421 13421
Misses 77 77Continue to review full report at Codecov.
|
|
I think it is fine to tag milestone for stuff that is in .Rbuildignore |
|
Even when having such a rule, there is no way to ensure we align to it always. It is easier to have a rule the other way around. |
|
PR fixed previous failure state is now due to grep, for some reason, ci yaml line is run in a job without leading OK, |
follow up of #3878