All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [Ocfs2-test-devel] OCFS2 test report for linux vanilla kernel V4.7.0
Date: Mon, 22 Aug 2016 11:31:57 +0800	[thread overview]
Message-ID: <57BA722D.8010503@huawei.com> (raw)
In-Reply-To: <6705ddee-a26f-6f26-3943-5977f3584502@suse.com>

Hi Eric,
Thanks very much for your efforts.
I am interested in the failed inline testcase. Could you please send out
the testcase as well as detailed log? I'll do analysis when I have time.

Thanks,
Joseph

On 2016/8/22 10:42, Eric Ren wrote:
> Hi,
> 
> 
> The test report below is agaist vanilla kernel v4.7.0. Some highlights:
> 
> 1.  As you can see from logs attached, pcmk stack is used with "blocksize=4096, clustersize=32768";
> 
> 2. "inline" testcase on multiple nodes failed 3/3 times so far; seems to be a regression issue;
> 
> 3. Two cases are skipped:
>     o lvb_torture:  libo2dlm [1] doesn't correctly support LVB operations for fs/dlm;
> 
>       Actually, ocfs2 tools (mkfs and fsck) even don't need LVB operations, so it is not worth touching
> 
>      libo2dlm right now, I think;
> 
>     o filecheck: is not scheduled this time;
> 
> 4. "discontig test" is missing now:-/
> 
> 
> If anyone is intersted in  the detailed test logs, I can upload somewhere;-) will schedule test for V4.8.rc2 soon.
> 
> [1] https://oss.oracle.com/pipermail/ocfs2-tools-devel/2008-May/000761.html
> 
> Eric
> 
> run-dev-test
> 	*BUILD UNSTABLE*
> Project: 	run-dev-test
> Date of build: 	Sat, 20 Aug 2016 20:11:19 +0800
> Build duration: 	19 hr
> Build cause: 	Started by upstream project "zren-testing/ocfs2-dlm-dev" build number 16
> Build description: 	 linux vanilla kernel V4.7.0
> Built on: 	HA-232
> 
> 
>   Health Report
> 
> W 	Description 	Score
> 	Build stability: 2 out of the last 5 builds failed. 	60
> 	Test Result: 1 test failing out of a total of 29 tests. 	96
> 
> 
>   Tests Reports
> 
> <http://147.2.207.237:8080/job/zren-testing/job/run-dev-test/28//testReport>
> Package 	Failed 	Passed 	Skipped 	Total
> MultipleNodes 	1 	8 	1 	*10*
> MultipleNodes.inline.inline-test
> SingleNode 	0 	18 	1 	*19*
> 
> 
> 
> 
> _______________________________________________
> Ocfs2-test-devel mailing list
> Ocfs2-test-devel at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-test-devel
> 

  reply	other threads:[~2016-08-22  3:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <410483215.37.1471766765455.JavaMail.jenkins@bj-ha-1>
2016-08-22  2:42 ` [Ocfs2-devel] OCFS2 test report for linux vanilla kernel V4.7.0 Eric Ren
2016-08-22  3:31   ` Joseph Qi [this message]
2016-08-30  7:51     ` [Ocfs2-devel] [Ocfs2-test-devel] " Eric Ren
2016-08-22  8:21   ` [Ocfs2-devel] OCFS2 test report for linux vanilla kernel V4.8.0-rc2 Eric Ren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57BA722D.8010503@huawei.com \
    --to=joseph.qi@huawei.com \
    --cc=ocfs2-devel@oss.oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.