Repository: single-cell-data/TileDB-SOMA (language: python)

Issue:
[r] No more "Last 13 lines of output:" in CI
As discussed in Slack


Discussion / hints:
Likely redundant because of https://github.com/single-cell-data/TileDB-SOMA/blob/main/apis/r/tools/r-ci.sh#L42 
## [Codecov](https://app.codecov.io/gh/single-cell-data/TileDB-SOMA/pull/1871?src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=single-cell-data) Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: Your organization needs to install the [Codecov GitHub app](https://github.com/apps/codecov/installations/select_target) to enable full functionality.

[see 34 files with indirect coverage changes](https://app.codecov.io/gh/single-cell-data/TileDB-SOMA/pull/1871/indirect-changes?src=pr&el=tree-more&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=single-cell-data)


:loudspeaker: Thoughts on this report? [Let us know!](https://about.codecov.io/pull-request-comment-report/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=single-cell-data).

I am seeing CI output I didn't see before. This is a good thing.
What's the test command?  Are you going through `r-ci.sh` which should have the value, or via `R CMD ...` directly?
@eddelbuettel I am seeing more output before in CI logs linked to from these PRs here in GitHub. I am happy with that fact.
@johnkerl I am happy you are happy but you did not answer my question to which my curious mind would still love an answer:  how did you trigger the tests so that setting YML fixed?

(Longer story R also reflects env variables just for checking from a file `~/.R/check.Renviron`, if it exists, so I have been contemplating having the `bootstrap` step during `r-ci.sh` run create it.  For that more info hence my question.)
@eddelbuettel I don't know the answer to your question.

* Before this PR I was seeing "Last 13 lines of output" when clicking through "Checks" links on PRs in this repo
* After this PR I am seeing more output
* I changed nothing other than what you see on this PR
* That is all I know, and all I need to know
@johnkerl So you are saying that the test was triggered as before by `cd apis/r && tools/r-ci.sh run_tests`. I asked you because during the ongoing discussions around the CI fail we had brought the topic of triggering the tests differently (e.g. via a call to `R CMD check ...`.    So what this shows then is that `r-ci.sh` was supposed to already supply the setting but didn't.  This gives me more to work with so thanks for all your continued help in finding this.

Fix patch:
diff --git a/.github/workflows/r-valgrind.yaml b/.github/workflows/r-valgrind.yaml
index 0014714b1e..2ea43c229a 100644
--- a/.github/workflows/r-valgrind.yaml
+++ b/.github/workflows/r-valgrind.yaml
@@ -7,6 +7,9 @@ on:
   schedule:
     - cron: "23 4 * * *"
 
+env:
+  _R_CHECK_TESTS_NLINES_: 0
+
 jobs:
   r-valgrind:
     runs-on: ubuntu-latest


Test patch:
diff --git a/.github/workflows/r-python-interop-testing.yml b/.github/workflows/r-python-interop-testing.yml
index 994c0e1971..079ee15331 100644
--- a/.github/workflows/r-python-interop-testing.yml
+++ b/.github/workflows/r-python-interop-testing.yml
@@ -114,3 +114,4 @@ jobs:
         run: python -m pytest apis/system/tests/
         env:
           TILEDB_SOMA_INIT_BUFFER_BYTES: 33554432 # accommodate tiny runners
+          _R_CHECK_TESTS_NLINES_: 0