[Gluster-devel] Test failed - due to out of memory on builder201?
dkhandel at redhat.com
Mon Jun 10 07:05:45 UTC 2019
I'm working on it. Looking at the logs and further health checkups, I did
not find any memory issue tracebacks on builder201.
On Mon, Jun 10, 2019 at 12:12 PM Yaniv Kaul <ykaul at redhat.com> wrote:
> From , we can see that non-root-unlink-stale-linkto.t failed on:
> useradd: /etc/passwd.30380: Cannot allocate memory
> useradd: cannot lock /etc/passwd; try again later.
> My patch only removed include statements that were not needed.
> I'm not sure how it can cause a memory issue.
> So it's either we have some regression, or the slaves do not have enough
> It was running on builder201.aws.gluster.org .
> Checking it, I see other jobs failing on the same issue. Perhaps it is
> the slave?
> Any ideas?
>  https://build.gluster.org/job/centos7-regression/6382/consoleFull
>  https://review.gluster.org/#/c/glusterfs/+/22844/
>  https://build.gluster.org/job/centos7-regression/6385/console
> BTW, we REALLY need to fix this message - it's clueless:
> E [MSGID: 106176] [glusterd-handshake.c:1038:__server_getspec]
> 0-management: Failed to mount the volume
> Community Meeting Calendar:
> APAC Schedule -
> Every 2nd and 4th Tuesday at 11:30 AM IST
> Bridge: https://bluejeans.com/836554017
> NA/EMEA Schedule -
> Every 1st and 3rd Tuesday at 01:00 PM EDT
> Bridge: https://bluejeans.com/486278655
> Gluster-devel mailing list
> Gluster-devel at gluster.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-devel