Consider variable assignments during command search (rehash of #20)#33
Consider variable assignments during command search (rehash of #20)#33
Conversation
|
I checked it locally, it does not break anything. Standing on 6156f8f modernish runs 116 tests and then is killed because of the issue #20 fixed. Standing on 84cb012 it runs 234 tests and then gets stuck in an endless loop in |
|
Hmm... are you on macOS? I wonder if I'm hitting something else weird, or if there's some other artifact of my local setup. Lem has been complaining about my numerics... I presume due to some local changes of mine. I'm happy to try folding in #21, but I'm starting to have trouble keeping track of all the moving parts! |
|
No, I'm on GNU/Linux. For me the modernish tests never successfully ran. Before #5 it would crash early and most of the tests didn't even get a chance to fail. Unfortunately the install script does not except the shell to just crash and does not report it as a problem. But if you run the tests directly, you should be able to observe how many tests actually run. The hack in #21 fixes the following tests:
Unfortunately without the fix these get stuck in an infinite loop, blocking the other tests from running. Sadly modernish does not have a way to skip tests, the best I can think of is asking for every other test suite to run: My pull requests should fix every other failure, expect for these four:
|
|
Hmm... interesting. In #34 I fix a bug with calls to I suspect there are some platform differences that are affecting Modernish's behavior, and some of those differences are leading to different tests being run... and so exposing different failures. I feel like Travis is going to be the best source of truth here, as annoying as that is. I semi-relatedly wonder about updating Modernish---my fork is more than 400 commits behind! |
The original fix in #20 looked good and tested well... but is breaking something in Modernish. Needs investigation.