On Sep 28, 2016 11:37 PM, "Nir Soffer"
<nsoffer(a)redhat.com> wrote:
>
> On Wed, Sep 28, 2016 at 11:20 PM, Nir Soffer <nsoffer(a)redhat.com> wrote:
> > On Wed, Sep 28, 2016 at 10:31 PM, Barak Korren <bkorren(a)redhat.com>
> > wrote:
> >> The CI setup did not change recently.
> >
> > Great
> >
> >> All standard-CI jobs run inside mock (chroot) which is stored on top
> >> of a regular FS, so they should not be affected by the slave OS at all
> >> as far as FS settings go.
> >>
> >> But perhaps some slave-OS/mock-OS combination is acting strangely, so
> >> could you be more specific and point to particular job runs that fail?
> >
> > This jobs failed, but it was deleted (I get 404 now):
> >
http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/2530/
>
> Oops, wrong build.
>
> This is the failing build:
>
>
>
http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/1054/console
>
> And this is probably the reason - using a ram disk:
>
> 12:24:53 Building remotely on
ovirt-srv08.phx.ovirt.org (phx physical
> integ-tests ram_disk fc23) in workspace
> /home/jenkins/workspace/vdsm_master_check-patch-el7-x86_64
>
> We cannot run the storage tests using a ramdisk. We are creating
> (tiny) volumes and storage domains and doing copies, this code cannot
> work with ramdisk.
Will it work on zram?
What if we configure ram based iSCSI targets?
I don't know, but it is easy to test - it this works the tests will work:
dd if=/dev/zero of=file bs=512 count=1 oflag=direct