BUG FIX: evalFuture() failed to restore objects in globalenv() on MS … #857
Annotations
11 errors and 25 warnings
macOS-latest (release)
No such keg: /opt/homebrew/Cellar/[email protected]
|
ubuntu-latest (3.6)
Running examples in ‘future-Ex.R’ failed
|
ubuntu-latest (3.6)
Unexpected result (of class ‘NULL’ != ‘FutureResult’) retrieved for MultisessionFuture future (label = ‘<none>’, expression = ‘lm(y ~ x - 1, weights = w)’): This suggests that the communication with ‘RichSOCKnode’ #1 on host ‘localhost’ (R version 3.6.3 (2020-02-29), platform x86_64-pc-linux-gnu) is out of sync.
|
ubuntu-latest (3.6)
Running examples in ‘future-Ex.R’ failed
|
ubuntu-latest (3.6)
R CMD check found ERRORs
|
ubuntu-latest (3.6)
Unexpected result (of class 'NULL' != 'FutureResult') retrieved for MultisessionFuture future (label = '<none>', expression = '{; message(sprintf("Calculating tile #%d of %d ...", ii, n),; appendLF = FALSE); fit <- mandelbrot(C); delay(fit); message(" done"); fit; }'): This suggests that the communication with 'RichSOCKnode' #1 on host 'localhost' (R version 3.6.3 (2020-02-29), platform x86_64-pc-linux-gnu) is out of sync.
|
ubuntu-latest (3.6)
Woops!
|
ubuntu-latest (3.6)
Unexpected result (of class 'NULL' != 'FutureResult') retrieved for MultisessionFuture future (label = '<none>', expression = '{; 2; }'): This suggests that the communication with 'RichSOCKnode' #1 on host 'localhost' (R version 3.6.3 (2020-02-29), platform x86_64-pc-linux-gnu) is out of sync.
|
ubuntu-latest (3.6)
Unexpected result (of class 'NULL' != 'FutureResult') retrieved for MultisessionFuture future (label = '<none>', expression = '2'): This suggests that the communication with 'RichSOCKnode' #1 on host 'localhost' (R version 3.6.3 (2020-02-29), platform x86_64-pc-linux-gnu) is out of sync.
|
ubuntu-latest (3.6)
value(b) == 2 is not TRUE
|
ubuntu-latest (3.6)
Unexpected result (of class 'NULL' != 'FutureResult') retrieved for MultisessionFuture future (label = '<none>', expression = '{; ii; }'): This suggests that the communication with 'RichSOCKnode' #1 on host 'localhost' (R version 3.6.3 (2020-02-29), platform x86_64-pc-linux-gnu) is out of sync.
|
macOS-latest (release)
pkgconf 2.3.0_1 is already installed and up-to-date.
To reinstall 2.3.0_1, run:
brew reinstall pkgconf
|
macOS-latest (release)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated
dependents or dependents with broken linkage!
|
windows-latest (devel)
Cache not found for keys: Windows Server 2022 x64 (build 20348)-R version 4.5.0 (ge:16; iid:2fdf6c18-697a-4ba7-b8ef-11c0d92f1327)-1-e2784e8d032e3e9bcf44c2ad1ee33f36b802ee4e3ad2e7a804c63523d6533cd8, Windows Server 2022 x64 (build 20348)-R version 4.5.0 (ge:16; iid:2fdf6c18-697a-4ba7-b8ef-11c0d92f1327)-1-
|
ubuntu-latest (3.6)
Cache not found for keys: Ubuntu 24.04.1 LTS-R version 3.6.3 (2020-02-29)-1-6d53e0acc037aee5914f8a8298e2c32a9ddf747370bb7c306de34a9189390530, Ubuntu 24.04.1 LTS-R version 3.6.3 (2020-02-29)-1-
|
ubuntu-latest (3.6)
restarting interrupted promise evaluation
|
ubuntu-latest (3.6)
restarting interrupted promise evaluation
|
ubuntu-latest (3.6)
R option 'future.globals.resolve' may only be used for troubleshooting. It must not be used in production since it changes how futures are evaluated and there is a great risk that the results cannot be reproduced elsewhere: 'TRUE'
|
ubuntu-latest (3.6)
R option 'future.globals.onMissing' may only be used for troubleshooting. It must not be used in production since it changes how futures are evaluated and there is a great risk that the results cannot be reproduced elsewhere: 'error'
|
ubuntu-latest (3.6)
R option 'future.globals.method' may only be used for troubleshooting. It must not be used in production since it changes how futures are evaluated and there is a great risk that the results cannot be reproduced elsewhere: 'conservative'
|
ubuntu-latest (3.6)
R option 'future.globals.resolve' may only be used for troubleshooting. It must not be used in production since it changes how futures are evaluated and there is a great risk that the results cannot be reproduced elsewhere: 'TRUE'
|
ubuntu-latest (3.6)
R option 'future.globals.onMissing' may only be used for troubleshooting. It must not be used in production since it changes how futures are evaluated and there is a great risk that the results cannot be reproduced elsewhere: 'error'
|
ubuntu-latest (3.6)
R option 'future.globals.method' may only be used for troubleshooting. It must not be used in production since it changes how futures are evaluated and there is a great risk that the results cannot be reproduced elsewhere: 'conservative'
|
ubuntu-latest (3.6)
R option 'future.globals.resolve' may only be used for troubleshooting. It must not be used in production since it changes how futures are evaluated and there is a great risk that the results cannot be reproduced elsewhere: 'TRUE'
|
ubuntu-latest (3.6)
R option 'future.globals.onMissing' may only be used for troubleshooting. It must not be used in production since it changes how futures are evaluated and there is a great risk that the results cannot be reproduced elsewhere: 'error'
|
ubuntu-latest (oldrel)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
windows-latest (release)
Cache not found for keys: Windows Server 2022 x64 (build 20348)-R version 4.4.2 (2024-10-31 ucrt)-1-02bfd689caedc1e9088392bcb983e10000e1447b9c5592acd619c50dd444286d, Windows Server 2022 x64 (build 20348)-R version 4.4.2 (2024-10-31 ucrt)-1-
|
ubuntu-latest (release)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
ubuntu-latest (release) no-immediate-relay-in-psock
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
ubuntu-latest (release) ko
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
ubuntu-latest (release) keepWhere
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
ubuntu-latest (release) zh_TW
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
ubuntu-latest (release) multicore, no-multithreading-in-forks
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
ubuntu-latest (release) zh_CN
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
ubuntu-latest (release) multisession, no-multithreading-in-forks
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
windows-latest (oldrel)
Cache not found for keys: Windows Server 2022 x64 (build 20348)-R version 4.3.3 (2024-02-29 ucrt)-1-aa02b4f6610b808ce8d434a413544c2d48ad1c88e325fca31bced2d29d8c0969, Windows Server 2022 x64 (build 20348)-R version 4.3.3 (2024-02-29 ucrt)-1-
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
Linux-r3.6-results
|
2.66 MB |
|