You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are facing a few problems that some maestro results are not reaching KCIDB for some reason.
I was discussing with @nuclearcat about this and he suggested we create a script to monitor KCIDB and check that everything landed and resend what didn't land.
You can also check other points in history and for the other days it seems things went fine (you can select the commit by clicking on a dot of this chart):
The kernelci job for my tree builds, but didn't boot or run any tests.
The email reports 8 builds, but the dashboard has 1 with no details:
https://dashboard.kernelci.org/tree/adf5063ed0f406c78322f9740dcdea3036248282?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%2Frobh%2Flinux.git%22%2C%22gitBranch%22%3A%22for-kernelci%22%2C%22treeName%22%3A%22robh%22%2C%22commitName%22%3A%22v6.12-rc1-1-gadf5063ed0f4%22%2C%22headCommitHash%22%3A%22adf5063ed0f406c78322f9740dcdea3036248282%22%7D
Here's the email for the build (note the links are broken):
robh/for-kernelci build: 8 builds: 0 failed, 8 passed, 23 warnings (v6.12-rc1-1-gadf5063ed0f40)
Full Build Summary: https://kernelci.org/build/robh/branch/for-kernelci/kernel/v6.12-rc1-1-gadf5063ed0f40/
Tree: robh
Branch: for-kernelci
Git Describe: v6.12-rc1-1-gadf5063ed0f40
Git Commit: adf5063ed0f406c78322f9740dcdea3036248282
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git
Built: 8 unique architectures
Warnings Detected:
arc:
haps_hs_smp_defconfig (gcc-12): 2 warnings
arm64:
arm:
i386:
mips:
32r2el_defconfig (gcc-12): 3 warnings
riscv:
sparc:
sparc64_defconfig (gcc-12): 18 warnings
x86_64:
The text was updated successfully, but these errors were encountered: