Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

t/10-run.t fails on newer FreeBSD systems #4

Open
eserte opened this issue Mar 5, 2018 · 2 comments
Open

t/10-run.t fails on newer FreeBSD systems #4

eserte opened this issue Mar 5, 2018 · 2 comments

Comments

@eserte
Copy link

eserte commented Mar 5, 2018

On my freebsd 11+12 smokers the test suite fails:

    #   Failed test 'Commit the changes.'
    #   at t/10-run.t line 100.
    # died: fatal: empty string is not a valid pathspec. please use . instead if you meant to match all paths at t/10-run.t line 94.
    
    #   Failed test 'The commit failed with an error message.'
    #   at t/10-run.t line 113.
    #                   undef
    #     doesn't match '(?^:x\ Test\ plugin\ \-\ custom\ return\ codes\.)'
Use of uninitialized value $exit_status in numeric ne (!=) at t/10-run.t line 122.
    
    #   Failed test 'Retrieve the commit message.'
    #   at t/10-run.t line 134.
    # died: fatal: your current branch 'master' does not have any commits yet at t/10-run.t line 132.
    
    #   Failed test 'The pre-commit errors are embedded in the commit message.'
    #   at t/10-run.t line 138.
    #                   undef
    #     doesn't match '(?^:x\ Test\ plugin\ \-\ custom\ return\ codes\.)'
    # Looks like you failed 4 tests of 6.

#   Failed test 'Commit without --no-verify.'
#   at t/10-run.t line 145.
# Looks like you failed 1 test of 2.
t/10-run.t .......... 
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/2 subtests 

git version installed here: 2.16.1 or 2.16.2, which is newer than on my other smoker systems.

@eserte
Copy link
Author

eserte commented Nov 16, 2018

Fails also on Ubuntu 18.04 (git 2.17.1).

@eserte
Copy link
Author

eserte commented Mar 15, 2020

Yes, it's git. There are no pass reports anymore since git 2.16.1. Statistical analysis (theta=-1 means "bad"):

****************************************************************
Regression 'qr:# git version (\S+)'
****************************************************************
Name                   Theta          StdErr     T-stat
[0='const']           1.0000          0.0104      96.31
[1='eq_1.7.1']       -0.0000          0.0215      -0.00
[2='eq_1.8.3.1']              0.0000          0.0235       0.00
[3='eq_2.1.4']       -0.0000          0.0168      -0.00
[4='eq_2.11.0']      -0.0465          0.0165      -2.81
[5='eq_2.15.1']      -0.0000          0.0434      -0.00
[6='eq_2.16.1']      -1.0000          0.0360     -27.80
[7='eq_2.16.2']      -1.0000          0.0360     -27.80
[8='eq_2.17.1']      -1.0000          0.0275     -36.40
[9='eq_2.17.2']      -1.0000          0.0265     -37.78
[10='eq_2.18.2']             -1.0000          0.0850     -11.77
[11='eq_2.19.1']             -1.0000          0.0335     -29.82
[12='eq_2.19.2']             -1.0000          0.0850     -11.77
[13='eq_2.20.1']             -1.0000          0.0300     -33.36
[14='eq_2.21.0']             -1.0000          0.0235     -42.54
[15='eq_2.24.1']             -1.0000          0.0605     -16.52
[16='eq_2.25.0']             -1.0000          0.0335     -29.82
[17='eq_2.7.4']       0.0000          0.0224       0.00

R^2= 0.967, N= 286, K= 18

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant