Skip to content

feat(api): wire per-tab lab filters and metrics lab health (#2059) - #2107

Open
alanpeixinho wants to merge 1 commit into
kernelci:mainfrom
profusion:feat/2059-api-lab-filters-metrics
Open

alanpeixinho wants to merge 1 commit into
kernelci:mainfrom
profusion:feat/2059-api-lab-filters-metrics

Conversation

@alanpeixinho

Copy link
Copy Markdown
Contributor

What it is

Closes #2059. Per-tab lab filters for tree and hardware APIs (filter_test.lab, filter_boot.lab, filter_build.lab), including hardware POST filter bodies. /api/metrics/ lab_maps now exposes per-lab StatusCount for builds, boots, and tests, plus covered_builds for the email “Covered builds” column. Covered-builds SQL uses nested GROUP BY lab, build_id.

What to test

  • Tree boots / tests / builds: filter_boot.lab, filter_test.lab, filter_build.lab (query + POST where supported); builds filter on build lab, not test lab
  • Hardware boots / tests / builds / summary: POST filter with per-tab lab keys; lab + status together
  • GET /api/metrics/: response includes new covered_builds on each lab entry, and builds / boots / tests as StatusCount objects (not plain ints)
  • Metrics page and metrics_summary email: “Covered builds” totals and per-lab values match pre-change behaviour; boots/tests columns unchanged
  • UI filters: test.lab and boot.lab still work; builds tab not lab-filtered via UI (by design)

Made with Cursor

…2059)

* filter_test.lab, filter_boot.lab, and filter_build.lab handlers with per-tab filter_labs
* Lab filtering on tree, hardware, rollup, and commits history listings
* Hardware POST filter body support for lab per boot/test/build tab
* lab_maps builds/boots/tests as StatusCount on /api/metrics/
* covered_builds int on LabMetricsData
* Faster covered-builds SQL via nested GROUP BY lab, build_id
* Metrics email template, Metrics page, and frontend filter types updates
* Unit tests for filters, metrics queries, notifications, and rollup

Signed-off-by: Alan Peixinho <alan.peixinho@profusion.mobi>
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.

API improvements for MCP

1 participant