Funds for sequencers (#873) #847
GitHub Actions / E2E report yarn test-sequencerCancellation
failed
Dec 19, 2024 in 0s
E2E report yarn test-sequencerCancellation ❌
❌ e2eTests/reports/junit.xml-36e40cf0-be24-11ef-8317-05d462a39de9.xml
6 tests were completed in 2358s with 5 passed, 1 failed and 0 skipped.
| Test suite | Passed | Failed | Skipped | Time |
|---|---|---|---|---|
| test/sequential/sequencerStaking.cancel.test.ts | 5✅ | 1❌ | 2358s |
❌ test/sequential/sequencerStaking.cancel.test.ts
❌ GIVEN a sequencer, WHEN <correctly> canceling an update THEN a % of the slash is given to it
Error: Expected: 800000000000000000
✅ 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
Annotations
Check failure on line 0 in e2eTests/reports/junit.xml-36e40cf0-be24-11ef-8317-05d462a39de9.xml
github-actions / E2E report yarn test-sequencerCancellation
test/sequential/sequencerStaking.cancel.test.ts ► GIVEN a sequencer, WHEN <correctly> canceling an update THEN a % of the slash is given to it
Failed test found in:
e2eTests/reports/junit.xml-36e40cf0-be24-11ef-8317-05d462a39de9.xml
Error:
Error: Expected: 800000000000000000
Raw output
Error: Expected: 800000000000000000
Actual: 797297840223577702
at /home/runner/_work/mangata-node/mangata-node/e2eTests/test/sequential/sequencerStaking.cancel.test.ts:101:36
at Generator.next (<anonymous>)
at fulfilled (/home/runner/_work/mangata-node/mangata-node/e2eTests/test/sequential/sequencerStaking.cancel.test.ts:8:58)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
Loading