Skip to content
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

Submodule secp256k1 instead of copying files #123

Merged
merged 3 commits into from
Mar 21, 2018

Conversation

mecampbellsoup
Copy link
Contributor

@mecampbellsoup
Copy link
Contributor Author

@Christewart how to trigger the build checks e.g. Coveralls?

@mecampbellsoup
Copy link
Contributor Author

mecampbellsoup commented Mar 21, 2018

[info] ! EscrowWithTimeoutScriptSigSpec.serialization symmetry: Exception raised on property evaluation.
[info] > Exception: java.lang.UnsatisfiedLinkError: org.bitcoin.NativeSecp256k1.secp256k1_ec_pubkey_decompress(Ljava/nio/ByteBuffer;JI)[[B

[info] ! P2PKScriptPubKeySpec.Serialization symmetry: Exception raised on property evaluation.
[info] > Exception: java.lang.UnsatisfiedLinkError: org.bitcoin.NativeSecp256k1.secp256k1_ec_pubkey_decompress(Ljava/nio/ByteBuffer;JI)[[B

[info] ! ECDigitalSignatureSpec.must create and verify a digital signature: Exception raised on property evaluation.
[info] > ARG_0: DoubleSha256DigestImpl(10e5a184d30854be4d8dd3a246dc78c622746bd55d3cacda4c6f97ff7b05f502)
[info] > ARG_1: ECPrivateKey(2e59c250b84a4419a62273a00c6eada91f7dcdd245d16135b685946f5a87dbff,true)
[info] > Exception: java.lang.UnsatisfiedLinkError: org.bitcoin.NativeSecp256k1.secp256k1_ec_pubkey_decompress(Ljava/nio/ByteBuffer;JI)[[B

Seeing a lot of test failures like ☝️ which leads me to think the secp256k1 submodule isn't... discoverable/linked?

@Christewart
Copy link
Contributor

I'm not sure why travis isn't being kicked off. But yes it looks like the secp256k1 module isn't being found. Does the relative path change when incorporating a submodule? I.e. is it not bitcoin-s-core/secp256k1 anymore?

@mecampbellsoup mecampbellsoup force-pushed the submodule-secp256k1 branch 2 times, most recently from 9beb064 to 9f91b3b Compare March 21, 2018 20:51
@coveralls
Copy link

Coverage Status

Coverage increased (+0.02%) to 90.29% when pulling 9f91b3b on mecampbellsoup:submodule-secp256k1 into 51d0ec7 on bitcoin-s:master.

@mecampbellsoup
Copy link
Contributor Author

@Christewart hey, we're green again! This is a no-op change so hopefully you're OK merging 😄

@Christewart Christewart merged commit 05cb546 into bitcoin-s:master Mar 21, 2018
@Christewart
Copy link
Contributor

Merged. Congrats @mecampbellsoup . We will need to update this whenever bitcoin-core/secp256k1#508 gets merged

@mecampbellsoup mecampbellsoup deleted the submodule-secp256k1 branch March 22, 2018 14:57
Christewart added a commit that referenced this pull request May 1, 2021
Submodule secp256k1 instead of copying files
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