Skip to content

Conversation

@ltratt
Copy link
Contributor

@ltratt ltratt commented Apr 27, 2025

A recent yklua change means that we do now see this case in the wild.

@ptersilie ptersilie added this pull request to the merge queue Apr 28, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Apr 28, 2025
@ptersilie
Copy link
Contributor

ptersilie commented Apr 28, 2025

Looks like this also depends on ykjit/yklua#120? Now that that is merged I will try again. Or do we need to wait for ykjit/yk-benchmarks#21 first? Edit: Re-reading your offline comment I see you did say we needed to wait.

@ptersilie ptersilie added this pull request to the merge queue Apr 28, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Apr 28, 2025
A recent yklua change means that we do now see this case in the wild.
@ltratt
Copy link
Contributor Author

ltratt commented Apr 28, 2025

This bit hadn't occurred to me: this PR needs the new yklua for buildbot.sh. Fixed in the force push.

@ptersilie ptersilie added this pull request to the merge queue Apr 28, 2025
Merged via the queue into ykjit:master with commit 74f0d45 Apr 28, 2025
2 checks passed
@ltratt ltratt deleted the write_64 branch April 28, 2025 10:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants