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

kci-dev development for milestone 8 #33

Open
3 tasks
nuclearcat opened this issue Oct 16, 2024 · 6 comments
Open
3 tasks

kci-dev development for milestone 8 #33

nuclearcat opened this issue Oct 16, 2024 · 6 comments

Comments

@nuclearcat
Copy link
Member

nuclearcat commented Oct 16, 2024

This issue opened to track changes i planned for kci-dev tool.

Changes

  • Add a --test option to match test and return corresponding code to shell
  • Add bisect subcommand that will use checkout subcommand and git bisect to find the commit that introduced a bug
  • Continue expanding functionality of existing patch subcommand that will test pending patch or patches on specific tree, including storing these patches in kernelci storage system
@aliceinwire
Copy link
Member

the patch sub-command should probably upgrade on this https://github.com/kernelci/kci-dev/blob/main/kci-dev/subcommands/patch.py

@nuclearcat
Copy link
Member Author

Yes, definitely! I will edit main post for more correct explanation.

@aliceinwire
Copy link
Member

by the way what milestone are you referring to ?

@nuclearcat
Copy link
Member Author

We will discuss this weekly, and publish it at next public weekly. I and other team members defining tasks/topics what we would like to work on next 4 weeks from October 21st to November 17th. This will help to understand what features might appear sooner, where we must avoid blocking each other and etc.
And of course anybody who want to contribute/join efforts are welcome.

@aliceinwire
Copy link
Member

are you telling me that this "milestone 8" is based on some collabora internal weekly meeting that will become public in next weeks?

@nuclearcat
Copy link
Member Author

nuclearcat commented Oct 17, 2024

Correct, its more public than internal, today we will start discussing it on our KernelCI weekly.

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

No branches or pull requests

2 participants