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

Cherry-pick to earlgrey_1.0.0: Revert "[opentitantool] Refuse downgrading HyperDebug firmware" #25937

Open
wants to merge 1 commit into
base: earlgrey_1.0.0
Choose a base branch
from

Conversation

github-actions[bot]
Copy link

This is an automatic cherry-pick of #25934 to branch earlgrey_1.0.0.

This reverts commit 7a0134a, such that
opentitantool no longer requires the `--force` switch in order to
downgrade firmware with `opentitantool transport update-firmware`.
Instead, opentitantool will be back to the original behavior of
overwriting firmware in any case when the version number does not match
exactly.

The original reason for not downgrading was that our branches had
diverged, such that they had different firmware versions, resulting in
CI machines constantly upgrading/downgrading as CI runs from different
branches were scheduled.

PR #25917, however introduced a faulty HyperDebug firmware with never
version number, which is now on a number of CI machines, and will not be
downgraded automatically, with the result that "innocent" other PRs will
have CI failures.

I think it is clear that we should avoid such excessive flashing by
keeping the HyperDebug firmware version in sync between branches.  (We
do not need to keep all of opentitantool logic in sync, just the
built-in firmware version.)  For now, in order to avoid CI failures, we
should merge this PR, and accept some upgrading/downgrading.

Change-Id: I57739777ab3d86fa7e0375834cf9140e8e6ac984
Signed-off-by: Jes B. Klinke <[email protected]>
(cherry picked from commit 2667a3a)
@github-actions github-actions bot requested a review from a team as a code owner January 18, 2025 20:10
@github-actions github-actions bot requested review from HU90m and removed request for a team January 18, 2025 20:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants