Skip to content

Conversation

shikokuchuo
Copy link
Member

@shikokuchuo shikokuchuo commented Aug 22, 2025

Fixes #236.

The failing tests have not been touched for multiple years, nor has code that affect these been changed in this release.
Also we make extensive rhub check runs prior to release (including MKL) e.g. at https://github.com/r-lib/later/actions/runs/17038400115.

I am able to re-produce the series of 3 test failures if and only if the run_now() in the g() function fails to execute the prior later() call.

  • Reproduce by removing the 0.5 delay in later() and commenting out the run_now() in g().
  • This causes the cascade of subsequent run_now() calls to run the previous later call rather than the expected one
  • If the initial test actually failed, we would get different error messages for the subsequent errors (if they failed independently themselves)

Although implausible, seems not impossible under extreme load.

The solution is to simply wait a full 2 secs in g().

@shikokuchuo shikokuchuo merged commit c9a69ab into main Aug 26, 2025
36 checks passed
@shikokuchuo shikokuchuo deleted the fix-tests branch August 26, 2025 08:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CRAN checks
1 participant