Hopefully, my branch fixes test-force on Windows as well as on Linux. I wouldn't worry too much about test-force until the current development is complete. It's a release blocker, but not an otherwise worrisome deal since it's new tests for a recently discovered issue that we now understand how to improve upon without breaking other features, thanks to Daniel Kochmanski's patient work.
-#f On Wed, Sep 14, 2016, 12:50 Robert Goldman <rpgold...@sift.net> wrote: > On 9/14/16 Sep 14 -9:07 AM, Faré wrote: > > Sorry, it's my bad for checking in bad code in master (that I fixed > > later on, but too late). > > > > What's failing at head on which implementations, already? Can you > > publish logs? > > Allegro (all flavors), CCL, SBCL, and ECL-bytecodes (note that I don't > have the toolchain to run ECL non-bytecodes on windows) all fail > test-force, and all fail in the same way: > > SBCL: > > Check that require-system of touched .asd will reload the asdf. > (That's what it does now, but if it could be fixed that'd be nice.) > While evaluating the form starting at line 96, column 0 > of #P"F:/asdf/test/test-force.script": > TEST ABORTED: These two expressions fail comparison with EQUAL: > (ASYMVAL :*TIMES-LOADED* :TEST-ASDF-SYSTEM) evaluates to 1 > 2 evaluates to 2 > > CCL: > Check that require-system of touched .asd will reload the asdf. > (That's what it does now, but if it could be fixed that'd be nice.) > TEST ABORTED: These two expressions fail comparison with EQUAL: > (ASYMVAL :*TIMES-LOADED* :TEST-ASDF-SYSTEM) evaluates to 1 > 2 evaluates to 2 > > > ECL and Allegro same. Backtraces useless because the action seems to be > in either how REQUIRE-SYSTEM is detecting the need to reload or in how > TOUCH-FILE and GET-FILE-STAMP are working on Windows, and those aren't > on the stack when the assertion fails. > > Cheers, > r > > >
