Ticket #738 (closed defect: duplicate)

Opened 18 months ago

Last modified 9 months ago

callback tests failure on cygwin

Reported by: mario Owned by: mario
Priority: major Milestone:
Component: unknown Version: 4.7.x
Keywords: cygwin, callback, test Cc:

Description

$ make PLATFORM=cygwin PREFIX=/home/mario/local/chicken-core DEBUGBUILD=1 CHICKEN=./chicken-boot check

...

======================================== callback tests ...
../chicken callback-tests.scm -output-file a.c -verbose -include-path ..
gcc a.c -o a.o -c  -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H -DC_ENAB
LE_PTABLES -g -Wall -Wno-unused -I.. -I"/home/mario/local/chicken-core/include/c
hicken"
rm a.c
gcc a.o -o a.out -L.. -L"/home/mario/local/chicken-core/lib" -lchicken -lm
rm a.o
callbacks ...
hi!
callbacks ...
hi!
hi!
[panic] callback returned twice - execution terminated

callback-tests.scm:16: print
##sys#gc
g1112
callback-tests.scm:7: call/cc
callback-tests.scm:9: print
callback-tests.scm:19: command-line-arguments
callback-tests.scm:20: k1
callback-tests.scm:9: print     <--
double-return from callback failed as it should.
======================================== runtime tests ...
[panic] nursery is too small - try higher setting using the `-:s' option - execu
tion terminated

make[1]: *** [check] Error 1
make[1]: Leaving directory `/home/mario/src/chicken-core'
make: *** [check] Error 2

Change History

Changed 18 months ago by felix

  • owner set to felix
  • status changed from new to assigned

This is not a callback-test failure - it is either apply-test.scm or test-gc-hooks.scm which fails. Can you run these two tests by hand to see where it fails?

Changed 18 months ago by mario

Sorry for the late reply. Sure, I can do that in the next days.

Changed 13 months ago by felix

  • owner changed from felix to mario

Changed 9 months ago by felix

  • milestone 4.8.0 deleted

Changed 9 months ago by felix

  • status changed from assigned to closed
  • resolution set to duplicate

See #919, which has more information.

Note: See TracTickets for help on using tickets.