action #155458
Updated by mkittler 3 months ago
## Observation
https://build.opensuse.org/package/live_build_log/devel:languages:perl/perl-Mojo-IOLoop-ReadWriteProcess/openSUSE_Tumbleweed/x86_64
fails and I don't even see the error:
```
…
[ 108s] t/12_mocked_container.t .. ok
[ 108s] t/13_shared.t ............ skipped: Skipped unless TEST_SHARED is set
[ 108s] All tests successful.
[ 108s] Files=15, Tests=69, 100 wallclock secs ( 0.08 usr 0.03 sys + 4.21 cusr 0.74 csys = 5.06 CPU)
[ 108s] Result: PASS
…
[ 108s] + RPM_EC=0
[ 108s] ++ jobs -p
[ 108s] + exit 0
[ 108s] Executing(%license): /usr/bin/bash -e /var/tmp/rpm-tmp.3qVKzU
[ 108s] + umask 022
[ 108s] + cd /home/abuild/rpmbuild/BUILD
[ 108s] + cd Mojo-IOLoop-ReadWriteProcess-0.34
[ 108s] + LICENSEDIR=/home/abuild/rpmbuild/BUILDROOT/perl-Mojo-IOLoop-ReadWriteProcess-0.340.0-38.11.x86_64/usr/share/licenses/perl-Mojo-IOLoop-ReadWriteProcess
[ 108s] + export LC_ALL=
[ 108s] + LC_ALL=
[ 108s] + export LICENSEDIR
[ 108s] + /usr/bin/mkdir -p /home/abuild/rpmbuild/BUILDROOT/perl-Mojo-IOLoop-ReadWriteProcess-0.340.0-38.11.x86_64/usr/share/licenses/perl-Mojo-IOLoop-ReadWriteProcess
[ 108s] + cp -pr /home/abuild/rpmbuild/BUILD/Mojo-IOLoop-ReadWriteProcess-0.34/LICENSE /home/abuild/rpmbuild/BUILDROOT/perl-Mojo-IOLoop-ReadWriteProcess-0.340.0-38.11.x86_64/usr/share/licenses/perl-Mojo-IOLoop-ReadWriteProcess
[ 108s] + RPM_EC=0
[ 108s] ++ jobs -p
[ 108s] + exit 0
[ 108s] Broken pipe
[ 108s] ### VM INTERACTION START ###
[ 108s] [ 105.200672][ T1] sysrq: Power Off
[ 108s] [ 105.201394][ T84] reboot: Power down
[ 108s] ### VM INTERACTION END ###
[ 108s]
[ 108s] i03-ch1c failed "build perl-Mojo-IOLoop-ReadWriteProcess.spec" at Wed Feb 14 08:02:04 UTC 2024.
```
EDIT: By now https://build.opensuse.org/package/live_build_log/devel:languages:perl/perl-Mojo-IOLoop-ReadWriteProcess/openSUSE_Tumbleweed/x86_64 is back to "succeeded" not showing "Broken pipe". I suggest to actually just report to OBS upstream about the errors, ignorable warnings, etc.
## Acceptance criteria
* **AC1**: The problem has been reported to upstream OBS (either already reported or new report)
## Suggestions
* Lookup if there any existing issues about such confusing error messages or report a new one
* Learn from OBS experts how to better handle such situation and share with the team