Build Update for libvirt/libvirt
-------------------------------------
Build: #1326
Status: Errored
Duration: 14 mins and 32 secs
Commit: 5babc51 (master)
Author: John Ferlan
Message: fdstream: Report error from the I/O thread
https://bugzilla.redhat.com/show_bug.cgi?id=1529059
Commit id 0fe4aa14 added the thread specific error message
reporting (or save) to virFDStreamEvent; however, as processing
goes via virStream{Send|SendHole|Recv} via calls from
daemonStreamHandle{WriteData|Hole|Read} the last error
gets reset in the main libvirt API's thus, whatever error
may have been set as last error will be cleared prior to
the error paths using it resulting in the generic error
on the client side.
For each of the paths that check threadQuit or threadErr,
check if threadErr was set and set it agian if there isn't
a last error (e.g. some other failure) set so that the
message can be provided back to the client.
Signed-off-by: John Ferlan <jferlan(a)redhat.com>
ACKed-by: Michal Privoznik <mprivozn(a)redhat.com>
View the changeset:
https://github.com/libvirt/libvirt/compare/6d21d9bccb05...5babc51912f9
View the full build log and details:
https://travis-ci.org/libvirt/libvirt/builds/389037862?utm_source=email&a...
--
You can configure recipients for build notifications in your .travis.yml file. See
https://docs.travis-ci.com/user/notifications
This email was sent to libvirt-ci(a)redhat.com (mailto:libvirt-ci@redhat.com)
unsubscribe from this list
(
http://clicks.travis-ci.com/track/unsub.php?u=14313403&id=552fcc40d3e...)