You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 31, 2023. It is now read-only.
Priority label is set to the lowest by default. To setup higher priority please change the label P0 label is set for Severity-Critical/Effort-easy
P1 label is set for Severity-Critical/Effort-hard
P2 label is set for Severity-Low/ Effort-easy
P3 label is set for Severity-Low/Effort-hard
Description
This happens during subtask computation on the provider's side. The error is most likely related to the CPU budget being incorrectly calculated and exceeding the expected value range.
2020-01-16 01:48:42 WARNING golem.docker.task_thread Task error - exit_code=2
stderr:
invalid value "25168333333333333334" for flag -l: value out of range
Usage of docker-cgroups-stats:
-l uint
CPU usage limit for the subprocess (in seconds) (default 18446744073709551615)
-o string
path to output file (default "/golem/stats/cgroups_stats.json")
-s string
cgroup subsystems to be included in the stats (as comma-separated strings) (default "cpuacct,memory")
The text was updated successfully, but these errors were encountered:
Golem Version: 0.22
Golem-Messages version (leave empty if unsure):
Electron version (if used):
OS [e.g. Windows 10 Pro]: Ubuntu 18.04.3 LTS
Branch (if launched from source): b0.22
Mainnet/Testnet: mainnet
Priority label is set to the lowest by default. To setup higher priority please change the label
P0 label is set for Severity-Critical/Effort-easy
P1 label is set for Severity-Critical/Effort-hard
P2 label is set for Severity-Low/ Effort-easy
P3 label is set for Severity-Low/Effort-hard
Description
This happens during subtask computation on the provider's side. The error is most likely related to the CPU budget being incorrectly calculated and exceeding the expected value range.
The text was updated successfully, but these errors were encountered: