Bug#990244: tests/streams: Failing test on pipe stdout file descriptor

[Dennis Filder <d.filder@web.de>]

Control: tags -1 moreinfo
X-Debbugs-CC: Ariel D'Alessandro <ariel.dalessandro@collabora.com>

It could be that OBS opens the pipe as a privileged process, forks,
then drops privileges afterwards such that the child process is
precluded from reopening the inode that backs the file descriptor
clisp operates on.

You'd somehow have to find a way to invoke "stat -L
/proc/<pid>/fd/<fdno>" on the failing file quickly enough to find out
if this is the case.  Inserting sleeps into the test could buy you
more time.

Alternatively (and assuming you use ocs) tools like socat/ptywrap
could maybe be used via $OSC_SU_WRAPPER to hook the child process onto
a pty (which should also be created after dropping the privileges).
Or you could try to run the build as root (osc build
--userootforbuild) and see if the error persists.

Regards,
Dennis