Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Run all benchmarks "as tests" in short setup on every PR #2846

Merged
merged 31 commits into from
Jul 22, 2023

Conversation

bkontur
Copy link
Contributor

@bkontur bkontur commented Jul 10, 2023

Inspired by: #2806 (comment)

Closes: #2806

TODOs

  • check # TODO: can we remove this?
  • update substrate ref because of asset-hub-westend issue

@bkontur bkontur added B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders. labels Jul 10, 2023
@bkontur bkontur marked this pull request as ready for review July 10, 2023 14:51
@bkontur bkontur requested review from a team as code owners July 10, 2023 14:51
@bkontur bkontur added the A0-please_review Pull request needs code review. label Jul 10, 2023
# # benchmarks jobs
# # TODO: can we remove this?-
- scripts/ci/gitlab/pipeline/benchmarks.yml
Copy link
Member

Choose a reason for hiding this comment

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

Looks like this one is automatically creating a MR to update the weights? I dont know if that is used.

Copy link
Contributor

@alvicsam alvicsam Jul 10, 2023

Choose a reason for hiding this comment

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

Correct, but it works only with release-parachains-v* branches. Last time it was used month ago

Copy link
Contributor

Choose a reason for hiding this comment

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

@ggwpez yes, it is used for the releases, when the benchmark job is triggered from git lab. We used to do it manually so far

Copy link
Contributor Author

@bkontur bkontur Jul 11, 2023

Choose a reason for hiding this comment

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

@EgorPopelyaev @ggwpez @joepetrowski @chevdor @alvicsam @bkchr
so for the very next release to regenerate weights, do we want to use:

  1. old way with manual gitlab job?
  2. new bot bench $ all ?

Copy link
Contributor

Choose a reason for hiding this comment

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

@bkontur lets's proceed with the new bot solution if it does a thing, but I would still keep the old pipeline yaml, as a plan B. At least for the next release

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@EgorPopelyaev ok, good point

@paritytech-ci paritytech-ci requested a review from a team July 10, 2023 15:15
@bkontur
Copy link
Contributor Author

bkontur commented Jul 11, 2023

bot rebase

@paritytech-processbot
Copy link

Rebased

@bkontur bkontur requested a review from alvicsam July 11, 2023 22:40
@paritytech-ci paritytech-ci requested a review from a team July 12, 2023 07:19
@bkontur
Copy link
Contributor Author

bkontur commented Jul 12, 2023

bot rebase

@paritytech-processbot
Copy link

Rebased

@bkontur
Copy link
Contributor Author

bkontur commented Jul 22, 2023

bot merge

@paritytech-processbot
Copy link

Waiting for commit status.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A0-please_review Pull request needs code review. B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[CI/CD] Run all benchmarks as (unit)tests on every PR
5 participants