Issue #46: buildbot's build sometimes fails because it can't access disk - taskotron

taskotron

#46 buildbot's build sometimes fails because it can't access disk

Closed: Fixed None Opened 9 years ago by jsedlak.

From time to time, last step of buildbot's build (cat /var/log/taskotron/taskotron.log) fails with cat: /var/log/taskotron/taskotron.log: No such file or directory. It's happening on dev machine on all clients (taskotron-client26, 27, 28 and 29).

See for example these builds:

Sometimes, even runtask step fails with disk-related issue, for example here:

http://taskotron-dev.fedoraproject.org/taskmaster/builders/all/builds/3965
http://taskotron-dev.fedoraproject.org/taskmaster/builders/i386/builds/5900

All these errors are from rpmlint task, but it doesn't seem likely that it's bug in rpmlint - perhaps it's caused by how fast rpmlint task is?

mkrizek commented 9 years ago

Just a note: it happens on dev machine because it's the only machine that runs the cat log step, it's not present on stg/prod yet.

kparal commented 9 years ago

@tflink found out it was a configuration issue, multiple tasks from different builders were run at the same time on the same buildslave. Dev env should be soon adjusted to avoid this situation, we'll see whether it helps or not.

kparal commented 9 years ago

◀ Merged tasks: T290.

kparal commented 9 years ago

This seems to be fixed with the buildbot configuration change.

Metadata Update from @jsedlak:
- Issue tagged with: infrastructure

6 years ago

Metadata

Assignee

None

Tags

Blocking

None

Depending on

None

Priority

High

taskotron

Source Code

#46 buildbot's build sometimes fails because it can't access disk Closed: Fixed None Opened 9 years ago by jsedlak.

Metadata

infra

#46 buildbot's build sometimes fails because it can't access disk

Closed: Fixed None Opened 9 years ago by jsedlak.