Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
disable lockfile generation in
callr
,testthat::tests
andR CMD CHECK
#1346disable lockfile generation in
callr
,testthat::tests
andR CMD CHECK
#1346Changes from 4 commits
2d2883c
9e5a8d3
7bc4ab4
d54cb80
1862043
1dd4758
14d4a14
adb8440
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
a question
what would happen if we do
load_all()
and thentest()
?Do I understand correctly that the option would be set to true and then lockfile created inside the tests?
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.
Let me check, good question
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 actually think that
Sys.getenv("TESTTHAT")
flag is set after the package is loaded during tests, and the initial value ofgetOption('teal.lockfile.enable')
is set toTRUE
during tests. Not as I would expect it to workI added this snippet to check the behavior of this flag during checks.
This made me think we actually need to disable the creation of the lockfile inside
srv_teal_lockfile
, ifSys.getenv("TESTTHAT")
gets set later after the package is loadedThere 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.
Sys.getenv("TESTTHAT")
is set attestthat::test_that
, not atdevtools::test()
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 got a similar idea. And I was thinking about this particular example in my previous comment here
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.
With this commit 1862043 I moved the functionality inside
srv_teal_lockfile
so the checks are made on lockfile execution.If the option was set before the lockfile was called, then the option is superior to the circumstances check