tests: add regen integration #40
Draft
Conversation
This file contains hidden or 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
conorsch
force-pushed
the
integration-tests-for-regen
branch
from
54bbeec to
c9d7ca8
Compare
conorsch
force-pushed
the
integration-tests-for-regen
branch
from
c9d7ca8 to
167e13e
Compare
conorsch
force-pushed
the
integration-tests-for-regen
branch
2 times, most recently
from
a0058dd to
ee37fdf
Compare
conorsch
force-pushed
the
integration-tests-for-regen
branch
from
ee37fdf to
cc62295
Compare
conorsch
force-pushed
the
integration-tests-for-regen
branch
2 times, most recently
from
a002231 to
71b418c
Compare
conorsch
force-pushed
the
integration-tests-for-regen
branch
from
71b418c to
4631037
Compare
Using a WIP utility lib by @cronokirby to handle the mechanics of local postgres over unix domain sockets. cleanup: more durable UDS impl Adding some ergonomic interfaces to picturesque to accommodate for UDS reqs like filepath length limit and absolute path requirement. Also includes a shoddy bash script for reference, that should be cleaned up prior to merge. test: actually check for blocks via pg Make some basic assertions about the pg db, same as we do for the sqlite3 db. logging: regen log every 100 -> 1000 blocks Unsure about the test names: does run order matter? is it ok to run all the archive tests, then all the regen tests?
Disable the "cargo check" step which will fail in `nix build` if there's a git dependency specified in the dev-deps. Had to update the crane lib in order to get the `doCheck = false` to take effect.
Height 4027443 -> 4836782, with corresponding checksum change.
conorsch
force-pushed
the
integration-tests-for-regen
branch
from
4631037 to
4151215
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.
No description provided.