-
Notifications
You must be signed in to change notification settings - Fork 212
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
Flake: Getting Started (registry/yarn) #9325
Comments
I've been running into this lately too. Latest with registry/npm
|
closes: #9325 ## Description Auto-retry the flaky test. ### Security Considerations none ### Scaling Considerations none ### Documentation Considerations none ### Testing Considerations The problem it's fixing is intermittent. If it passes CI once, let's let it in and see over the following days whether CI failure is down. (And reopen the issue that landing this closes) ### Upgrade Considerations none
closes: #9325 ## Description Auto-retry the flaky test. ### Security Considerations none ### Scaling Considerations none ### Documentation Considerations none ### Testing Considerations The problem it's fixing is intermittent. If it passes CI once, let's let it in and see over the following days whether CI failure is down. (And reopen the issue that landing this closes) ### Upgrade Considerations none
#9550 set up a retry, but it doesn't always work. CI log
› gettingStartedWorkflowTest (packages/agoric-cli/tools/getting-started.js:124:7) ─ 1 test failed |
@frazarshad to get this working I suggest making a PR in which each of the Once we solve that, the "retry upon failure" mechanism should solve the flakiness. |
@michaelfig 's fix from 2 days ago (after your PR) does fix the leftover file problem. I'd approve changing it to #9740 because I think it's more clear and maintainable. I'm not certain that's the only problem with retries. I'd still like to see a run inducing (unnecessary) repetition to confirm. But I'm okay with closing this and reopening it if the flake is encountered again. |
closes: #9325, closes: #9710 ## Description This is a minor fix to make sure the `registry/yarn` getting-started CI test doesn't fail. It embraces the current situation that `agoric install $DISTTAG` is not currently usable within the default [Agoric/dapp-offer-up](https://github.com/Agoric/dapp-offer-up) because of the long list of `packageJson.resolutions` `dapp-offer-up` uses. Thus, `getting-started.js` has `AGORIC_INSTALL_DISTTAG` set to `false`. This ensures that `agoric install $DISTTAG` does not execute. It is replaced by simply `yarn install`.
re-opening due to recent failures |
Describe the bug
The Getting Started (registry/yarn) is flakey
To Reproduce
The test failed, as shown in
https://github.com/Agoric/agoric-sdk/actions/runs/8973265730/job/24643072843?pr=9283
hitting "Rerun failed tests" caused it to pass.
Other instances
Error: rpc error: code = Unknown desc = rpc error: code = Unknown desc = account sequence mismatch, expected 63, got 62: incorrect account sequence [agoric-labs/cosmos-sdk@v0.46.16-alpha.agoric.2.4/x/auth/ante/sigverify.go:269] With gas wanted: '18446744073709551615' and gas used: '38588' : unknown request
Expected behavior
Tests should not be flakey.
Platform Environment
Running in CI.
The text was updated successfully, but these errors were encountered: