Simple fuzz test for v0.14 <-> v0.15 interoperability #270
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
BREAKING CHANGE: Updating the Go version to 1.23
ci: uci/update-go
* refactor: keep same api for SplitFirst/SplitLast Not worth breaking this function, and it saves us some pain with updating downstream deps * add defensive copy
…ent (#272) * Backwards compatible Encapsulate/Decapsulate/Join * remove EncapsulateC * feat: Add Multiaddr.AppendComponent * remove .Empty (#274) prefer the simpler `len` check for Multiaddr and `== nil` for `*Component`. * export AsMultiaddrer interface * rename AsMultiaddr to Multiaddr Export Multiaddrer interface
git-subtree-dir: compattest/internal/prev git-subtree-split: 37363a0
MarcoPolo
force-pushed
the
marco/backwards-compat
branch
from
24b8ec0 to
bf94599
Compare
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.
I wrote this small test as a sanity check to make sure v0.15 did not accidentally break anything in a subtle ways. It pulls in v0.14 into the compattest/internal/prev folder and fuzzes against it.
We probably don't need to merge this. Running this locally was enough to increase my confidence that we aren't accidentally breaking something.
Note that we also have transport interop tests in go-libp2p as well that would fail if v0.15 were not compatible. The goal with the fuzz tests is to hopefully check edge cases as well.