Test benchmarks #79
Open
Test benchmarks #79
+1,479
−420
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…embed it in its README paritytech#6333 (paritytech#7093) Use docify export for parachain template hardcoded configuration and embed it in its README paritytech#6333 Docify currently has a limitation of not being able to embed a variable/const in its code, without embedding it's definition, even if do something in a string like "this is a sample string ${sample_variable}" It will embed the entire string "this is a sample string ${sample_variable}" without replacing the value of sample_variable from the code Hence, the goal was just to make it obvious in the README where the PARACHAIN_ID value is coming from, so a note has been added at the start for the same, so whenever somebody is running these commands, they will be aware about the value and replace accordingly. To make it simpler, we added a rust ignore block so the user can just look it up in the readme itself and does not have to scan through the runtime directory for the value. --------- Co-authored-by: Iulian Barbu <[email protected]>
…aritytech#7253) Saw this test flake a few times, last time [here](https://github.com/paritytech/polkadot-sdk/actions/runs/12834432188/job/35791830215). We first fetch all processes in the test, then query `/proc/<pid>/stat` for every one of them. When the file was not found, we would error. Now we tolerate not finding this file. Ran 200 times locally without error, before would fail a few times, probably depending on process fluctuation (which I expect to be high on CI runners).
Log error instead of failing with an error when block processing fails --------- Co-authored-by: command-bot <>
…ghts. (paritytech#7098) This PR addresses a few minor issues found while working on the polkadot-fellows PR [https://github.com/polkadot-fellows/runtimes/pull/522](https://github.com/polkadot-fellows/runtimes/pull/522): - Incorrect generic type for `InboundLaneData` in `check_message_lane_weights`. - Renaming leftovers: `assigner_on_demand` -> `on_demand`.
Part of paritytech#6504 ### Added modules - `utility`: Traits not tied to any direct operation in the runtime. polkadot address: 14SRqZTC1d8rfxL8W1tBTnfUBPU23ACFVPzp61FyGf4ftUFg --------- Co-authored-by: Giuseppe Re <[email protected]>
…h#7263) ## Description The `frame-benchmarking-cli` crate has not been buildable without the `rocksdb` feature since version 1.17.0. **Error:** ```rust self.database()?.unwrap_or(Database::RocksDb), ^^^^^^^ variant or associated item not found in `Database` ``` This issue is also related to the `rocksdb` feature bleeding (paritytech#3793), where the `rocksdb` feature was always activated even when compiling this crate with `--no-default-features`. **Fix:** - Resolved the error by choosing `paritydb` as the default database when compiled without the `rocksdb` feature. - Fixed the issue where the `sc-cli` crate's `rocksdb` feature was always active, even compiling `frame-benchmarking-cli` with `--no-default-features`. ## Review Notes Fix the crate to be built without rocksdb, not intended to solve paritytech#3793. --------- Co-authored-by: command-bot <>
…ritytech#7260) For eth-indexer, it's probably safer to use `subscribe_finalized` and index these blocks into the DB rather than `subscribe_best` --------- Co-authored-by: command-bot <>
Currently `pallet-collator-selection` does not expose a way to query the assigned pot account derived from the `PotId` configuration item. Without it, it is not possible to transfer the existential deposit to it. This PR addresses this issue by exposing an extra constant. --------- Co-authored-by: Bastian Köcher <[email protected]>
Copies all the integration tests from Rococo to Westend. Closes: paritytech#6389
Link-checker job is constantly failing because of these two links. In the browser there is a redirect, apparently our lychee checker can't handle it.
Part of paritytech#6504 --------- Co-authored-by: Bastian Köcher <[email protected]> Co-authored-by: Giuseppe Re <[email protected]>
Signed-off-by: Iulian Barbu <[email protected]>
Signed-off-by: Iulian Barbu <[email protected]>
|
User @iulianbarbu, please sign the CLA here. |
|
/cmd bench --runtime westend --pallet pallets_balances |
|
Command "bench --runtime westend --pallet pallets_balances" has started 🚀 See logs here |
|
Command "bench --runtime westend --pallet pallets_balances" has failed ❌! See logs here |
|
/cmd bench --runtime westend --pallet pallet_balances |
|
Command "bench --runtime westend --pallet pallet_balances" has started 🚀 See logs here |
|
Command "bench --runtime westend --pallet pallet_balances" has failed ❌! See logs here |
2 similar comments
|
Command "bench --runtime westend --pallet pallet_balances" has failed ❌! See logs here |
|
Command "bench --runtime westend --pallet pallet_balances" has failed ❌! See logs here |
|
/cmd bench --runtime westend --pallet pallet_balances |
|
Command "bench --runtime westend --pallet pallet_balances" has started 🚀 See logs here |
…llet pallet_balances'
|
Command "bench --runtime westend --pallet pallet_balances" has finished ✅ See logs here Subweight results:
Command output:✅ Successful benchmarks of runtimes/pallets: |
User @seemantaggarwal, please sign the CLA here.User @skunert, please sign the CLA here.User @pgherveou, please sign the CLA here.User @bkontur, please sign the CLA here.User @yrong, please sign the CLA here.User @runcomet, please sign the CLA here.User @re-gius, please sign the CLA here.User @bgallois, please sign the CLA here.User @Moliholy, please sign the CLA here.User @claravanstaden, please sign the CLA here. |
|
/cmd bench-omni --runtime westend --pallet pallet_balances |
|
Command "bench-omni --runtime westend --pallet pallet_balances" has started 🚀 See logs here |
… --pallet pallet_balances'
|
Command "bench-omni --runtime westend --pallet pallet_balances" has finished ✅ See logs here Subweight results:
Command output:✅ Successful benchmarks of runtimes/pallets: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
test PR