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
Over the last year, we have had vastly improved our continuous integration due to the move from Travis CI to TuxSuite + GitHub Actions as well as reaching out to other continuous integration platforms such as Red Hat's Continuous Kernel Integration (CKI).
This talk aims to outline the improved coverage such as:
generator.yml / check_logs.py / generate_*.py
Coverage of allmodconfig / allyesconfig
Coverage of clang-10 through clang-14
Coverage of sanitizers
Coverage of distribution configurations
The talk will discuss some of the pain points of maintaining a continuous integration setup and see if there are ways to improve this:
Making failure reasons more obvious
Applying patches to help failing builds
Automatically filing issues (or sending emails?)
Making issues more reproducible
Estimated duration of talk
30-45 minutes between presentation and potential discussion.
The text was updated successfully, but these errors were encountered:
Title
ClangBuiltLinux Continuous Integration: Review and Look Ahead
Author
Nathan Chancellor <[email protected]>
Abstract
Over the last year, we have had vastly improved our continuous integration due to the move from Travis CI to TuxSuite + GitHub Actions as well as reaching out to other continuous integration platforms such as Red Hat's Continuous Kernel Integration (CKI).
This talk aims to outline the improved coverage such as:
generator.yml
/check_logs.py
/generate_*.py
allmodconfig
/allyesconfig
clang-10
throughclang-14
The talk will discuss some of the pain points of maintaining a continuous integration setup and see if there are ways to improve this:
Estimated duration of talk
30-45 minutes between presentation and potential discussion.
The text was updated successfully, but these errors were encountered: