[golemfactory/golem] Task computing error, because something in peewee (#2823)

When this had happened in the network were two tasks, one in timeout, second one in computations. Freshly set network, no other tasks yet. Three nodes, test mainnet as provider, and two my nodes, one requesting, one providing. On requestor was computed simple task with one frame, ten subtasks. Seven subtasks were computed by test mainnet node, one by one, on the eighth subtask test mainnet node had failed with timeout, for no visible reason.
««
mainnet-gf-3 git 25f0f0e4-6335-11e8-81d5-a8e8ed0bb427 0:00:00 Finished 100.00 %
mainnet-gf-3 git 9725dbba-6335-11e8-8fbe-a8e8ed0bb427 0:00:00 Finished 100.00 %
mainnet-gf-3 git 16b2d54c-6336-11e8-9d0a-a8e8ed0bb427 0:00:00 Finished 100.00 %
mainnet-gf-3 git bf61828c-6336-11e8-9cba-a8e8ed0bb427 0:00:00 Finished 100.00 %
mainnet-gf-3 git 85dcb4f0-6337-11e8-8d83-a8e8ed0bb427 0:00:00 Finished 100.00 %
mainnet-gf-3 git 1ddc5cbe-6338-11e8-8751-a8e8ed0bb427 0:00:00 Finished 100.00 %
mainnet-gf-3 git ad8ec62e-6338-11e8-94d5-a8e8ed0bb427 0:00:00 Finished 100.00 %
mainnet-gf-3 git 56c7b166-6339-11e8-8ad8-a8e8ed0bb427 0:00:00 Failure 0.00 %
«`
Checked subtask in cli:

«`results: []
status: Failure
stderr: ‘[GOLEM] Timeout’
stdout: «`

Task have been continued on other node, set in the meantime.

Запись редактировалась последний раз: May 30, 2018, 8:02 pm