Skip to content

ci: Update git checkout to use specific SDK reference#105

Closed
galargh wants to merge 2 commits intomainfrom
galargh/last-known-good-ref
Closed

ci: Update git checkout to use specific SDK reference#105
galargh wants to merge 2 commits intomainfrom
galargh/last-known-good-ref

Conversation

@galargh
Copy link
Copy Markdown
Contributor

@galargh galargh commented May 3, 2026

This pins tests with synapse-sdk to FilOzone/synapse-sdk@8b85290 (last known working commit). Should we start testing with last release + master?

The next run with FilOzone/synapse-sdk@4d47a35 was already failing.

This gives us quite a large changeset to look through for the offender - https://github.com/FilOzone/synapse-sdk/compare/8b85290ce100b25a8e431f4c6b1ea0a1eda450ff..4d47a35fb396e99d89e640ab62bb21cd3a345f02 - but it would make sense if it was associated with FilOzone/synapse-sdk#698 since the error we're seeing now is:

Error: The contract function "getClientDataSets" reverted with the following reason:
    message execution failed (exit=[33], revert reason=[none], vm error=[message failed with backtrace:
    ...

https://filecoinproject.slack.com/archives/C06GD1SS56Y/p1745413864023989 also seems relevant. Disclaimer: I haven't yet looked at what to change to make the latest version of synapse SDK work here.

@FilOzzy FilOzzy added this to FOC May 3, 2026
@github-project-automation github-project-automation Bot moved this to 📌 Triage in FOC May 3, 2026
@galargh galargh force-pushed the galargh/last-known-good-ref branch from 1e7195e to 5a8c470 Compare May 3, 2026 08:52
@galargh galargh requested a review from BigLep May 3, 2026 10:13
@BigLep
Copy link
Copy Markdown
Contributor

BigLep commented May 3, 2026

@galargh : yeah, lets start using latest release and master. Thank you!

@BigLep BigLep moved this from 📌 Triage to ⌨️ In Progress in FOC May 3, 2026
@galargh
Copy link
Copy Markdown
Contributor Author

galargh commented May 4, 2026

I finally managed to fix the tests with master of synapse-sdk in #107

Let's get that in first and then we can setup latest release tests too. I'm going to close this one now since #107 is likely what we want instead.

@galargh galargh closed this May 4, 2026
@github-project-automation github-project-automation Bot moved this from ⌨️ In Progress to 🎉 Done in FOC May 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 🎉 Done

Development

Successfully merging this pull request may close these issues.

3 participants