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

enable running chaos tests on release packages #435

Closed
wants to merge 1 commit into from
Closed

enable running chaos tests on release packages #435

wants to merge 1 commit into from

Conversation

0xdiba
Copy link
Contributor

@0xdiba 0xdiba commented Jan 20, 2021

No description provided.

@0xdiba 0xdiba requested a review from ivotron January 20, 2021 15:51
@emaxerrno
Copy link
Contributor

@ivotron this has been sitting here for a few weeks. can we review this

@ivotron
Copy link
Member

ivotron commented Feb 10, 2021

we found an issue with the way secrets are shared between forks/base repos. That is being addressed in https://github.com/ivotron/redpanda/tree/slash-commands-refactor but this in turn is being blocked by other changes that are required at the ducktape automation level. I think we could close this PR in the meantime, or mark it as draft so that we revisit once these are resolved. Thoughts @0xdiba ?

@0xdiba
Copy link
Contributor Author

0xdiba commented Feb 11, 2021

This PR was used to run Chaos tests with the packages produced when a release was tagged.
It isn't restricted by the PR-secrets problem (since it is trigger by an internal event) but it depends on the same GitHub action.
We could probably merge it without problems but I think we should be consistent in our way of testing and use the same methods both for ducktape and chaos.

After all, running the chaos tests after release is just a single command away (not so much manual labor saved).

@dotnwat
Copy link
Member

dotnwat commented Apr 13, 2021

@0xdiba merge conflict

@0xdiba
Copy link
Contributor Author

0xdiba commented Apr 13, 2021

@dotnwat I think this is pretty obsolete now since we have moved to task and stuff.
I will close this and open a ticket to coordinate doing this with task.

@0xdiba 0xdiba closed this Apr 13, 2021
@dotnwat
Copy link
Member

dotnwat commented Apr 13, 2021

@dotnwat I think this is pretty obsolete now since we have moved to task and stuff.
I will close this and open a ticket to coordinate doing this with task.

thanks!

travisdowns added a commit to travisdowns/redpanda that referenced this pull request Apr 26, 2023
@travisdowns
Use fetch scheduling group to handle fetches
10721ef 
Add the with_scheduling_group call to switch to the kafka scheduling
group in the fetch handling flow. See prior change for context.

Issue redpanda-data/core-internal/redpanda-data#435.
travisdowns added a commit to travisdowns/redpanda that referenced this pull request Apr 26, 2023
@travisdowns
Use fetch scheduling group to handle fetches
c501a03 
Add the with_scheduling_group call to switch to the kafka scheduling
group in the fetch handling flow. See prior change for context.

Issue redpanda-data/core-internal/redpanda-data#435.
travisdowns added a commit to travisdowns/redpanda that referenced this pull request Apr 26, 2023
@travisdowns
Use fetch scheduling group to handle fetches
9a93a9c 
Add the with_scheduling_group call to switch to the kafka scheduling
group in the fetch handling flow. See prior change for context.

Issue redpanda-data/core-internal/redpanda-data#435.
vbotbuildovich pushed a commit to vbotbuildovich/redpanda that referenced this pull request Apr 27, 2023
@travisdowns @vbotbuildovich
Use fetch scheduling group to handle fetches
6ddc9d1 
Add the with_scheduling_group call to switch to the kafka scheduling
group in the fetch handling flow. See prior change for context.

Issue redpanda-data/core-internal/redpanda-data#435.

(cherry picked from commit 9a93a9c)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ivotron ivotron ivotron left review comments

@dotnwat dotnwat Awaiting requested review from dotnwat

@emaxerrno emaxerrno Awaiting requested review from emaxerrno

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@0xdiba @emaxerrno @ivotron @dotnwat