-
Notifications
You must be signed in to change notification settings - Fork 831
Extract travis testing into locally-runnable script #227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extract travis testing into locally-runnable script #227
Conversation
7fca28b
to
6f06a32
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to still be testing things, may be worth double-checking that failures result in travis failures.
The script has a Checked assumption that if script fails travis also fails: https://docs.travis-ci.com/user/job-lifecycle/#customizing-the-build-phase |
In some of the rust-bitcoin projects I have an untracked script that
If you add 1.5 that runs |
I didn't know about |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, ran it locally, works with my setup.
6f06a32
to
50fef2d
Compare
Rebased, please reACK: @sgeisler @TheBlueMatt |
Slightly off topic: is there a tool/git command that you can use to compare two change sets (see if it was just a rebase or which changes happened)? |
They thought of everything: https://git-scm.com/docs/git-range-diff |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utack
Add psbt preimage satisfaction logic
This allows people to locally run
contrib/test.sh
on their fast hardware before Travis gets to it.