Please file a bug against project-infrastructure.
On Tue, Jul 12, 2016 at 6:50 PM, Raghavendra Talur
wrote:
> Nigel/Misc,
>
> Could you please look into this?
> slave29 does not seem to have a xfs formatted backend for tests.
>
> Thanks,
> Raghavendra Talur
>
> On Tue, Jul 12, 2016 at 6:41 PM, A
Nigel/Misc,
Could you please look into this?
slave29 does not seem to have a xfs formatted backend for tests.
Thanks,
Raghavendra Talur
On Tue, Jul 12, 2016 at 6:41 PM, Avra Sengupta wrote:
> Atin,
>
> I am not sure about the docker containers, but both the failures you
> mentioned are in slav
Atin,
I am not sure about the docker containers, but both the failures you
mentioned are in slave29, which as Talur explained is missing the
appropriate backend filesystem. Owing to this, op-errno.t is just the
tip of the iceberg, and every other test that uses lvm will fail in this
particula
I checked the machine.
Here is the df -hT output
[jenkins@slave29 ~]$ cat /etc/fstab
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/xvda1 / ext3
defaults
https://build.gluster.org/job/rackspace-regression-2GB-triggered/22156/consoleFull
- another failure
On Tue, Jul 12, 2016 at 4:42 PM, Atin Mukherjee wrote:
>
>
> On Tue, Jul 12, 2016 at 4:36 PM, Avra Sengupta
> wrote:
>
>> Hi Atin,
>>
>> Please check the testcase result in the console. It clear
On Tue, Jul 12, 2016 at 4:36 PM, Avra Sengupta wrote:
> Hi Atin,
>
> Please check the testcase result in the console. It clearly states the
> reason of the failure. A quick search of 30815, as shown in the testcase
> shows that the error that is generated is a thinp issue, and we can see
> falloc
Hi Atin,
Please check the testcase result in the console. It clearly states the
reason of the failure. A quick search of 30815, as shown in the testcase
shows that the error that is generated is a thinp issue, and we can see
fallocate failing and lvm not properly being setup in the environment
