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.

Sign up for GitHub

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

Jump to bottom

Backport failpoints to old releases #17817

Open
serathius opened this issue Apr 17, 2024 · 3 comments
Open

Backport failpoints to old releases #17817

serathius opened this issue Apr 17, 2024 · 3 comments
Assignees
@ciphx
Labels
backport/v3.4 backport/v3.5 help wanted priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. type/feature

Comments

@serathius
Copy link
Member

What would you like to be added?

Backport all the failpoint comments from main branch to release-3.4 and release-3.5.
For example compactBeforeSetFinishedCompact from #17780

TODO:
Find all comments like // gofail: var compactBeforeSetFinishedCompact struct{} and backport them to old releases.

Why is this needed?

This will allow running #17815 on old releases and allow robustness test to use them.
@jmhbnz jmhbnz added backport/v3.4 priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. backport/v3.5 labels May 12, 2024
@serathius serathius mentioned this issue Jun 17, 2024
Merged
@serathius serathius mentioned this issue Aug 19, 2024
Open
8 tasks
@ciphx
Copy link

ciphx commented Sep 12, 2024

Hello @serathius , can you assign this issue to me?

@serathius
Copy link
Member Author

serathius commented Sep 12, 2024 •
edited
Loading

/assign @ciphx

@serathius
Copy link
Member Author

ping @ciphx any progress?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ciphx ciphx

Labels
backport/v3.4 backport/v3.5 help wanted priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. type/feature
Milestone
No milestone
Development

No branches or pull requests
3 participants
@serathius @ciphx @jmhbnz