Hi!
> I'm seeing several testcases with a TCONF result end up in the
> FAILCMDFILE log file. This makes triaging actual failures more
> difficult. Should TCONF results not be placed in FAILCMDFILE?
>
> As an example, adjtimer02 has a TCONF on recent upstream kernels.
That should have been fixed in:
commit 5f71cf97d5753c5506cdf8287812f28e2fffe4aa
Author: Xiaoguang Wang <wangxg.f...@cn.fujitsu.com>
Date: Tue Sep 23 15:59:43 2014 +0800
runltp, pan/ltp-pan.c: record test cases(not fully tested) into file
Since commit 6f6878f4e1406d79cae53564777c5e1245d2a124, we start to
differentiate TCONF from TFAIL, but in pan/ltp-pan.c, we still write
test cases that return TCONF into failcmdfile, this is wrong, fix this.
Since that commit, the TCONF testcases should be written into a separate file.
And that commit should be part of the latest release 20150119.
--
Cyril Hrubis
chru...@suse.cz
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
