Closed ederenn closed 5 years ago
Solution
Create empty __init__.py
files at the following locations:
apps/glambda/__init__.py
apps/glambda/benchmarks/__init__.py
apps/glambda/task/__init__.py
after fix another another thing is not working
2019-07-02 19:18:35 ERROR golem.task.benchmarkmanager Unable to run WASM benchmark:
2019-07-02 19:18:35 CRITICAL golem.client Can't start network. Giving up.
Traceback (most recent call last):
File "/home/buildbot-worker/worker/buildpackage_linux/build/golem/client.py", line 331, in start
File "/home/buildbot-worker/worker/buildpackage_linux/build/golem/client.py", line 383, in start_network
File "/home/buildbot-worker/worker/buildpackage_linux/build/golem/task/taskserver.py", line 131, in __init__
File "/home/buildbot-worker/worker/buildpackage_linux/build/golem/task/taskcomputer.py", line 78, in __init__
File "/home/buildbot-worker/worker/buildpackage_linux/build/golem/core/deferred.py", line 33, in sync_wait
File "/home/buildbot-worker/worker/buildpackage_linux/build/.venv/lib/python3.6/site-packages/twisted/python/failure.py", line 385, in raiseException
Exception
2019-07-02 19:18:35 INFO golem.client Shutting down ...
2019-07-02 19:18:35 INFO golem.client Stopping network ...
Description
Golem Version: GOLEM Version: 0.20.0+dev3.gc178317
Golem-Messages version (leave empty if unsure): golem_messages Version: 3.7.0
Electron version (if used): 0.2.0 v9
OS [e.g. Windows 10 Pro]: all systems
Branch (if launched from source): -
Mainnet/Testnet: testnet
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 of the issue:
It is not possible to start testnet Golem on any OS in
golem.log
Actual result:
Golem is crashing
Steps To Reproduce
Logs and any additional context
Proposed Solution?
(Optional: What could be a solution for that issue)