[Koha-bugs] [Bug 35461] Renew All 66 SIP server response messages produce HASH content in replies

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35461

--- Comment #9 from David Nind <david at davidnind.com> ---
I hope I haven't confused things....

With the unit tests patch, the tests fail (as expected):

prove t/db_dependent/SIP/Message.t
t/db_dependent/SIP/Message.t .. 5/18 
    #   Failed test at t/db_dependent/SIP/Message.t line 1399.
    #          got: '61'
    #     expected: 'String 'HASH(' not found in reponse ( Bug 35461 )'
    # Looks like you failed 1 test of 3.

#   Failed test 'Test renew desensitize'
#   at t/db_dependent/SIP/Message.t line 106.
t/db_dependent/SIP/Message.t .. 18/18 # Looks like you failed 1 test of 18.
t/db_dependent/SIP/Message.t .. Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/18 subtests 

Test Summary Report
-------------------
t/db_dependent/SIP/Message.t (Wstat: 256 Tests: 18 Failed: 1)
  Failed test:  6
  Non-zero exit status: 1
Files=1, Tests=18,  7 wallclock secs ( 0.04 usr  0.00 sys +  5.08 cusr  1.11
csys =  6.23 CPU)
Result: FAIL


After applying the main patch, I'm still getting test failures:


prove t/db_dependent/SIP/Message.t
t/db_dependent/SIP/Message.t .. 5/18 
    #   Failed test at t/db_dependent/SIP/Message.t line 1399.
    #          got: '-2'
    #     expected: 'String 'HASH(' not found in reponse ( Bug 35461 )'
    # Looks like you failed 1 test of 3.

#   Failed test 'Test renew desensitize'
#   at t/db_dependent/SIP/Message.t line 106.
t/db_dependent/SIP/Message.t .. 17/18 # Looks like you failed 1 test of 18.
t/db_dependent/SIP/Message.t .. Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/18 subtests 

Test Summary Report
-------------------
t/db_dependent/SIP/Message.t (Wstat: 256 Tests: 18 Failed: 1)
  Failed test:  6
  Non-zero exit status: 1
Files=1, Tests=18,  8 wallclock secs ( 0.03 usr  0.01 sys +  5.44 cusr  1.06
csys =  6.54 CPU)
Result: FAIL

-- 
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.