[4.0] run integration tests in CI with libtester from leap-dev.deb #172
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
larryk85
approved these changes
May 4, 2023
|
Hey @spoonincode, would you mind making this same PR for main too? |
dimas1185
approved these changes
May 17, 2023
spoonincode
changed the title
This was referenced May 24, 2023
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.
Runs the integration tests in CI via a libtester installed by leap-dev.deb
I elected to just place the target leap-dev.deb version straight in the workflow vs a json indirection as used in contracts CI. And I also didn't make it configurable like contract CI. I guess consider this an MVP of sorts 😉
Resolves #168
Integration tests can be seen successfully run here on this line,
https://github.com/AntelopeIO/cdt/actions/runs/4877470506/jobs/8702137641?pr=172#step:6:23075