weirdness with compile-op and retry restart
dear devs, i have a system with a file that has a compilation error. i try to load it: (asdf:load-system :hu.dwim.web-server.application.test) it leads to an error with the following restart (notice its unusual wording, and that it's about the entire system, not just that one source file): 6: RETRY Retry completing compilation for #<HU.DWIM.TEST-SYSTEM "hu.dwim.web-server.application.test">. the rest FTR: 5: ACCEPT Continue, treating completing compilation for #<HU.DWIM.TEST-SYSTEM "hu.dwim.web-server.application.test"> as having been successful. 4: RETRY Retry ASDF operation. 3: CLEAR-CONFIGURATION-AND-RETRY Retry ASDF operation after resetting the configuration. if i touch the file and select the restart, then cl:compile-file doesn't get called and no compilation seems to happen. there used to be a restart to recompile the single source file that has failed. i'm on ASDF 3.2.1 and the very latest SBCL (i'm testing it for the current freeze) note: these systems have some customizations from hu.dwim.asdf, but not much changed there recently. is this something obvious that i'm failing to see, or should i dig deeper? what else would help? it's not a show-stopper for me, so feel free to ignore this. i'm writing this up more as offering help than asking for help. thanks for your time, -- • attila lendvai • PGP: 963F 5D5F 45C7 DFCD 0A39 -- “Understand and abide by the following self-evident principle, and you will be an anarchist: If there is something that would be wrong for you to do yourself, then you shouldn't ask anyone else to do it either.” — Larken Rose (1968–)
On Thu, Jul 20, 2017 at 7:59 PM, Attila Lendvai <attila@lendvai.name> wrote:
dear devs,
i have a system with a file that has a compilation error. i try to load it:
(asdf:load-system :hu.dwim.web-server.application.test)
it leads to an error with the following restart (notice its unusual wording, and that it's about the entire system, not just that one source file):
6: RETRY Retry completing compilation for #<HU.DWIM.TEST-SYSTEM "hu.dwim.web-server.application.test">.
the rest FTR:
5: ACCEPT Continue, treating completing compilation for #<HU.DWIM.TEST-SYSTEM "hu.dwim.web-server.application.test"> as having been successful.
4: RETRY Retry ASDF operation.
3: CLEAR-CONFIGURATION-AND-RETRY Retry ASDF operation after resetting the configuration.
if i touch the file and select the restart, then cl:compile-file doesn't get called and no compilation seems to happen. there used to be a restart to recompile the single source file that has failed.
i'm on ASDF 3.2.1 and the very latest SBCL (i'm testing it for the current freeze)
note: these systems have some customizations from hu.dwim.asdf, but not much changed there recently.
is this something obvious that i'm failing to see, or should i dig deeper? what else would help?
it's not a show-stopper for me, so feel free to ignore this. i'm writing this up more as offering help than asking for help.
thanks for your time,
Would you perchance be using deferred-warnings? If an unresolved deferred warning is detected at system check time, that could be the expected (though admittedly poorly worded) symptom. I have ideas on how deferred warnings and testing could be improved, by producing "all good" reports (or "something bad" report), but work on this feature has stopped long ago, considering the backlash when I tried to enable it by default. It would be a good idea to regularly try cl-test-grid with deferred warnings enabled, but at this point, I'm not going to pour much more work into ASDF unless I find funding of some sort. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Do not handicap your children by making their lives easy. — Robert Heinlein, "Time Enough For Love"
Would you perchance be using deferred-warnings?
yes. i asked myself: what exactly (asdf:enable-deferred-warnings-check) does? i couldn't answer. then i didn't find anything in the manual, and a brief inspection of the code also didn't satisfy my curiosity... so, i guess i'll just turn it off then... :) thanks for the info, -- • attila lendvai • PGP: 963F 5D5F 45C7 DFCD 0A39 -- “I'm not scared of the Maos and the Stalins and the Hitlers. I'm scared of the thousands of millions of people that hallucinate them to be "authority", and so do their bidding, and pay for their empires, and carry out their orders. I don't care if there's one looney with a stupid moustache. He's not a threat if the people do not believe in "authority".” — Larken Rose (1968–)
i asked myself: what exactly (asdf:enable-deferred-warnings-check) does? i couldn't answer. then i didn't find anything in the manual, and a brief inspection of the code also didn't satisfy my curiosity... so, i guess i'll just turn it off then... :)
It does save each file's deferrable warnings, to check them at the end of the system. So, for instance, if a file calls an undefined function, it will verify that the function has been defined by the time the system is done compiling, or not. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org I contend we are both atheists, I just believe in one fewer god than you do. When you understand why you dismiss all the other possible gods, you will understand why I dismiss yours. — Stephen F Roberts
participants (2)
-
Attila Lendvai -
Faré