Descriptions, all tabs use tests counts, and all tests needs a join with builds, and all builds
-- This but good
select * from (select * from checkouts where (origin, branch, commithash) ) as checkouts
left join
builds
checkout.id = builds.checkout_id (don't forget to get the start time for the optimized where here)
left join
tests on
builds.id = tests.build_id
And then in a syngle python loop
feed the hashtables that will compose the data presented in the view
Descriptions, all tabs use tests counts, and all tests needs a join with builds, and all builds
And then in a syngle python loop feed the hashtables that will compose the data presented in the view
use hashtables
Good test cases
linux-next on search https://staging.dashboard.kernelci.org:9000/tree/d05eb7a8dbd3854a4a21f2e62ff91251466abab4?tableFilter=%7B%22bootsTable%22%3A%22all%22%2C%22buildsTable%22%3A%22all%22%2C%22testsTable%22%3A%22all%22%7D&origin=maestro¤tTreeDetailsTab=treeDetails.builds&diffFilter=%7B%7D&treeInfo=%7B%22gitUrl%22%3A%22https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Fnext%2Flinux-next.git%22%2C%22gitBranch%22%3A%22pending-fixes%22%2C%22treeName%22%3A%22next%22%2C%22commitName%22%3A%22v6.11-rc7-63-gd05eb7a8dbd3%22%2C%22headCommitHash%22%3A%22d05eb7a8dbd3854a4a21f2e62ff91251466abab4%22%7D
broonies origin on maestro is also good