Skip to content
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

[subsystem-benchmarks] Fix availability-write regression tests #3698

Merged
merged 42 commits into from
Mar 25, 2024

Conversation

AndreiEres
Copy link
Contributor

@AndreiEres AndreiEres commented Mar 14, 2024

Adds availability-write regression tests.
The results for the availability-distribution subsystem are volatile, so I had to reduce the precision of the test.

@AndreiEres AndreiEres added R0-silent Changes should not be mentioned in any release notes T12-benchmarks This PR/Issue is related to benchmarking and weights. labels Mar 14, 2024
@AndreiEres AndreiEres marked this pull request as ready for review March 14, 2024 16:00
@AndreiEres AndreiEres requested a review from a team as a code owner March 14, 2024 16:00
@paritytech-review-bot paritytech-review-bot bot requested a review from a team March 14, 2024 17:37
@AndreiEres AndreiEres changed the title [WIP] Fix availability-write regression tests Fix availability-write regression tests Mar 15, 2024
@AndreiEres AndreiEres changed the title [WIP] Fix availability-write regression tests Fix availability-write regression tests Mar 22, 2024
Copy link
Contributor

@sandreim sandreim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work! Let's let them be with {"build_allow_failure":true} for a while and see if there is any more flakiness.

messages.extend(usage.check_network_usage(&[
("Received from peers", 307200.000, 0.05),
("Sent to peers", 1.667, 0.05),
// We don't expect any other values for received and sent
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rephrase it as no variance is expected here, also, why not 0.0 ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Set it to 0.001 because we operate with floats

@paritytech-cicd-pr
Copy link

The CI pipeline was cancelled due to failure one of the required jobs.
Job name: cargo-clippy
Logs: https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/5622613

Copy link
Contributor

@alexggh alexggh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

@AndreiEres AndreiEres changed the title Fix availability-write regression tests [subsystem-benchmarks] Fix availability-write regression tests Mar 25, 2024
@AndreiEres AndreiEres added this pull request to the merge queue Mar 25, 2024
Merged via the queue into master with commit cc1e6ac Mar 25, 2024
128 of 134 checks passed
@AndreiEres AndreiEres deleted the AndreiEres/av-write-regression branch March 25, 2024 16:56
@dcompoze
Copy link
Contributor

After this was merged, the CI now fails on TOML format of polkadot/node/subsystem-bench/Cargo.toml and also the continuous-integration/gitlab-subsystem-regression-tests job seems to fail.

github-merge-queue bot pushed a commit that referenced this pull request Mar 26, 2024
dharjeezy pushed a commit to dharjeezy/polkadot-sdk that referenced this pull request Apr 9, 2024
…ytech#3698)

Adds availability-write regression tests.
The results for the `availability-distribution` subsystem are volatile,
so I had to reduce the precision of the test.
dharjeezy pushed a commit to dharjeezy/polkadot-sdk that referenced this pull request Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R0-silent Changes should not be mentioned in any release notes T12-benchmarks This PR/Issue is related to benchmarking and weights.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants