Skip to content

Conversation

@berendkleinhaneveld
Copy link
Collaborator

Most of the benchmark will fail based on the current status on the master branch because of a recursion error, but that should not withhold running the benchmarks.

@berendkleinhaneveld
Copy link
Collaborator Author

berendkleinhaneveld commented Nov 19, 2025

It skips the run because there is no baseline yet. We could merge it and see what happens?

Edit: I've just changed it to at least run the benchmarks, even if it can't compare it to anything yet.

@Korijn Korijn merged commit 4b8ece5 into master Nov 19, 2025
9 of 10 checks passed
@Korijn Korijn deleted the benchmarks branch November 19, 2025 10:44
@berendkleinhaneveld
Copy link
Collaborator Author

I'm going to add to the benchmark workflow to always store the result anyways, whether it succeeded or failed.

berendkleinhaneveld added a commit that referenced this pull request Nov 19, 2025
* Iterative Levenshtein distance (can handle larger diffs now) (Iterative Levenshtein distance #21)
* Add benchmark and workflow (Add benchmark and workflow (based on observ's) #22)
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