Skip to content

Actions: futureverse/furrr

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
272 workflow runs
272 workflow runs

Filter by Workflow

⌥ + click/return to exclude

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
POC: Signal progress via progressr R-CMD-check.yaml #254: Pull request #305 opened by DavisVaughan
5m 24s feature/progressr
feature/progressr
5m 24s
POC: Signal progress via progressr format-suggest.yaml #8: Pull request #305 opened by DavisVaughan
13s
13s
Unbalanced Load distribution on first run pr-commands.yaml #340: Issue comment #247 (comment) created by mfakaehler
1s
1s
pr-commands.yaml pr-commands.yaml #339: created by HenrikBengtsson
1s
1s
future_map not obviously faster than map in simple linear regression setting pr-commands.yaml #338: Issue comment #267 (comment) created by DavisVaughan
1s
1s
Unbalanced Load distribution on first run pr-commands.yaml #337: Issue comment #247 (comment) created by DavisVaughan
1s
1s
Possible memory leaks with future_pwalk() appear related to furrr_options(scheduling = ...) pr-commands.yaml #336: Issue comment #275 (comment) created by DavisVaughan
1s
1s
pr-commands.yaml pr-commands.yaml #335: created by DavisVaughan
1s
1s
Multiple calls of future_map() within a single plan() or script result in massive slowdown. pr-commands.yaml #334: Issue comment #268 (comment) created by DavisVaughan
Skipped
Skipped
Performance regression in future/globals when finding globals in a list of data frames pr-commands.yaml #333: Issue comment #303 (comment) created by DavisVaughan
1s
1s
Best way to run nested furrr functions when running in a HPC pr-commands.yaml #332: Issue comment #291 (comment) created by aimundo
2s
2s
pr-commands.yaml pr-commands.yaml #331: created by HenrikBengtsson
1s
1s
Performance regression in future/globals when finding globals in a list of data frames pr-commands.yaml #330: Issue comment #303 (comment) created by DavisVaughan
1s
1s
Performance regression in future/globals when finding globals in a list of data frames pr-commands.yaml #329: Issue comment #303 (comment) created by DavisVaughan
1s
1s
Performance regression in future/globals when finding globals in a list of data frames pr-commands.yaml #328: Issue comment #303 (comment) created by DavisVaughan
1s
1s
pages build and deployment pages-build-deployment #51: by github-pages Bot
23s gh-pages
gh-pages
23s
pages build and deployment pages-build-deployment #50: by github-pages Bot
59s gh-pages
gh-pages
59s
Use parallelly::availableCores(max = 2L) test-coverage.yaml #253: Commit 6f21565 pushed by DavisVaughan
3m 30s main
main
3m 30s
Use parallelly::availableCores(max = 2L) pkgdown.yaml #205: Commit 6f21565 pushed by DavisVaughan
3m 9s main
main
3m 9s
Use parallelly::availableCores(max = 2L) R-CMD-check.yaml #253: Commit 6f21565 pushed by DavisVaughan
10m 24s main
main
10m 24s
Remove deprecated future_invoke_map() family (#301) R-CMD-check.yaml #252: Commit 48638fa pushed by DavisVaughan
10m 32s main
main
10m 32s
Remove deprecated future_invoke_map() family (#301) test-coverage.yaml #252: Commit 48638fa pushed by DavisVaughan
3m 54s main
main
3m 54s
Remove deprecated future_invoke_map() family (#301) pkgdown.yaml #204: Commit 48638fa pushed by DavisVaughan
2m 34s main
main
2m 34s
Best way to run nested furrr functions when running in a HPC pr-commands.yaml #327: Issue comment #291 (comment) created by HenrikBengtsson
1s
1s
Remove deprecated future_invoke_map() family pkgdown.yaml #203: Pull request #301 opened by DavisVaughan
2m 28s feature/remove-invoke-map
feature/remove-invoke-map
2m 28s