On Mon, Oct 27, 2014 at 10:00:33PM +0530, Kaushal M wrote:
> Can you run the test from within the GlusterFS src directory using
> './run-tests.sh '? The run-tests.sh script now does some
> environmental setup before running the test.
I found the problem: $testcnt is left padded with white spaces
o
IIRC, the regression test suite was changed a little recently, which
leads to tests failing to run when called directly using prove.
Can you run the test from within the GlusterFS src directory using
'./run-tests.sh '? The run-tests.sh script now does some
environmental setup before running the te
On Mon, Oct 27, 2014 at 07:31:22PM +0530, Venky Shankar wrote:
> ?possible to get verbose output? prove -v ?
It does not help much:
(...)
=
TEST 39 (line 87): rm -rf ./tests/encryption/frag
ok 39
RESULT 39: 0
All 39 subtests passed
[16:25:35]
Test Summary Report
The 'include.rc' file, which should be sourced at the top of every
test, generates the TAP plan and TAP output.
To generate the TAP plan, include.rc counts the number (N) of
TEST,EXPECT etc and prints a line '1..N' which is the TAP plan. No
plan in TAP output means that this line isn't being genera
​possible to get verbose output? prove -v ?
Venky
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
No anwser, anyone?
On Thu, Oct 23, 2014 at 12:58:37PM +, Emmanuel Dreyfus wrote:
> Hi
>
> When running tests, even if they all succeed, I have this:
> Test Summary Report
> ---
> ./tests/basic/bd.t (Wstat: 0 Tests: 0 Failed: 0)
> Parse errors: No plan found in TAP output
> F
Hi
When running tests, even if they all succeed, I have this:
Test Summary Report
---
./tests/basic/bd.t (Wstat: 0 Tests: 0 Failed: 0)
Parse errors: No plan found in TAP output
Files=1, Tests=0, 2 wallclock secs ( 0.06 usr 0.09 sys + 0.10 cusr 0.94
csys = 1.19 CPU)
Result:
