Current status of allyesconfig and allmodconfig #839
Labels
[CONFIG] allmodconfig
Issue affects allmodconfig on certain architectures
[CONFIG] allyesconfig
Issue affects allyesconfig on certain architectures
I have decided to create this issue to track other various issues that prevent us from fully building an
allyesconfig
orallmodconfig
build for certain architectures.I think that getting some visibility on these and trying to get them addressed is important for trying to get more people involved with the project because a lot of people experiment with this through building their distribution's kernel, which will be much closer to
allmodconfig
thandefconfig
.We do not have much visibility into these results aside from the reports that are sent to our mailing list from KernelCI (and it appears that they stopped doing clang builds?) because Travis won't be able to handle that kind of workload and I don't know of anyone else doing this kind of testing publicly.
Currently with
clang
at llvm/llvm-project@995c18f...arm32 results
allmodconfig
LD=ld.lld allmodconfig
allyesconfig
LD=ld.lld allyesconfig
arm64 results
allmodconfig
LD=ld.lld allmodconfig
allyesconfig
LD=ld.lld allyesconfig
x86_64 results
allmodconfig
LD=ld.lld allmodconfig
allyesconfig
LD=ld.lld allyesconfig
This is the script that I wrote to generate these results
I do these builds every day but I think doing a build every Sunday (when the new RC hits) and reporting the results here would be kind of nice.
The text was updated successfully, but these errors were encountered: