Build succeeds but reported as failure?

  • Open
  • quality assurance status badge
Details
One participant
  • Greg Hogan
Owner
unassigned
Submitted by
Greg Hogan
Severity
normal
G
G
Greg Hogan wrote on 18 Mar 17:53 +0100
(address . bug-guix@gnu.org)
CA+3U0Z=26--Y+S0s8_UkP16zs1Xqrpu25R5jW7_BdhvJtUDqcQ@mail.gmail.com
Build log attached. Reported as a failed build ...

build of /gnu/store/rr89l2fmf6ai7l9ipqszralspjn0qnzz-qtwebengine-6.5.3.drv
failed
View build log at
'/var/log/guix/drvs/rr/89l2fmf6ai7l9ipqszralspjn0qnzz-qtwebengine-6.5.3.drv.gz'.

... but the build ran to completion:

$ zcat /var/log/guix/drvs/rr/89l2fmf6ai7l9ipqszralspjn0qnzz-qtwebengine-6.5.3.drv.gz
| tail
`../qtwebengine-everywhere-src-6.5.3/LICENSES/LGPL-3.0-only.txt' ->
`/gnu/store/1cpyi5hapa8kqym9435q96zr38cw2wy0-qtwebengine-6.5.3/share/doc/qtwebengine-6.5.3/LGPL-3.0-only.txt'
`../qtwebengine-everywhere-src-6.5.3/LICENSES/GPL-3.0-only.txt' ->
`/gnu/store/1cpyi5hapa8kqym9435q96zr38cw2wy0-qtwebengine-6.5.3/share/doc/qtwebengine-6.5.3/GPL-3.0-only.txt'
`../qtwebengine-everywhere-src-6.5.3/LICENSES/GPL-2.0-only.txt' ->
`/gnu/store/1cpyi5hapa8kqym9435q96zr38cw2wy0-qtwebengine-6.5.3/share/doc/qtwebengine-6.5.3/GPL-2.0-only.txt'
`../qtwebengine-everywhere-src-6.5.3/LICENSES/GFDL-1.3-no-invariants-only.txt'
-> `/gnu/store/1cpyi5hapa8kqym9435q96zr38cw2wy0-qtwebengine-6.5.3/share/doc/qtwebengine-6.5.3/GFDL-1.3-no-invariants-only.txt'
`../qtwebengine-everywhere-src-6.5.3/LICENSES/BSD-3-Clause.txt' ->
`/gnu/store/1cpyi5hapa8kqym9435q96zr38cw2wy0-qtwebengine-6.5.3/share/doc/qtwebengine-6.5.3/BSD-3-Clause.txt'
phase `install-license-files' succeeded after 0.0 seconds
starting phase `reset-gzip-timestamps'
phase `reset-gzip-timestamps' succeeded after 0.0 seconds
starting phase `compress-documentation'
phase `compress-documentation' succeeded after 0.0 seconds
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 69874@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 69874
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch