oasisprotocol / oasisprotocol/oasis-core
e2e: Fix flaky runtime governance test
Open
Nobody has claimed this yet.
c:testing
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Fails:
- https://buildkite.com/oasisprotocol/oasis-core-ci/builds/16638#019d2486-4e81-459d-b58d-c91e38a09f4b
- https://buildkite.com/oasisprotocol/oasis-core-ci/builds/16638#019d26f8-ce01-461d-8961-c0dcef294781
Succeeds: https://buildkite.com/oasisprotocol/oasis-core-ci/builds/16638#019d2968-bb6e-4560-85b3-7e4be4ab9d1a
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the two failing and one succeeding Buildkite logs, then locate the e2e runtime governance test that they exercise. Reproduce the intermittent failure and identify the relevant test setup or timing; done means the test passes reliably rather than only in the successful run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100