On Mon, Feb 19, 2018 at 8:53 AM, Nigel Babu wrote:
> Hello,
>
> As you all most likely know, we store the tarball of the binaries and core
> if there's a core during regression. Occasionally, we've introduced a bug
> in Gluster and this tar can take up a lot of space. This has happened
> recently
Hello,
As you all most likely know, we store the tarball of the binaries and core
if there's a core during regression. Occasionally, we've introduced a bug
in Gluster and this tar can take up a lot of space. This has happened
recently with brick multiplex tests. The build-install tar takes up 25G,
[...truncated 6 lines...]
https://bugzilla.redhat.com/1536908 / build: gluster-block build as "fatal
error: api/glfs.h: No such file or directory"
https://bugzilla.redhat.com/1541261 / build: "glustereventsd-SuSE.in" is
missing in extras/init.d
https://bugzilla.redhat.com/1544851 / build: Redefin
