io: merge eval_ast into eval, add DEBUG-EVAL #699
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@asarhaddon @dubek The update to the version of io in the Dockerfile appears to have completed self-hosted tests successfully: https://github.com/kanaka/mal/actions/runs/11327008274/job/31497159120 The io repo hasn't changed from the time when @dubek did the update to when the pushed image would have been pushed (although it would have been a different instance of the build but of the same sources). Maybe it's some sort of temperamental GC related issue? When I build and run locally with it works. |
|
Sorry, I have no clue and miss motivation to investigate this issue. |
asarhaddon
force-pushed
the
merge-eval
branch
from
de50bf7
to
3b16c39
Compare
asarhaddon
force-pushed
the
merge-eval
branch
from
965a518
to
46adc4b
Compare
|
@asarhaddon sounds like a reasonable plan. I've added io to #662 |
29 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The self-hosted tests fail, for apparently unrelated reasons (the first readline fails in step0). Were they failing before?