From mboxrd@z Thu Jan  1 00:00:00 1970
From: eric <zren@suse.com>
Date: Sat, 10 Oct 2015 16:21:08 +0800
Subject: [Ocfs2-devel] OCFS2 test project current status ANNOUNCEMENT
In-Reply-To: <20151009051207.GA11859@laptop.ha>
References: <20151009051207.GA11859@laptop.ha>
Message-ID: <5618CA74.3090807@suse.com>
List-Id: <ocfs2-devel.oss.oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ocfs2-devel@oss.oracle.com

Hi,

The following patches are also conflicted and dropped:

[PATCH 19/59] verify_truncate: Lack of cluster index variable upon 
memcmp failure.
[PATCH 20/59] verify_truncate: Kill o_ret which is unused variable.
[PATCH 21/59] reserve_space: s/lld/PRId64/g to suppress compiler warning.
[PATCH 24/59] Inline-data: Remove unused label from inline-data.c.
[PATCH 53/59] discontig: fix remote mount

Sorry for late to report it!

Thanks,
Eric

On 10/09/15 13:12, Eric Ren wrote:
> Hi all,
>
> Now, we have already collected 55 patches into Mark's github repo[1]
> since Mar 16, 2012.
> [1] https://github.com/markfasheh/ocfs2-test
>
> Thanks a lot for their contributors:
>      Junxiao Bi: 23
>      Jeff Liu: 11
>      Tiger Yang: 12
>      Goldwynr: 5
>      Eric Ren: 3
>      Gang He: 1
>
> This patches below are dropped, need improved, or conflicted with
> previous ones:
>
> [PATCH 09/10] Trigger udev rescan to get volume label that mkfs made remotely.   -- relate to blkid.conf, needs improved
> [PATCH 42/59] mmap-test: fix segment fault  -- needs improved
> [PATCH 48/59] ocfs2-test: fix build error   -- conflicted, dropped
> [PATCH 45/59] flock-test: disable posix lock test   -- needs improved
> [PATCH 53/59] discontig: fix remote mount   -- conflicted, dropped
> [PATCH 32/59] xattr-test: fix single test failed    -- conflicted, dropped
> [PATCH 17/59] Splice: Fix conflict definition of splice(2) for splice tests.    -- conflicted, dropped
> [PATCH 13/59] aio-stress: fix aio-stress Makefile to link pthread explicitly.   -- conflicted, dropped
>
> There might be some incorrectness in my conclusion. For details, please
> refer to ocfs2-test-devel mailist!
>
> Test project is very important to ensure the quality of ocfs2. Welcome
> more contributions from you! Let's make it better;-)
>
> Thanks,
> Eric