Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unparsed warnings and errors #295

Open
nickdesaulniers opened this issue Feb 2, 2022 · 1 comment
Open

unparsed warnings and errors #295

nickdesaulniers opened this issue Feb 2, 2022 · 1 comment

Comments

@nickdesaulniers
Copy link

Given a link to a report, such as https://linux.kernelci.org/build/android/branch/android12-5.10/kernel/ASB-2022-01-05_12-5.10-22-ga32e89883a53/:

(under the Errors tab, the default in the above link):
ixp4xx_defconfig, and pxa_defconfig are red, yet have no errors or warnings, yet are red. Does that signify a boot error then? The warning logs for ixp4xx_defconfig aren't empty, so maybe it's an issue parsing warnings from the assembler? Same for the error log.

@gctucker
Copy link
Contributor

gctucker commented Feb 2, 2022

These are builds that failed because make returned a non-zero status. There's no errors shown because the logs were not parsed correctly. So it's not an issue with the frontend but with the logic in the backend to match errors. It hasn't been updated in years while compilers have evolved and we're running LLVM/Clang builds now. Also, yes maybe it's not matching assembler warnings and errors.

I'll move this issue to kernelci-backend as that's where the problem currently lies.

@gctucker gctucker transferred this issue from kernelci/kernelci-frontend Feb 2, 2022
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

No branches or pull requests

2 participants