test-mutual-redefinition fails on ABCL

Bug #1704255 reported by Robert P. Goldman on 2017-07-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Tested on both ABCL 1.4 and 1.5

Failure details:

; System definition file #P"/home/rpg/common-lisp/asdf/test/test-mutual-redefinition-1.asd" contains definition for syste\
m "test-mutual-redefinition-2". Please only define "test-mutual-redefinition-1" and secondary systems with a name starting \
with "test-mutual-redefinition-1/" (e.g. "test-mutual-redefinition-1/test") in that file.

; Loaded /home/rpg/common-lisp/asdf/test/test-mutual-redefinition-1.asd (0.031 seconds)

; Compilation unit finished
; Caught 1 WARNING condition

TEST ABORTED: The assertion WARNED-P failed.

Faré (fahree) wrote :

I can confirm that this test works on master (commit 5eca374) and fails on plan (as of 2017-07-20; commit non meaningful because of frequent rebasing) using ABCL 1.3.2.

After some investigation, it appears that the BAD-SYSTEM-NAME warning is not caught by our test's handler-bind, but by a handler installed by the WITH-COMPILATION-UNIT that is part of our PERFORM-PLAN method. This is probably a bug in ABCL.

NB: Adding #+abcl (setf jvm::*resignal-compiler-warnings* t) to the test makes it work.

I believe this is not a regression in ASDF itself, though it makes this test fail.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers