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

Test production gateways #104

Closed
4 tasks done
Tracked by #120
laurentsenta opened this issue Jun 30, 2023 · 5 comments
Closed
4 tasks done
Tracked by #120

Test production gateways #104

laurentsenta opened this issue Jun 30, 2023 · 5 comments
Assignees

Comments

@laurentsenta
Copy link
Contributor

laurentsenta commented Jun 30, 2023

Contributes to #8

  • pick one or more gateways (https://ipfs.github.io/public-gateway-checker/ - ipfs.runfission.com might be a good candidate)
  • automatically pin our fixtures.car file (using web3.storage) on merge to main
  • configure the test suite to run tests there (probably not the one related to dnslink and ipns)
  • generate dashboards
@laurentsenta laurentsenta self-assigned this Jun 30, 2023
This was referenced Jun 30, 2023
@laurentsenta
Copy link
Contributor Author

laurentsenta commented Jul 5, 2023

The follow-up task would be to create a dashboard when we run these tests:

Phase 1:

  1. run the tests for every gateway we care about
  2. aggregate test results by specs involved (gateway-car, gateway-trustless, etc).
    ideally we end up with a matrix of (gateway x specs x PASS/FAIL)
  3. generate an HTML, similar to https://ipfs.github.io/public-gateway-checker/

Phase 2:

add support for dnslink and ipns record, these will require sync'ing with the gateway providers

@BigLep
Copy link

BigLep commented Jul 5, 2023

@laurentsenta : cool. I can see how this can be done for gateways with a public URL like the ones in https://github.com/ipfs/public-gateway-checker . How would we do this against various gateway implementations (Boxo, Kubo, bifrost-gateway)? Would we be needing to recreate their setups in the gateway-conformance pipeline so we can get an instance of them running?

@laurentsenta
Copy link
Contributor Author

@BigLep

Would we be needing to recreate their setups in the gateway-conformance pipeline so we can get an instance of them running?

That would be a "worst case" scenario: since all the projects you listed have gateway conformance in their CI, we can definitely find a collaborative approach where we reuse their workflows or the artifacts they produced.

@laurentsenta
Copy link
Contributor Author

@lidel @BigLep
fwiw I drafted a solution in #116

example dashboard output: https://github.com/singulargarden/gateway-conformance/actions/runs/5681118160/attempts/1#summary-15396709726

@laurentsenta
Copy link
Contributor Author

Closing this, it's running. Follow-up / related tasks live in #120

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

No branches or pull requests

2 participants