How do you diagnose slow CI here? #256
Closed
djaiswal12
started this conversation in
General
Replies: 1 comment
|
I would suggest asking in the Zephyr Project instead, as CANnectivity is really just piggybacking on the build environment of Zephyr: https://github.com/zephyrproject-rtos/zephyr/ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I've been looking at cross-platform CMake projects to understand how maintainers debug build time, and cannectivity has more CI surface than most; 4 workflows across Linux + Windows + Macos.
When a build gets noticeably slower, how do you work out which target is responsible? Do you dig into the Ninja log or CMake timings, or mostly go by feel and bisect?
Asking because I keep hitting this on my own native projects and I'm trying to figure out if there's a better way people have landed on. Happy to share what I learn across the projects I'm looking at.
All reactions