-
Notifications
You must be signed in to change notification settings - Fork 1k
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
GLCI fixes #5758
GLCI fixes #5758
Conversation
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.
hi Jan it looks ok to me, but I am not really familiar with this, so not sure if I would be able to catch any issues.
.test-install-deps: &install-deps | ||
- Rscript -e 'source(".ci/ci.R"); install.packages(dcf.dependencies("DESCRIPTION", which="most"), quiet=TRUE)' | ||
- Rscript -e 'source(".ci/ci.R"); install.packages(dcf.dependencies("DESCRIPTION", which="all"), repos=file.path("file:", normalizePath("bus/mirror-packages/cran", mustWork=FALSE)), quiet=TRUE)' |
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.
I would start (e.g.) .ci/scripts/
and add .ci/scripts/test-install-deps.R
with:
source(".ci/ci.R")
install.packages(
dcf.dependencies("DESCRIPTION", which="all"),
repos=file.path("file:", normalizePath("bus/mirror-packages/cran", mustWork=FALSE)),
quiet=TRUE
)
This will be more readable and avoid duplication (and hence double maintenance/risk of getting out of sync) across test-intall-deps
and test-install-deps-win
jobs.
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.
Or, we can find a way to put RUN_SCRIPT=if(win) Rscript.exe else Rscript
into env and unify the jobs.
(just noticing the other small diff on Windows getwd()
, so it's probably best to write this into the suggested script)
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.
Quoting arguments from shell also differs
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.
I would start (e.g.)
.ci/scripts/
and add.ci/scripts/test-install-deps.R
with:source(".ci/ci.R") install.packages( dcf.dependencies("DESCRIPTION", which="all"), repos=file.path("file:", normalizePath("bus/mirror-packages/cran", mustWork=FALSE)), quiet=TRUE )This will be more readable and avoid duplication (and hence double maintenance/risk of getting out of sync) across
test-intall-deps
andtest-install-deps-win
jobs.
Unless we will need distinction for some reason, then we ended up having two scripts :)
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.
Quoting arguments from shell also differs
Can't we unify if there's no env inside "
? Anyway, if the shell command is just Rscript -e "source(...)"
it will still be easier to glance & see it looks ~OK.
Unless we will need distinction for some reason, then we ended up having two scripts :)
Looks like not the case yet, we can do some .Platform
/Sys.info()
switching to handle the small differences. Still almost all of the logic between the two jobs is the same, I find it more confusing needing to read long one-line scripts without syntax highlighting.
# flags: gcc -O3 -flto -fno-common -Wunused-result | ||
# tests for compilation warnings | ||
# measure memory usage during tests | ||
test-rel-lin: |
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.
lin
is linux
here? I would just write out linux
I don't see much benefit to saving 2 characters
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.
Yes, it is 3 letters so it aligns better when printing, to win and mac. Maybe lnx then?
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.
That would be less ambiguous, yes
Ditto, basically LGTM but I don't follow 100%. It's just CI though, issues should be easy to detect/fix later, effects on package code are second-order only (e.g. if a mistake in CI eventually lets a mistake pass through PR review unnoticed) |
These CI runs on master so after PR being merged already. Design was made that ghci gives fast feedback and let us do merge, while glci tests thoroughly and we don't have to wait for it. |
towards #5727