Easy way to locate failed subtests about pjdfstest

[asomers]

Could you please rephrase the question? Use complete sentences so I can understand what you mean.

If it's prove's output you don't like, then that's an issue with prove, not pjdfstest. You can always try prove -v.

[ngie-eign]

@samuelsh: as @asomers noted, the best way to get more information is use prove -v instead of prove.

What the above output is stating is that there were 2 tests in rmdir/07.t that failed, and a test in rmdir/08.t that failed. You need to use prove -v to drill down further.

[samuelsh]

Thanks @asomers/ @ngie-eign ,
prove -v indeed helped, but still I'm not sure if there's easy way to locate failed subtests, i.e:

not ok 111 - tried 'chown pjdfstest_4fab06e83b05b8508c49ce1e12a0954c 65535 65535', expected 0, got EPERM
not ok 112 - tried '-u 65535 -g 65535 chmod pjdfstest_4fab06e83b05b8508c49ce1e12a0954c 02755', expected 0, got EPERM
not ok 113 - tried 'stat pjdfstest_4fab06e83b05b8508c49ce1e12a0954c mode', expected 02755, got 0755
not ok 114 - tried '-u 65535 -g 65535 chmod pjdfstest_4fab06e83b05b8508c49ce1e12a0954c 0755', expected 0, got EPERM
ok 115
not ok 116 - tried '-u 65535 -g 65534 chmod pjdfstest_4fab06e83b05b8508c49ce1e12a0954c 02755', expected 0, got EPERM
ok 117
ok 118
ok 119
Failed 17/119 subtests

Test Summary Report
-------------------
/home/vastdata/qa/pjdfstest/tests/chmod/00.t (Wstat: 0 Tests: 119 Failed: 17)
  Failed tests:  87-88, 91-92, 95-96, 99-100, 103-104, 107-108
                111-114, 116
Files=1, Tests=119, 12 wallclock secs ( 0.04 usr  0.01 sys +  0.23 cusr  0.35 csys =  0.63 CPU)
Result: FAIL

Now I would like to find subtest #87 in order to debug it explicitly vs my FileSystem.
How do I find that specific subtest in chmod/00.t file?

Thanks

[asomers]

You essentially have to count all of the expect statements, keeping in mind loops and macros.

[samuelsh]

Great, thanks a lot :)