search

kernelci / kci-dev

Tool for interact with KernelCI instances
https://kernelci.github.io/kci-dev/
GNU Lesser General Public License v2.1
1 stars 2 forks source link

feat(checkout): Add custom checkout command #24

Closed nuclearcat closed 3 weeks ago

nuclearcat commented 3 weeks ago

Add command to trigger custom checkout and run all or selected test on this checkout.

aliceinwire commented 3 weeks ago

documentation is missing

nuclearcat commented 3 weeks ago

Yes, still in progress, will add as separate commit

aliceinwire commented 3 weeks ago

I'm not sure if this should be merged with the commit subcommand

nuclearcat commented 3 weeks ago

What are other options? I'm open to suggestions.

As next plans, in separate PR i am planning to add --watch option to this checkout option, so this will be key tool to automated bisection, key option. So for example: kci-dev bisect badcommit goodcommit kbuildname testsuite [testname] will run git bisect, obtain first suggested by it commit and start

kci-dev checkout (tree and branch options and jobfilter) --commit firstcommit --watch testname/testsuite

Then it will track progress, how tree being built and etc. If result fail -it will give "git bisect bad" (and if good - opposite) and test next commit, until we find offending commit. P.S. Also as Pawel suggested, it might be that some commits are not building, so it will be git bisect skip in such cases.

aliceinwire commented 3 weeks ago

What are other options? I'm open to suggestions.

As next plans, in separate PR i am planning to add --watch option to this checkout option, so this will be key tool to automated bisection, key option. So for example: kci-dev bisect badcommit goodcommit kbuildname testsuite [testname] will run git bisect, obtain first suggested by it commit and start

kci-dev checkout (tree and branch options and jobfilter) --commit firstcommit --watch testname/testsuite

Then it will track progress, how tree being built and etc. If result fail -it will give "git bisect bad" (and if good - opposite) and test next commit, until we find offending commit. P.S. Also as Pawel suggested, it might be that some commits are not building, so it will be git bisect skip in such cases.

I see! I'm ok with merging the checkout command, thanks for working on this. I was just thinking how much was going to be different from the commit command but this answered the question. thanks

aliceinwire commented 3 weeks ago

checkout.md is empty I suppose we will write with the progress of the command features

nuclearcat commented 3 weeks ago

checkout.md is empty I suppose we will write with the progress of the command features

One minute, seems deleted content by mistake.