-
Notifications
You must be signed in to change notification settings - Fork 760
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
Remove message from frame-omni-bencher CLI #7019
Labels
I10-unconfirmed
Issue might be valid, but it's not yet known.
Comments
github-actions
bot
added
the
I10-unconfirmed
Issue might be valid, but it's not yet known.
label
Dec 30, 2024
CC @ggwpez |
github-merge-queue bot
pushed a commit
that referenced
this issue
Jan 2, 2025
# Description This PR removes the outdated warning message from the `frame-omni-bencher` CLI that states the tool is "not yet battle tested". Fixes #7019 ## Integration No integration steps are required. ## Review Notes The functionality of the tool remains unchanged. Removes the warning message from the CLI output. --------- Co-authored-by: Oliver Tale-Yazdi <[email protected]> Co-authored-by: command-bot <>
^ FYI to anyone who clicked it. This was a phishing comment. |
dudo50
pushed a commit
to paraspell-research/polkadot-sdk
that referenced
this issue
Jan 4, 2025
# Description This PR removes the outdated warning message from the `frame-omni-bencher` CLI that states the tool is "not yet battle tested". Fixes paritytech#7019 ## Integration No integration steps are required. ## Review Notes The functionality of the tool remains unchanged. Removes the warning message from the CLI output. --------- Co-authored-by: Oliver Tale-Yazdi <[email protected]> Co-authored-by: command-bot <>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
frame-omni-bencher
CLI currently displays a warning message about the tool not being battle tested, despite being included in the stable release polkadot-stable2412.Current warning message:
The text was updated successfully, but these errors were encountered: