Summary

message-digest's test failure on 2012-12-05

Metadata

Description

See http://tests.call-cc.org/master/linux/x86/2012/12/05/salmonella-report/test/message-digest.html

message-digest has not changed recently, and no egg it depends on has changed either.

The chicken used by salmonella on 2012-12-04 (all message-digest's tests pass) was 432aa3c. The chicken used on 2012-12-05, when message-digest's tests fail, was 19a6b5b.

Maybe chicken core's 52c69531d586a39c51f3acc636596c65e181622e is the cause?

Changes and comments

[2012-12-06 16:32:42 UTC] kon changed status from new to accepted

[2012-12-06 16:32:42 UTC] kon wrote:

Cannot reproduce w/ chicken core 52c69531d586a39c51f3acc636596c65e181622e but I will look deeper. (MacOS 10.8.2 w/ clang 4.1 & x86_64)

[2012-12-21 23:52:09 UTC] kon wrote:

(foreign-lambda* (... (unsigned-integer64 u64) ...)

 =>

C_u64 u64=(C_u64 )C_num_to_uint64(C_a1);

segmentation fault from the above C.

[2012-12-22 05:33:17 UTC] felix wrote:

Replying to kon: > (foreign-lambda* (... (unsigned-integer64 u64) ...) > > => > > C_u64 u64=(C_u64 )C_num_to_uint64(C_a1); > > segmentation fault from the above C.

This could only happen in case `C_al` does not hold a fixnum or flonum.

[2012-12-22 12:23:47 UTC] kon wrote:

Hum:(test-assert (message-digest-update-u64-be md #xAB54A98CEB1F0AD2))

[2012-12-23 17:58:08 UTC] sjamaan changed status from accepted to closed

[2012-12-23 17:58:08 UTC] sjamaan set resolution to fixed

[2012-12-23 17:58:08 UTC] sjamaan wrote:

Fixed by 42c869949f893baba40c9b0d5e4832eb2004b20e