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

[R-package] [ci] added check on number of R CMD CHECK notes #2942

Merged
merged 1 commit into from
Mar 25, 2020

Conversation

jameslamb
Copy link
Collaborator

Currently in CI, we run R CMD check on the R package and fail builds if ERRORs or WARNINGs are encountered. As we get closer to CRAN (#629), I'd like to start limiting the NOTEs being generated. Currently Linux and macOS builds have 3 NOTEs. One is being addressed in #2911 , the other two are not problematic.

Following @StrikerRUS 's suggestion in #2911 (comment), this PR proposing putting an upper limit on the number of NOTEs.

This PR has it set to 3, and mainly introduces how we'll enforce this. I think we should merge this, then change it from 3 to 2 on #2911 . I think it's better for this to be a separate PR so that other changes in the repo don't introduce new notes (like I accidentally did in #2803 and then had to fix in #2928 ).

Copy link
Collaborator

@StrikerRUS StrikerRUS left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

Can you please push a commit with ALLOWED_CHECK_NOTES=2 and then revert it to make sure that corresponding CI builds fail as expected?

@jameslamb
Copy link
Collaborator Author

jameslamb commented Mar 25, 2020

LGTM, thanks!

Can you please push a commit with ALLOWED_CHECK_NOTES=2 and then revert it to make sure that corresponding CI builds fail as expected?

oh sure! I did that on my fork already actually

Travis: https://travis-ci.org/github/jameslamb/LightGBM/jobs/666851877
Commit: jameslamb@05d8694

You can see this error in the logs:

image

@StrikerRUS
Copy link
Collaborator

@jameslamb
Great, many thanks!

@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants