Ticket #2117 (closed bug: fixed)

Opened 4 years ago

Last modified 3 years ago

t/pmc/nci.t fails when extra nci thunks are disabled

Reported by: dukeleto Owned by: jkeenan
Priority: normal Milestone:
Component: testing Version: 3.4.0
Severity: medium Keywords:
Cc: ligne Language:
Patch status: Platform: all

Description

Snippet:

$ prove -v t/library/nciutils.t 
t/library/nciutils.t .. 
1..13
ok 1 - load_bytecode
No NCI thunk available for signature `ptr (ptr, STRING)'
current instr.: 'parrot;NCI;Utils;nciwrap' pc 558 (runtime/parrot/library/NCI/Utils.pir:421)
called from Sub 'main' pc 87 (t/library/nciutils.t:49)
Dubious, test returned 1 (wstat 256, 0x100)
Failed 12/13 subtests 

Test Summary Report
-------------------
t/library/nciutils.t (Wstat: 256 Tests: 1 Failed: 0)
  Non-zero exit status: 1
  Parse errors: Bad plan.  You planned 13 tests but ran 1.
Files=1, Tests=1,  0 wallclock secs ( 0.02 usr  0.00 sys +  0.00 cusr  0.01 csys =  0.03 CPU)
Result: FAIL
(sarkomand)(~/git/parrot master )$ prove -v t/pmc/nci.t 
t/pmc/nci.t .. 
1..58
ok 1 - load library fails
ok 2 - dlfunc on undef
ok 3 - dlfunc function not found
ok 4 - dlfunc function is defined
not ok 5 - dlfunc function pointer

#   Failed test 'dlfunc function pointer'
#   at t/pmc/nci.t line 142.
# Exited with error code: 1
# Received:
# libnci_test was successfully loaded
# No NCI thunk available for signature `double (double)'
# current instr.: 'test' pc 19 (/media/ssd/git/parrot/t/pmc/nci_5.pir:13)
# 
# Expected:
# libnci_test was successfully loaded
# 1
# 1
# 1
# 
not ok 6 - nci_c - return a char in an INTEGER register

Change History

follow-up: ↓ 2   Changed 3 years ago by jkeenan

  • cc ligne added

dukeleto,

Is this the same problem as was described in TT #1979?

If so, can we close this ticket in favor of that one?

Thank you very much.

kid51

in reply to: ↑ 1   Changed 3 years ago by jkeenan

  • owner changed from plobsing to jkeenan
  • status changed from new to assigned

Replying to jkeenan:

dukeleto, Is this the same problem as was described in TT #1979? If so, can we close this ticket in favor of that one?

No response, but I'm going to close this ticket as I've applied a patch in TT #1979 and expect to close that one within two days.

Thank you very much.

kid51

  Changed 3 years ago by jkeenan

  • status changed from assigned to closed
  • resolution set to fixed
Note: See TracTickets for help on using tickets.