Skip to content

Conversation

@nuclearcat
Copy link
Member

Sometimes when we issue invalid command during bisect, we need to be less obscure why did it happen and how to reproduce. Also use a bit more correct job-filter/platform-filter commands, even underscore works too.
Example:

ci-dev bisect --workdir kcidev-src/ --giturl https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git --branch linux-5.15.y --job-filter kbuild-gcc-12-x86 --job-filter baseline-x86-intel --test baseline-x86-intel --platform-filter acer-chromebox-cxi4-puff --good 3a5928702e7120f83f703fd566082bfb59f1a57e --bad 584a40a22cb9bf5a03135869f11c3106b6200453
Loaded state file
giturl: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
branch: linux-5.15.y
good: 3a5928702e7120f83f703fd566082bfb59f1a57e
bad: 584a40a22cb9bf5a03135869f11c3106b6200453
retryfail: 2
history: [{'62356668d855deb075a93fdf9f26888c4f80b7d6': 'good'}, {'fdb6429ae356cf2bb4f8a34c3ae7f9f48af78ce7': 'good'}, {'eb54979471aa97182e05aa4e91a1072fa862bf62': 'good'}, {'f30ea678a21e73eb9aaa64f9d11558a9bb85a97f': 'good'}, {'e31942147bf5c7fe532f4703e6229c3ffd075dfe': 'good'}, {'7db54f3ba8cf45a8a3b97472a6f3703293195706': 'good'}]
job_filter: ['kbuild-gcc-12-x86', 'baseline-x86-intel']
platform_filter: ['acer-chromebox-cxi4-puff']
test: baseline-x86-intel
workdir: kcidev-src/
bisect_init: True
next_commit: 83948838e1c7a90015834d62932cec37d04941bf
Pulling repository
Bisection loop
Testing commit: 83948838e1c7a90015834d62932cec37d04941bf
Executing kci-dev command:  ['kci-dev', 'checkout', '--giturl', 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git', '--branch', 'linux-5.15.y', '--test', 'baseline-x86-intel', '--commit', '83948838e1c7a90015834d62932cec37d04941bf', '--watch', '--job-filter', 'kbuild-gcc-12-x86', '--job-filter', 'baseline-x86-intel', '--platform-filter', 'acer-chromebox-cxi4-puff']
maestro api endpoint: https://staging.kernelci.org:9100/api/checkout
Unknown or critical return code from kci-dev: 64. Try to run last command manually and inspect the output:
kci-dev checkout --giturl https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git --branch linux-5.15.y --test baseline-x86-intel --commit 83948838e1c7a90015834d62932cec37d04941bf --watch --job-filter kbuild-gcc-12-x86 --job-filter baseline-x86-intel --platform-filter acer-chromebox-cxi4-puff

Sometimes when we issue invalid command during bisect, we need
to be less obscure why did it happen and how to reproduce.
Also use a bit more correct job-filter/platform-filter commands,
even underscore works too.

Signed-off-by: Denys Fedoryshchenko <denys.f@collabora.com>
@aliceinwire
Copy link
Member

This is draft, you intend to add this on 0.1.2 or 0.1.3?

@nuclearcat
Copy link
Member Author

I think 0.1.3, it is more cosmetics change and easier troubleshooting. I will test it a bit more, maybe will add some improvements.

@aliceinwire aliceinwire added this to the v0.1.3 milestone Jan 21, 2025
@nuclearcat nuclearcat marked this pull request as ready for review January 23, 2025 11:46
@aliceinwire aliceinwire merged commit 49a8828 into kernelci:main Jan 23, 2025
2 checks passed
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