#46 buildbot's build sometimes fails because it can't access disk
Closed: Fixed Opened 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:

http://taskotron-dev.fedoraproject.org/taskmaster/builders/i386/builds/4689
http://taskotron-dev.fedoraproject.org/taskmaster/builders/all/builds/3989
http://taskotron-dev.fedoraproject.org/taskmaster/builders/i386/builds/5101
http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/6245
http://taskotron-dev.fedoraproject.org/taskmaster/builders/all/builds/4094
http://taskotron-dev.fedoraproject.org/taskmaster/builders/all/builds/4087
http://taskotron-dev.fedoraproject.org/taskmaster/builders/all/builds/4062
http://taskotron-dev.fedoraproject.org/taskmaster/builders/all/builds/4179
http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/7946
http://taskotron-dev.fedoraproject.org/taskmaster/builders/x86_64/builds/7836

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?


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.

@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.

◀ Merged tasks: T290.

This seems to be fixed with the buildbot configuration change.

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

Metadata