[Gluster-devel] On some (spurious) test failures

[Ravishankar N]

On 27/10/20 9:13 pm, Dmitry Antipov wrote:
> I've never had the following tests succeeded, neither via
> 'run-tests.sh' nor running manually with 'prove -vf':
>
> tests/basic/afr/entry-self-heal.t (Wstat: 0 Tests: 252 Failed: 2)
>   Failed tests:  104, 208
>
> tests/basic/afr/entry-self-heal-anon-dir-off.t (Wstat: 0 Tests: 261 
> Failed: 2)
>   Failed tests:  105, 209
>
> tests/basic/afr/granular-esh/granular-esh.t (Wstat: 0 Tests: 82 
> Failed: 1)
>   Failed test:  46
>
> tests/basic/afr/self-heal.t (Wstat: 0 Tests: 145 Failed: 1)
>   Failed test:  124
>
> tests/basic/ec/ec-quorum-count.t (Wstat: 0 Tests: 142 Failed: 2)
>   Failed tests:  111, 139
>
> tests/basic/ctime/ctime-heal-symlinks.t (Wstat: 0 Tests: 31 Failed: 2)
>   Failed tests:  12, 26
>
> tests/basic/ctime/ctime-utimesat.t (Wstat: 0 Tests: 14 Failed: 1)
>   Failed test:  14
>
> tests/bugs/heal-symlinks.t (Wstat: 0 Tests: 31 Failed: 2)
>   Failed tests:  12, 26
>
> Does anyone has seen something similar? Any ideas on what may be wrong 
> here?

Which branch are you running them on? They pass for me locally on the 
latest devel branch, as do the upstream regression runs when you submit 
a patch.

If a .t is always failing in the same line in your setup, you could put 
an 'exit' after the line in the test so that you have a live state for 
debugging.

Thanks,
Ravi
>
> Thanks,
> Dmitry
>
> _______________________________________________
>
> Community Meeting Calendar:
>
> Schedule -
> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
> Bridge: https://bluejeans.com/441850968
>
>
>
>
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-devel
>