Closed okdas closed 2 weeks ago
The CI will now also run the e2e tests on devnet, which increases the time it takes to complete all CI checks.
You may need to run make trigger_ci
to submit an empty commit that'll trigger the tests.
GCP workloads (requires changing the namespace to 567)) Grafana network dashboard for devnet-issue-{issue-id}
The CI will now also run the e2e tests on devnet, which increases the time it takes to complete all CI checks.
You may need to run make trigger_ci
to submit an empty commit that'll trigger the tests.
GCP workloads (requires changing the namespace to 567)) Grafana network dashboard for devnet-issue-{issue-id}
The CI will now also run the e2e tests on devnet, which increases the time it takes to complete all CI checks.
You may need to run make trigger_ci
to submit an empty commit that'll trigger the tests.
GCP workloads (requires changing the namespace to 567)) Grafana network dashboard for devnet-issue-{issue-id}
@Olshansk @red-0ne E2E tests are green. I think this PR is ready for the first pass of reviews. Please let me know what you think and if I need to change anything.
I know the go tests are not fixed yet, and this is what I'm going to be focusing on next.
Thanks!
Seems like the only e2e test that fails is the same flaky TestFeatures/Session_Namespace/Supplier_completes_claim/proof_lifecycle_for_a_valid_session
.
Merging with one flaky test still failing.
Summary
Adds an ability to run many suppliers on one relayminer
Issue
528
Type of change
Select one or more:
Testing
Documentation changes (only if making doc changes)
make docusaurus_start
; only needed if you make doc changesLocal Testing (only if making code changes)
make go_develop_and_test
make test_e2e
PR Testing (only if making code changes)
devnet-test-e2e
label to the PR.make trigger_ci
if you want to re-trigger tests without any code changesSanity Checklist