Skip to content

Fix: path search on treeDetails#1878

Open
MarceloRobert wants to merge 2 commits intokernelci:mainfrom
MarceloRobert:fix/test-path-filter
Open

Fix: path search on treeDetails#1878
MarceloRobert wants to merge 2 commits intokernelci:mainfrom
MarceloRobert:fix/test-path-filter

Conversation

@MarceloRobert
Copy link
Copy Markdown
Collaborator

@MarceloRobert MarceloRobert commented Apr 24, 2026

Fixes an issue where a path filter would make the rollup rows filter the entire path group instead of only filtering individual tests. For the solution, legacy rows have to be used since the aggregated rows don't have information about individual tests. We opted for a solution where the test path filter only applies to the table in the frontend, without making changes in the backend so that we don't fallback to the legacy query and the path filtering becomes faster too.

The tests were being filtered correctly, but the summary was returning empty and was causing all the frontend components to be replaced with a "no data" too.

Changes

  • Removed test path and boot path from the mapping that ultimately goes to the backend request
  • Altered the frontend testsTable and bootsTable so that they use the table state for the path filtering

Since these changes are in the core component, they work in the treeDetails page, hardwareDetails page, and buildDetails page (that has a testTable).

How to test

Check any treeDetails page and try applying a test or boot path filter that only works on a subset of a group (ex "nfs" for "boot.nfs" or "setup" for "tast.setup"). Then compare with the production state.

Closes #1872

@MarceloRobert MarceloRobert self-assigned this Apr 24, 2026
@MarceloRobert MarceloRobert added bug Something isn't working Backend Most or all of the changes for this issue will be in the backend code. labels Apr 24, 2026
@MarceloRobert MarceloRobert marked this pull request as draft April 27, 2026 13:55
@MarceloRobert
Copy link
Copy Markdown
Collaborator Author

Moved to draft because we discussed about changing the behavior of the filter to not apply the path filter on the summary endpoint, which won't lose a lot of functionality while increasing the performance massively

change test path filter to be frontend-only

Closes kernelci#1872
@MarceloRobert MarceloRobert marked this pull request as ready for review April 27, 2026 19:21
Adds a fallback to the legacy query if an user accesses the summary endpoint with a path filter, even if the frontend doesn't access it anymore
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Backend Most or all of the changes for this issue will be in the backend code. bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

String based searches for issues aren't substring based

1 participant