Build Update for libvirt/libvirt
-------------------------------------
Build: #68
Status: Fixed
Duration: 19 minutes and 38 seconds
Commit: 058bf55 (master)
Author: Roman Bogorodskiy
Message: tests: fix virfilewrapper
If __lxstat() and __xstat() functions are not available, build fails with:
CC virfilewrapper.o
virfilewrapper.c:180:5: error: no previous prototype for function '__lxstat' [-Werror,-Wmissing-prototypes]
int __lxstat(int ver, const char *path, struct stat *sb)
^
virfilewrapper.c:208:5: error: no previous prototype for function '__xstat' [-Werror,-Wmissing-prototypes]
int __xstat(int ver, const char *path, struct stat *sb)
Luckily, we already check presence of these functions in configure
using AC_CHECK_FUNCS, so just don't wrap these if they're not available.
Signed-off-by: Roman Bogorodskiy <bogorodskiy(a)gmail.com>
View the changeset: https://github.com/libvirt/libvirt/compare/40824174258a...058bf5549f66
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/230343200?utm_source=email&utm…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications
Build Update for libvirt/libvirt
-------------------------------------
Build: #50
Status: Passed
Duration: 26 minutes and 56 seconds
Commit: 42faf31 (v3.3.0-rc2)
Author: Jiri Denemark
Message: client: Report proper close reason
When we get a POLLHUP or VIR_EVENT_HANDLE_HANGUP event for a client, we
still want to read from the socket to process any accumulated data. But
doing so inevitably results in an error and a call to
virNetClientMarkClose before we get to processing the hangup event (and
another call to virNetClientMarkClose). However the close reason passed
to the second virNetClientMarkClose call is ignored because another one
was already set. We need to pass the correct close reason when marking
the socket to be closed for the first time.
https://bugzilla.redhat.com/show_bug.cgi?id=1373859
Signed-off-by: Jiri Denemark <jdenemar(a)redhat.com>
View the changeset: https://github.com/libvirt/libvirt/compare/v3.3.0-rc2
View the full build log and details: https://travis-ci.org/libvirt/libvirt/builds/228376192?utm_source=email&utm…
--
You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications