@PavelBal OK, this can be merged now. Finally, the artifacts are created both for Windows and Linux (Ubuntu 22).
All tests run through under Linux - very nice!
Linux (Ubuntu 22.04) test summary
```
══ Warnings ═══════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════
── Warning (test-utilities-pk-analysis.R:31:3): it can return pk analysis for sparse population and only return ids defined in the population file ──
One or more parsing issues, call `problems()` on your data frame for details, e.g.:
dat <- vroom(...)
problems(dat)
Backtrace:
▆
1. ├─ospsuite::pkAnalysesToDataFrame(pkAnalyses) at test-utilities-pk-analysis.R:31:3
2. │ ├─base::tryCatch(...)
3. │ │ └─base (local) tryCatchList(expr, classes, parentenv, handlers)
4. │ └─readr::read_csv(...)
5. │ └─vroom::vroom(...)
6. │ └─vroom:::vroom_(...)
7. └─cli (local) ``(``, "vroom_parse_issue")
── Warning (test-utilities-pk-analysis.R:59:3): It can convert valid pk-analysis results to data frame ──
One or more parsing issues, call `problems()` on your data frame for details, e.g.:
dat <- vroom(...)
problems(dat)
Backtrace:
▆
1. ├─ospsuite::pkAnalysesToDataFrame(pkAnalyses = pkAnalyses) at test-utilities-pk-analysis.R:59:3
2. │ ├─base::tryCatch(...)
3. │ │ └─base (local) tryCatchList(expr, classes, parentenv, handlers)
4. │ └─readr::read_csv(...)
5. │ └─vroom::vroom(...)
6. │ └─vroom:::vroom_(...)
7. └─cli (local) ``(``, "vroom_parse_issue")
[ FAIL 0 | WARN 2 | SKIP 36 | PASS 932 ]
```
When merging from r-sharp-r6 into develop, all the paths C:/projects/ospsuite-r-rsharp/... must be replaced with C:/projects/ospsuite-r/...
Theoretically, appveyor provides environment variable for this (APPVEYOR_BUILD_FOLDER) - but somehow it does not work when passing to rake.
@PavelBal OK, this can be merged now. Finally, the artifacts are created both for Windows and Linux (Ubuntu 22). All tests run through under Linux - very nice!
Linux (Ubuntu 22.04) test summary
``` ══ Warnings ═══════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════════ ── Warning (test-utilities-pk-analysis.R:31:3): it can return pk analysis for sparse population and only return ids defined in the population file ── One or more parsing issues, call `problems()` on your data frame for details, e.g.: dat <- vroom(...) problems(dat) Backtrace: ▆ 1. ├─ospsuite::pkAnalysesToDataFrame(pkAnalyses) at test-utilities-pk-analysis.R:31:3 2. │ ├─base::tryCatch(...) 3. │ │ └─base (local) tryCatchList(expr, classes, parentenv, handlers) 4. │ └─readr::read_csv(...) 5. │ └─vroom::vroom(...) 6. │ └─vroom:::vroom_(...) 7. └─cli (local) `When merging from r-sharp-r6 into develop, all the paths C:/projects/ospsuite-r-rsharp/... must be replaced with C:/projects/ospsuite-r/... Theoretically, appveyor provides environment variable for this (
APPVEYOR_BUILD_FOLDER) - but somehow it does not work when passing to rake.