fix: Increase instance class for stash service from B2 to B8 for be…
#368
GitHub Actions / E2E report yarn test-sequencerCancellation
succeeded
Jan 31, 2025 in 0s
6 passed, 0 failed and 0 skipped
✅ e2eTests/reports/junit.xml-7f2c6720-dff6-11ef-b7e4-df268dcb3c2f.xml
6 tests were completed in 2352s with 6 passed, 0 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| test/sequential/sequencerStaking.cancel.test.ts | 6✅ | 2352s |
✅ test/sequential/sequencerStaking.cancel.test.ts
✅ GIVEN a sequencer, WHEN <correctly> canceling an update THEN a % of the slash is given to it
✅ GIVEN a sequencer, WHEN <in-correctly> canceling an update THEN my slash is burned
✅ GIVEN a sequencer, WHEN <no> canceling an update THEN no slash is applied
✅ GIVEN a sequencer, WHEN <in-correctly> canceling an update AND some pending updates/cancels, THEN it can be still slashed and kicked, cancels & updates will be executed.
✅ GIVEN a sequencer, WHEN <in-correctly> canceling an update AND cancelator provides staking THEN cancelator will be slashed but he will stay in activeSequncer pool
✅ GIVEN a sequencer, WHEN <in-correctly> canceling an update AND some pending updates/cancels AND users provide staking THEN users have read/cancel rights
Loading