future.tests: Tests with resolved and lazy fail

[HenrikBengtsson]

$ Rscript -e future.tests::check --args --test-plan="future.mirai::mirai_multisession" --test-tags=resolved,lazy
── Settings ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
- future.tests version      : 0.6.0.9002
- R_FUTURE_TESTS_ROOT       : 
- Option 'future.tests.root': NULL
- Default test set folder   : /home/henrik/R/x86_64-pc-linux-gnu-library/4.2-CBI-gcc11/future.tests/test-db
- Max number of workers     : 2
- Timeout                   : N/A

── Running 2 test sets with plan(future.mirai::mirai_multisession) ─────────────────────────────────────────────────────────────────────
ℹ Backend package: future.mirai 0.0.0.9002
✔  1. resolved() on lazy futures (1 test) (108ms)                               
✖  2. resolved() - assert non-blocking while launching lazy futures (1 test) (28ms)
  ✖ lazy=FALSE, globals=TRUE, stdout=TRUE
    Error of class ‘simpleError’ with message:
    ss[[kk]] == "created" is not TRUE
    Call:
    eval(expr, envir = envir)
    Output:
    [1] "created" "created" "created"
    [1] "running" "created" "created"
    [1] "running" "running" "created"
    [1] "running" "running" "running"

Number of tests: 2
Number of test steps: 2
Duration: 200ms
Results: 1 ok ✔ | 0 skips ★ | 1 error ✖ | 0 timeouts T

[HenrikBengtsson]

It doesn't matter if we use the default daemon(n, dispatcher = TRUE) or daemon(n, dispatcher = FALSE).

[HenrikBengtsson]

Fixed in future.tests 0.6.0-9006.