Skip to content

Conversation

JenySadadia
Copy link

Restructure KCIDB issues related commands.

Modifications:

  • Remove issues command group and subcommand handlers as part of command restructuring
  • Implement results issue command
    • Fetch KCIDB issue matching provided ID. Also, get associated builds and tests.
      kci-dev results issue --id <id> --origin <origin>
  • Implement results issues command
    • Fetch KCIDB issues from the dashboard
    • Get new issues for checkout with --new option
    • Get failed/inconclusive builds and boots without
      any associated issues with --missing option

@JenySadadia JenySadadia marked this pull request as ready for review August 7, 2025 10:35
@JenySadadia JenySadadia requested a review from padovan August 7, 2025 10:35
@JenySadadia
Copy link
Author

issue command output:

$ kci-dev results issue --id redhat:issue_2753
Issue information:
- Issue ID: redhat:issue_2753
  origin: redhat
  version: 1716387967
  comment: KUNIT: KFENCE failed to allocate
  field_timestamp: 2025-08-06T23:44:44.050949Z
  culprit_code: True
  culprit_tool: False
  culprit_harness: False

Associated builds:
No associated builds found

Associated tests:
- redhat:1626193375-aarch64-kernel-64k_upt_18
- redhat:1633276830-aarch64-kernel-64k_upt_18
- redhat:1633379163-aarch64-kernel-64k_upt_7
- redhat:1634393276-aarch64-kernel-64k_upt_19
- redhat:1634768214-ppc64le-kernel_upt_8
- redhat:1626664281-aarch64-kernel_upt_18
- redhat:1635006205-aarch64-kernel-64k_upt_19
- redhat:1569812661-ppc64le-kernel_upt_15
- redhat:koji-126644432-aarch64-kernel-64k_upt_6
- redhat:1639467482-aarch64-kernel-64k_upt_16
- redhat:1640007736-aarch64-kernel_upt_18
- redhat:1640003284-aarch64-kernel_upt_18
- redhat:1641503170-x86_64-kernel_upt_13
- redhat:1642354951-x86_64-kernel_upt_13
- redhat:1639467482-aarch64-kernel-64k_upt_16
- redhat:1576630306-aarch64-kernel-64k_upt_18
- redhat:koji-126697389-aarch64-kernel-64k_upt_6
- redhat:1692715109-ppc64le-kernel_upt_9
- redhat:1692766765-ppc64le-kernel_upt_9
- redhat:1693711336-ppc64le-kernel_upt_9
- redhat:1696353777-ppc64le-kernel_upt_16
- redhat:1697622989-ppc64le-kernel_upt_9
- redhat:1697552504-ppc64le-kernel_upt_17
- redhat:koji-129805675-aarch64-kernel-64k_upt_6
- redhat:koji-129867125-aarch64-kernel-64k_upt_6
- redhat:koji-129867125-aarch64-kernel-64k_upt_6
- redhat:koji-129949568-aarch64-kernel-64k_upt_6
- redhat:koji-129949568-aarch64-kernel-64k_upt_6
- redhat:1707109024-ppc64le-kernel_upt_18
- redhat:koji-130442758-aarch64-kernel-64k_upt_6
- redhat:koji-126942713-aarch64-kernel-64k_upt_6
- redhat:1592388569-aarch64-kernel-64k_upt_19
- redhat:koji-126965714-ppc64le-kernel_upt_12
- redhat:koji-126965714-aarch64-kernel-64k_upt_6
- redhat:1593667542-ppc64le-kernel_upt_8
- redhat:1610403851-ppc64le-kernel_upt_7
- redhat:koji-127641511-aarch64-kernel-64k_upt_6
- redhat:1618796740-aarch64-kernel-64k_upt_25
- redhat:1620200259-aarch64-kernel-64k_upt_19
- redhat:koji-127862062-ppc64le-kernel_upt_12
- redhat:koji-127862062-aarch64-kernel-64k_upt_6
- redhat:1732228635-aarch64-kernel-64k_upt_28
- redhat:1732307255-aarch64-kernel-64k_upt_68
- redhat:1736522618-aarch64-kernel-64k_upt_18
- redhat:1736507484-aarch64-kernel_upt_20
- redhat:1738799082-aarch64-kernel-rt-64k_upt_18
- redhat:1738799119-ppc64le-kernel_upt_10
- redhat:koji-130814469-aarch64-kernel-64k_upt_6
- redhat:koji-130814469-aarch64-kernel_upt_6
- redhat:1741035423-ppc64le-kernel_upt_16
- redhat:koji-130946606-aarch64-kernel-64k_upt_6
- redhat:1745508299-ppc64le-kernel_upt_17
- redhat:1745508299-ppc64le-kernel_upt_17
- redhat:koji-133463419-x86_64-kernel_upt_6
- redhat:koji-133463419-x86_64-kernel_upt_6
- redhat:koji-130987467-aarch64-kernel-64k_upt_6
- redhat:koji-131343286-aarch64-kernel-64k_upt_6
- redhat:1766309500-aarch64-kernel-64k_upt_71
- redhat:koji-131564191-aarch64-kernel-64k_upt_6
- redhat:koji-131564191-aarch64-kernel-64k_upt_6
- redhat:koji-131646726-aarch64-kernel-64k_upt_6
- redhat:koji-131679199-x86_64-kernel_upt_6
- redhat:koji-131861103-x86_64-kernel_upt_6
- redhat:koji-131861103-x86_64-kernel_upt_6
- redhat:koji-131910167-x86_64-kernel_upt_6
- redhat:koji-132433399-x86_64-kernel_upt_6
- redhat:koji-132682609-x86_64-kernel_upt_6
- redhat:koji-132682609-x86_64-kernel_upt_6
- redhat:koji-132733158-x86_64-kernel_upt_6
- redhat:koji-133013980-x86_64-kernel_upt_6
- redhat:koji-133624968-x86_64-kernel_upt_6
- redhat:koji-133368318-x86_64-kernel_upt_6
- redhat:koji-133873019-x86_64-kernel_upt_6
- redhat:koji-134361516-x86_64-kernel_upt_6
- redhat:koji-134772687-x86_64-kernel_upt_6
- redhat:koji-135166239-x86_64-kernel_upt_6
- redhat:koji-135437850-x86_64-kernel_upt_6
- redhat:koji-135704936-x86_64-kernel_upt_6
- redhat:1587400690-ppc64le-kernel_upt_12
- redhat:1587473818-ppc64le-kernel_upt_8
$ kci-dev results issue --id maestro:d8317f5d8e192f5277f02847d9c2dbc0a47c1888
Issue information:
- Issue ID: maestro:d8317f5d8e192f5277f02847d9c2dbc0a47c1888
  origin: maestro
  version: 1
  comment:  suggest parentheses around comparison in operand of ‘|’ [-Werror=parentheses] in drivers/misc/mediatek/slbc/slbc_mt8196.o (drivers/misc/mediatek/slbc/slbc_mt8196.c) [logspec:kbuild,kbuild.compiler.error]
  field_timestamp: 2025-08-06T10:58:37.609586Z
  culprit_code: True
  culprit_tool: False
  culprit_harness: False

Associated builds:
- maestro:688395cef2919f099dfc1fd2
- maestro:6886e5dff2919f099d049c05
- maestro:6887fd83759fd8fd442bccf9
- maestro:6888e5a1759fd8fd442ff66b
- maestro:688abe85759fd8fd4437b1d1
- maestro:688b21af759fd8fd4438a7a3
- maestro:688c55fe236da8c8a0d0dbd3
- maestro:688c8d68236da8c8a0d1f505
- maestro:68906303236da8c8a0d77cfa
- maestro:6892e6a079d5d217e545652c

Associated tests:
No associated tests found

@JenySadadia JenySadadia marked this pull request as draft August 7, 2025 10:46
@JenySadadia JenySadadia force-pushed the restructure-issues-cmd branch from d2c51f3 to 3c5ac24 Compare August 7, 2025 11:39
@JenySadadia
Copy link
Author

Issues command output:

$ kci-dev results issues
- Issue ID: maestro:b521ccaba0bc36c8ba1608c5bba5120a880aa7e4
  origin: maestro
  version: 1
  comment:  in /tmp/kci/linux/tools/testing/selftests/acct/acct_syscall (../lib.mk:222) [logspec:kbuild,kbuild.compiler]
  field_timestamp: 2025-08-07T09:28:35.009160Z
  culprit_code: True
  culprit_tool: False
  culprit_harness: False

- Issue ID: maestro:721516cb40a17ba5aaddc2e6e410d3eec5c49fc6
  origin: maestro
  version: 1
  comment:  WARNING: Unclean boot. Reached prompt but marked as failed. [logspec:generic_linux_boot,maestro.linux.kernel.boot]
  field_timestamp: 2025-08-06T17:43:13.877767Z
  culprit_code: True
  culprit_tool: False
  culprit_harness: False

- Issue ID: maestro:e602fca280d85d8e603f7c0aff68363bb0cd7993
  origin: maestro
  version: 1
  comment:  Bootloader did not finish or kernel did not start. [logspec:generic_linux_boot,maestro.linux.kernel.boot]
  field_timestamp: 2025-08-07T09:29:11.162902Z
  culprit_code: True
  culprit_tool: False
  culprit_harness: False

- Issue ID: maestro:9f62126602458a4234fed52f1605db5e17457615
  origin: maestro
  version: 1
  comment:  clang: error: linker command failed with exit code 1 (use -v to see invocation) in /tmp/kci/linux/tools/testing/selftests/exec/load_address.static.0x1000 (Makefile:46) [logspec:kbuild,kbuild.other]
  field_timestamp: 2025-08-05T03:33:28.776430Z
  culprit_code: True
  culprit_tool: False
  culprit_harness: False

- Issue ID: maestro:b46d73b45df05158d4ef06c7116444146c7a4ab3
  origin: maestro
  version: 1
  comment:  in vmlinux (Makefile:1226) [logspec:kbuild,kbuild.other]
  field_timestamp: 2025-08-06T18:13:45.177081Z
  culprit_code: True
  culprit_tool: False
  culprit_harness: False

- Issue ID: maestro:a8ba4fd7ab9f996d9e569f77d5cf91354e7a783b
  origin: maestro
  version: 1
  comment:  in /tmp/kci/linux/tools/testing/selftests/fchmodat2/fchmodat2_test (../lib.mk:222) [logspec:kbuild,kbuild.other]
  field_timestamp: 2025-08-05T08:10:31.529217Z
  culprit_code: True
  culprit_tool: False
  culprit_harness: False

- Issue ID: maestro:1d98f1676e29fca15e5ee7c886db2f060ed341e5
  origin: maestro
  version: 1
  comment:  incompatible pointer to integer conversion returning 'void *' from a function with result type 'int' [-Wint-conversion] in drivers/media/platform/camx/cam_sensor_module/cam_eeprom/cam_eeprom_dev.o (drivers/media/platform/camx/cam_sensor_module/cam_eeprom/cam_eeprom_dev.c) [logspec:kbuild,kbuild.compiler.error]
  field_timestamp: 2025-08-04T11:53:17.879595Z
  culprit_code: True
  culprit_tool: False
  culprit_harness: False

- Issue ID: maestro:5ce5dc1862bf3e513dd0196750a67e49f751f73a
  origin: maestro
  version: 1
  comment:  in /tmp/kci/linux/tools/testing/selftests/cachestat/test_cachestat (../lib.mk:222) [logspec:kbuild,kbuild.compiler]
  field_timestamp: 2025-08-07T10:21:33.232266Z
  culprit_code: True
  culprit_tool: False
  culprit_harness: False

$ kci-dev results issues --missing
Fetching data for builds...
android/android15-6.6: 
  - Commit:b81b7955a6b4a374f56d4369ff697d4b6ba67dc7
  maestro:6893d05679d5d217e546d38d
chromiumos/chromeos-6.6: 
  - Commit:bd2758313476964ef28591f95d7480d62e4e8d2d
  maestro:6893d05679d5d217e546d38d
netdev-testing/net-next-hw-2025-08-06--00-00: 
  - Commit:1a25bad6a92e8e02baac2301142a67dcdb5775e3
  maestro:6893d05679d5d217e546d38d
netdev-testing/net-next-hw-2025-08-06--08-00: 
  - Commit:9cdaa0f0abb1b9141bb6f4971e4ee5c614e78b8a
  maestro:6893d05679d5d217e546d38d
netdev-testing/net-next-hw-2025-08-02--16-00: 
  - Commit:e18d338c03ca7d1c455ff5b312bbe4151cd70732
  maestro:6893d05679d5d217e546d38d
sashal-next/linus-next: 
  - Commit:5d508e02491e32dc9d2797ba732d11facbb368a6
  maestro:6893d05679d5d217e546d38d

Fetching data for boots...
android/android16-6.12: 
  - Commit:886d2f37b79982531259490548bc83b9216ca685
  maestro:6893233d79d5d217e54616d7
  maestro:6893233e79d5d217e54616da
  maestro:6893233e79d5d217e54616dd
  maestro:6893233c79d5d217e54616d4
  maestro:6893284579d5d217e546198d
  maestro:6893284679d5d217e5461990
  maestro:6893284079d5d217e546196c
  maestro:6893284679d5d217e5461993
  maestro:6893284779d5d217e5461996
  maestro:6893284379d5d217e5461981
  maestro:6893307379d5d217e5461bdd
  maestro:6893307479d5d217e5461be6
android/android-mainline: 
  - Commit:d8052c63548133e7cfcefbc7bf5027214df7822b
  maestro:6893233d79d5d217e54616d7
  maestro:6893233e79d5d217e54616da
  maestro:6893233e79d5d217e54616dd
  maestro:6893233c79d5d217e54616d4
  maestro:6893284579d5d217e546198d
  maestro:6893284679d5d217e5461990
  maestro:6893284079d5d217e546196c
  maestro:6893284679d5d217e5461993
  maestro:6893284779d5d217e5461996
  maestro:6893284379d5d217e5461981
  maestro:6893307379d5d217e5461bdd
  maestro:6893307479d5d217e5461be6
$ kci-dev results issues --new --commit efe5eff6f49306b5c6012f769243928019a89612 --giturl https://gitlab.com/cki-project/kernel-ark.git --branch ark-latest --origin redhat
Fetching new issues for the checkout...
c10s/ark-latest:efe5eff6f49306b5c6012f769243928019a89612
- redhat:afdebd9b5ec1d3fb752bb500e14770b7e3cb39a2
- redhat:c3802939746ca44995a25d9ba8c842e4d71fdf43
- redhat:eaf666adebfc9681742f6930aee1769b215b4232
$ kci-dev results issues --new --origin redhat
Fetching new issues for all checkouts...
c10s/ark-latest:efe5eff6f49306b5c6012f769243928019a89612
- redhat:afdebd9b5ec1d3fb752bb500e14770b7e3cb39a2
- redhat:c3802939746ca44995a25d9ba8c842e4d71fdf43
- redhat:eaf666adebfc9681742f6930aee1769b215b4232
c10s/main:6a78f7dea47e1aadaa209c416cc5187b19372462
No issues found
c9s/main-automotive:3b98869e6058239cb0cb345a1490e7aa62acbcdc
No issues found
c9s/main:9f87d5353e1869a65e80e9b334f498510ba8475e
No issues found
fedora-eln/None:None
ERROR:root:API returned error: No results available for this tree/branch/commit
{'error': 'No results available for this tree/branch/commit'}
Exception: No results available for this tree/branch/commit
mainline/master:6e64f4580381e32c06ee146ca807c555b8f73e24
No new issues found
stable-rc/queue/6.15:3e4cd0751f0dc001f06296e86b850bb06ed0fe8c
No issues found
stable-rt/v5.10-rt:502b544c60cfebcd564285a0c807cf32b1a3e656
No new issues found
upstream-block/for-next:20c74c07321713217b2f84c55dfd717729aa6111
No new issues found
upstream-nf-next/main:d9104cec3e8fe4b458b74709853231385779001f
No issues found
upstream-stable/linux-6.15.y:097aa9a71fd56cdc62c11bdf45a84f07acaa3604
No new issues found
upstream-tnguy-net/dev-queue:0af56426e9a59084bca60a0d4dc1dc995e2808ee
No issues found
upstream-tnguy-next/dev-queue:dfc2efdee6179dfcef9bab3c26b8663ca9d22bf0
No new issues found

@JenySadadia JenySadadia marked this pull request as ready for review August 7, 2025 11:40
@padovan
Copy link
Contributor

padovan commented Aug 7, 2025

Hi Jeny, thanks for these changes. I'll add some comments:

kci-dev results issues

  • highlight comment as the title - first line of the data. In that case I think we can just omit "comment:"
  • add a link to the dashboard.
  • add tree/branch of the first incident (if there is no incident, we can ignore that issue for now)
  • new issues should have a NEW tag in red.

kci-dev results issues --missing

  • add link to the dashboard, instead of issue id directly
  • then, in front of the link add "(status: )", so we know the status before clicking on the link

kci-dev results issues --new <>

  • should use the same output form as kci-dev results issues`. If we add tree/branch of the first incident there, then we are ready to just pass the a list of issues to the print function.

@JenySadadia JenySadadia force-pushed the restructure-issues-cmd branch 2 times, most recently from c2bf3ed to 1ab70d3 Compare August 11, 2025 10:01
@JenySadadia
Copy link
Author

Hi Jeny, thanks for these changes. I'll add some comments:

Thank you for the feedback.

kci-dev results issues

  • highlight comment as the title - first line of the data. In that case I think we can just omit "comment:"
  • add a link to the dashboard.
  • add tree/branch of the first incident (if there is no incident, we can ignore that issue for now)
  • new issues should have a NEW tag in red.

Addressed all the comments except the last one.
Here we are listing down all the issues. The issue will have tree/branch of the first incident. Hence, this tag isn't applicable here. The tag can be applied if we separate issues based on tree/branch.

kci-dev results issues --missing

  • add link to the dashboard, instead of issue id directly
  • then, in front of the link add "(status: )", so we know the status before clicking on the link

Done.

kci-dev results issues --new <>

  • should use the same output form as kci-dev results issues`. If we add tree/branch of the first incident there, then we are ready to just pass the a list of issues to the print function.

Done.

@JenySadadia JenySadadia force-pushed the restructure-issues-cmd branch from 1ab70d3 to 9ceaec7 Compare August 11, 2025 10:11
@padovan
Copy link
Contributor

padovan commented Aug 13, 2025

  1. kci-dev results issues --giturl https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git --branch master

is not filtering by tree/branch

  1. if I add --new to the line above without mentioning the --commit, it should give a error telling the user that the commit is missing

1 similar comment
@padovan
Copy link
Contributor

padovan commented Aug 13, 2025

  1. kci-dev results issues --giturl https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git --branch master

is not filtering by tree/branch

  1. if I add --new to the line above without mentioning the --commit, it should give a error telling the user that the commit is missing

@JenySadadia
Copy link
Author

  1. kci-dev results issues --giturl https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git --branch master

is not filtering by tree/branch

I think this was already discussed on the etherpad.

3. Add --giturl, --branch --commit (or --latest) parameters to `results issues`, so we can filter then per tree/branch/commit

> (Jeny) Issues are independent of git branch, URL, or commit. Hence, can't be filtered by these options. If we filter issues based on incidents, issues without any incidents associated to it, will not be listed.

> (Gus) Indeed. However, I mean filtering by the info on the incident. Maybe we can park this as just create a GH issues for the time being, then wait the work on the Dashboard DB to solidify. We will do a issues refactor when that happens.

> (Jeny) Ok, I'll create a GH issue. Thanks.
  1. if I add --new to the line above without mentioning the --commit, it should give a error telling the user that the commit is missing

Done.

@JenySadadia JenySadadia force-pushed the restructure-issues-cmd branch 2 times, most recently from df6d8a9 to 910c239 Compare August 18, 2025 05:38
@aliceinwire
Copy link
Member

  1. kci-dev results issues --giturl https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git --branch master

is not filtering by tree/branch

I think this was already discussed on the etherpad.

what etherpad?

@JenySadadia
Copy link
Author

  1. kci-dev results issues --giturl https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git --branch master

is not filtering by tree/branch

I think this was already discussed on the etherpad.

what etherpad?

This PR is based on the feedback I received from @padovan
Here is the link to it https://etherpad.collabora.com/p/kci-dev_results_issues

@JenySadadia
Copy link
Author

  1. kci-dev results issues --giturl https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git --branch master

is not filtering by tree/branch

I think this was already discussed on the etherpad.

3. Add --giturl, --branch --commit (or --latest) parameters to `results issues`, so we can filter then per tree/branch/commit

> (Jeny) Issues are independent of git branch, URL, or commit. Hence, can't be filtered by these options. If we filter issues based on incidents, issues without any incidents associated to it, will not be listed.

> (Gus) Indeed. However, I mean filtering by the info on the incident. Maybe we can park this as just create a GH issues for the time being, then wait the work on the Dashboard DB to solidify. We will do a issues refactor when that happens.

> (Jeny) Ok, I'll create a GH issue. Thanks.

As per our latest conversation, I'll handle issue filtering from kci-dev side for now.

  1. if I add --new to the line above without mentioning the --commit, it should give a error telling the user that the commit is missing

Done.

@aliceinwire
Copy link
Member

  1. kci-dev results issues --giturl https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git --branch master

is not filtering by tree/branch

I think this was already discussed on the etherpad.

3. Add --giturl, --branch --commit (or --latest) parameters to `results issues`, so we can filter then per tree/branch/commit

> (Jeny) Issues are independent of git branch, URL, or commit. Hence, can't be filtered by these options. If we filter issues based on incidents, issues without any incidents associated to it, will not be listed.

> (Gus) Indeed. However, I mean filtering by the info on the incident. Maybe we can park this as just create a GH issues for the time being, then wait the work on the Dashboard DB to solidify. We will do a issues refactor when that happens.

> (Jeny) Ok, I'll create a GH issue. Thanks.

As per our latest conversation, I'll handle issue filtering from kci-dev side for now.

  1. if I add --new to the line above without mentioning the --commit, it should give a error telling the user that the commit is missing

Done.

  1. kci-dev results issues --giturl https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git --branch master

is not filtering by tree/branch

I think this was already discussed on the etherpad.

what etherpad?

This PR is based on the feedback I received from @padovan Here is the link to it https://etherpad.collabora.com/p/kci-dev_results_issues

  1. kci-dev results issues --giturl https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git --branch master

is not filtering by tree/branch

I think this was already discussed on the etherpad.

3. Add --giturl, --branch --commit (or --latest) parameters to `results issues`, so we can filter then per tree/branch/commit

> (Jeny) Issues are independent of git branch, URL, or commit. Hence, can't be filtered by these options. If we filter issues based on incidents, issues without any incidents associated to it, will not be listed.

> (Gus) Indeed. However, I mean filtering by the info on the incident. Maybe we can park this as just create a GH issues for the time being, then wait the work on the Dashboard DB to solidify. We will do a issues refactor when that happens.

> (Jeny) Ok, I'll create a GH issue. Thanks.

As per our latest conversation, I'll handle issue filtering from kci-dev side for now.

Filtering issues will be handled on this PR or a different PR?

@JenySadadia
Copy link
Author

I'll make changes to this PR.

@aliceinwire
Copy link
Member

I'll make changes to this PR.

ok, thanks

Remove `issues` command group and subcommand
handlers as part of command restructuring.

Signed-off-by: Jeny Sadadia <[email protected]>
@JenySadadia
Copy link
Author

Hi @padovan

Here is the sample output with issue filtering working:

$ kci-dev results issues --giturl https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git --branch master --commit next-20250820 --origin maestro
resolved to: 5303936d609e09665deda94eaedf26a0e5c3a087
next/master:5303936d609e09665deda94eaedf26a0e5c3a087
-  the frame size of 1448 bytes is larger than 1024 bytes [-Werror=frame-larger-than=] in drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn10/dcn10_hwseq.o (drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn10/dcn10_hwseq.c) [logspec:kbuild,kbuild.compiler.error]
  https://dashboard.kernelci.org/issue/maestro:4d4120bf99fecc5f852604382b7c406b99440116
  origin: maestro
  version: 1
  field_timestamp: 2025-08-20T05:03:27.970827Z
  culprit_code: True
  First incident seen on next/master

-  ‘pinmux_generic_get_function_count’ undeclared here (not in a function); did you mean ‘pinmux_generic_free_functions’? in drivers/pinctrl/qcom/pinctrl-msm.o (drivers/pinctrl/qcom/pinctrl-msm.c) [logspec:kbuild,kbuild.compiler.error]  NEW
  https://dashboard.kernelci.org/issue/maestro:4466df3c987ba2945eca05fcb2f3c22e97d8636a
  origin: maestro
  version: 1
  field_timestamp: 2025-08-20T04:52:00.879437Z
  culprit_code: True
  First incident seen on next/master

-  Bootloader did not finish or kernel did not start. [logspec:generic_linux_boot,maestro.linux.kernel.boot]
  https://dashboard.kernelci.org/issue/maestro:da694c56147298d223ee432ad8d6a8ee311b773a
  origin: maestro
  version: 1
  field_timestamp: 2025-08-20T09:41:12.706877Z
  culprit_code: True
  First incident seen on net-next/main

-  sleeping function called from invalid context at kernel/locking/rwsem.c:1589 [logspec:generic_linux_boot,linux.kernel.bug]  NEW
  https://dashboard.kernelci.org/issue/maestro:4a7604ad2b208f9142109c871e17a6453ee9ff9c
  origin: maestro
  version: 1
  field_timestamp: 2025-08-20T07:25:46.101792Z
  culprit_code: True
  First incident seen on next/master

-  shift-out-of-bounds: shift exponent -1 is negative [logspec:generic_linux_boot,linux.kernel.ubsan]
  https://dashboard.kernelci.org/issue/maestro:b91eba41d9d0281c086ee574a82bdee035760751
  origin: maestro
  version: 1
  field_timestamp: 2025-08-20T07:25:46.101792Z
  culprit_code: True
  First incident seen on None/None

Note: New issues will have a NEW tag alongside the issue title.

@JenySadadia JenySadadia force-pushed the restructure-issues-cmd branch from 910c239 to 869104f Compare August 20, 2025 11:33
To avoid printing error returned from API,
use `error_verbose` option while sending
GET request to dashboard API.
Add the option to `results builds` and
`results boots` command.
This change is needed to avoid a flood
of error message while fetching new/missing
issues with `results issues` command.

Signed-off-by: Jeny Sadadia <[email protected]>
@JenySadadia JenySadadia force-pushed the restructure-issues-cmd branch from 869104f to fbc9cde Compare August 20, 2025 11:39
@padovan
Copy link
Contributor

padovan commented Aug 20, 2025

@JenySadadia sounds good. The 2 issues that don't have next/master in the first incident still have incidents on the tree.

As for the NEW tag, let's add it to the beginning of the line:

[NEW] sleeping function called from invalid context at kernel/locking/rwsem.c:1589 [logspec:generic_linux_boot,linux.kernel.bug]

With [NEW] in green or red

Jeny Sadadia added 2 commits August 20, 2025 20:24
Fetch KCIDB issue matching provided ID.
Also get associated builds and tests.
Sample command:
`kci-dev results issue --id <id> --origin <origin>`

Signed-off-by: Jeny Sadadia <[email protected]>
`kci-dev results issues` command utilities:
- Fetch KCIDB issues from the dashboard with `results issues`
command
- Filter issues by checkout by providing `--giturl`, `--branch`,
`--commit` and `--tree`(optional) options
- Get new issues for checkouts with `--new` option
- Get failed/inconclusive builds and boots without
any associated issues with `--missing` option

Signed-off-by: Jeny Sadadia <[email protected]>
@JenySadadia JenySadadia force-pushed the restructure-issues-cmd branch from fbc9cde to 5256faf Compare August 20, 2025 14:54
@JenySadadia
Copy link
Author

@JenySadadia sounds good. The 2 issues that don't have next/master in the first incident still have incidents on the tree.

As for the NEW tag, let's add it to the beginning of the line:

[NEW] sleeping function called from invalid context at kernel/locking/rwsem.c:1589 [logspec:generic_linux_boot,linux.kernel.bug]

With [NEW] in green or red

Done. Updated the tag to have the red color.

@aliceinwire
Copy link
Member

@JenySadadia sounds good. The 2 issues that don't have next/master in the first incident still have incidents on the tree.
As for the NEW tag, let's add it to the beginning of the line:
[NEW] sleeping function called from invalid context at kernel/locking/rwsem.c:1589 [logspec:generic_linux_boot,linux.kernel.bug]
With [NEW] in green or red

Done. Updated the tag to have the red color.

As we are showing issues, I also think that red is better

@aliceinwire
Copy link
Member

This looks like it can be merged

@aliceinwire aliceinwire merged commit b8e8689 into kernelci:main Aug 28, 2025
5 checks passed
@JenySadadia JenySadadia deleted the restructure-issues-cmd branch August 28, 2025 04:24
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.

3 participants