Skip to content

Conversation

tcharding
Copy link
Member

On top of #818, this was quicker than writing an issue. Maybe it will just work.

@apoelstra
Copy link
Member

#818 was merged -- you can rebase and undraft this. Looks like it worked, nice!

Un-comment the wasm job now that WASM builds again - maybe.
@tcharding tcharding force-pushed the 07-04-ci-enablem-wasm branch from 1e4c21e to 1800e73 Compare July 4, 2025 23:55
@tcharding tcharding marked this pull request as ready for review July 4, 2025 23:55
@tcharding
Copy link
Member Author

That was easy. Props to @andunieee for bringing the issue to our attention.

Copy link
Member

@apoelstra apoelstra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK 1800e73; successfully ran local tests

@apoelstra apoelstra merged commit 1ed5ef3 into rust-bitcoin:master Jul 5, 2025
13 checks passed
@apoelstra
Copy link
Member

Fucking Github. This did not "pass CI". Github silently disabled all of our checks because the spacing in this PR was wrong.

#840.

@tcharding
Copy link
Member Author

ouch

apoelstra added a commit that referenced this pull request Aug 30, 2025
471cd63 ci: delete broken WASM job (Andrew Poelstra)
0d0263e secp-sys: update raw pointer deref syntax in fuzz version of the crate (Andrew Poelstra)
d477198 ci: remove now-removed 'hashes' feature from tests (Andrew Poelstra)

Pull request description:

  The incorrectly-indented wasm test from #819 is causing Github to silently disable all of our checks. If you click through to the "Actions" tab of this repo you can see it failing (with a "syntax error on line 1" nonsense error). For example https://github.com/apoelstra/rust-secp256k1/actions/runs/17178718613/workflow
  
  Delete the test, and also fix everything else that broke in the meantime.


ACKs for top commit:
  tcharding:
    ACK 471cd63


Tree-SHA512: b52f86a203cb08f66ecbe2afc6e85d973193373da9d5a8bc7e10ca4f9b0991a69cf30e851b439ad6c463b468d10a35c87540fabc6b9ed877fadd82df74221fe8
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.

2 participants