, 's patch in the previous comment will take care of this. Closing.

anything needed from infra or this issue will be solved with the patch to the project?

Here is the patch:

Use 'mktemp' to create the build directory
https://gerrit.ovirt.org/72840

is completely right, mktemp is better than a fixed path, I will submit a patch to change that. Note that the only possible downside is that in some distributions (Fedora, for example) the /tmp directory is mounted by default as a tmpfs filesystem, so in those cases the build will run completely in memory, which may cause issues in low memory environments.

Unfortunately this is not something we can fix easily for now. The job names have to be verbose because we have many of them.

You are running inside an isolated mock environment, so theoretically we could set $PWD to anything. But there are some scenarios where things inside mock interact with things outside of it (e.g. Lago/libvirt), and hence the paths inside mock need to match those outside.

Given that you are in mock you can makdir and cd anywhere to work around this. This essentially what did.

There is one thing I'd change with Juan`s patch to future-proof it, and also enable using the check-patch.sh script locally without mock_runner.sh. That is using mktemp to get a work directory under /tmp instead of hard-coding /b. That will make it work even if you don`t get root permissions.

was kind enough to work around this issue in our project by setting the 'build_dir' to 'b' – see https://gerrit.ovirt.org/#/c/72823

is there anything that can be done more globally that you can think of? If not, feel free to close this.