FIX(develop): Update workflow caching to fix faiiling github action used before #778
GitHub Actions / E2E report yarn test-parallel-autocompound
succeeded
Jul 8, 2024 in 0s
E2E report yarn test-parallel-autocompound ✅
✅ e2eTests/reports/junit.xml-2304bb00-3d08-11ef-9ebf-4d2011b9454b.xml
23 tests were completed in 2040s with 23 passed, 0 failed and 0 skipped.
✅ test/parallel/xyk-pallet.API.accuracy.shared.pool.test.ts
Accuracy > Shared pool
✅ Each user who minted owns the same % of tokens - one user gets extra token
✅ Each user who minted onws the same % of tokens - two users gets the extra
✅ Each user who minted onws the same % of tokens - divisible by 3
✅ Each user who minted different % of tokens [50k,25k,5k]- get diff amounts
✅ Given 3 users that minted liquidity WHEN only one activated the rewards THEN all rewards belongs to him on this pool
✅ test/parallel/xyk-pallet.API.parachainStacking.activateRewards.test.ts
✅ Given a user with bonded but not activated liq tokens WHEN he tries to activate THEN the tokens are activated for rewards
✅ test/parallel/xyk-pallet.API.pool.deactivatedLiq.test.ts
✅ GIVEN a disabled pool the user can still interact with it: Burn, deactivate Liq
✅ test/parallel/xyk-pallet.API.pool.promoting.test.ts
✅ GIVEN a promoted pool WHEN more pools gets activated THEN shares are decreased and equally divided among all the activated pools
✅ test/parallel/xyk-pallet.API.pool.weightedPools.test.ts
✅ Check that we can get the list of promoted pools with proofOfStake.promotedPoolRewards data storage
✅ Validate that weight can be modified by using updatePoolPromotion AND only sudo can update weights
✅ Testing that the sum of the weights can be greater than 100
✅ GIVEN a pool WHEN it has configured with 0 THEN no new issuance will be reserved
✅ GIVEN a deactivated pool WHEN its configured with more weight, THEN rewards are now active, new users can get portion of those rewards AND issuance grows
✅ GIVEN an activated pool WHEN pool was deactivated THEN check that the user will still get some rewards from the curve, and storage is updated
✅ test/parallel/xyk-pallet.API.poolLiqidity.claimReward.test.ts
✅ Check that rewards are generated and can be claimed on each session, then burn all tokens and rewards wont be available
✅ Given a pool with 2 users with activated rewards WHEN more than one period last AND the user burn all liquidity THEN pool is destroyed but users can still claim pending rewards
✅ Given a pool with user with activated rewards WHEN it was deactivated AND activated again THEN the user can receive a reward in both a deactivated and activated pool
✅ test/parallel/xyk-pallet.API.poolLiqidity.mintLiqudity.test.ts
✅ Check that a user that mints on a promoted pool liquidity tokens are reserved
✅ Check that a user that mints on a non-promoted pool liquidity tokens are free
✅ Given 3 pool: token1-MGX, token2-MGX and token1-token2 WHEN token1-token2 is promoted THEN user can receive rewards from token1-token2 pool
✅ test/parallel/xyk-pallet.API.validateStatus.test.ts
Validate initial status
✅ User just minted on a promoted pool
✅ User just minted and rewards generated
✅ User just minted on a promoted pool and after rewards being generated mint some more
Loading