# Why so many libraries on github say that their builds are failing?

**URL:** <https://discourse.julialang.org/t/why-so-many-libraries-on-github-say-that-their-builds-are-failing/111027>\
**Category:** General Usage\
**Created:** [March 1, 2024, 6:23pm UTC](https://discourse.julialang.org/t/why-so-many-libraries-on-github-say-that-their-builds-are-failing/111027 "2024-03-01T18:23:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Veenty](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/veenty/32/50940_2.png) [@Veenty](https://discourse.julialang.org/u/Veenty)\
**Post date:** [March 1, 2024, 6:23pm UTC](https://discourse.julialang.org/t/why-so-many-libraries-on-github-say-that-their-builds-are-failing/111027/1 "2024-03-01T18:23:37Z")

</div>

This has been going on more months and I’m not sure why.  
Like even the official one say this.

> **[GitHub - SciML/DiffEqDocs.jl: Documentation for the DiffEq differential...](https://github.com/SciML/DiffEqDocs.jl)**
>
> Documentation for the DiffEq differential equations and scientific machine learning (SciML) ecosystem - SciML/DiffEqDocs.jl

> **[GitHub - JuliaLang/julia: The Julia Programming Language](https://github.com/JuliaLang/julia)**
>
> The Julia Programming Language. Contribute to JuliaLang/julia development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)\
**Post date:** [March 1, 2024, 7:34pm UTC](https://discourse.julialang.org/t/why-so-many-libraries-on-github-say-that-their-builds-are-failing/111027/2 "2024-03-01T19:34:59Z")

</div>

The answer will be different for each and every repository. Some answers might include:

- The badges often reflect the state of the tip of the dev branch — and not the release branch. Sometimes dev test suites fail more frequently than ones targeted for release.
- Test suites often encapsulate _many_ configurations, and it only takes one to fail for the summary to be a big red box. Sometimes these failing configurations aren’t necessarily problematic, but they’re sometimes not marked optional.
- Test suites sometimes fail for very mundane reasons — like HTTP connectivity or timeouts.
- Thorough test suites sometimes trip over sporadic and hard-to-nail down bugs that aren’t easily reproducible. These take time and often significant effort to find and fix.
- Sometimes the problem is in the testing infrastructure itself, and has nothing to do with the particular repository’s code.

In the specific case of Julia itself, you can [click the badge](https://buildkite.com/julialang/julia-master) to see what happened for the most recent build. The most recent pipeline (as of this comment, build 34231) did fail. The tests used nearly 22 hours worth of computer time. You can see that currently Julia is built and tested across 13 different configurations of macOS, Windows, Linux, and FreeBSD, with an additional 9 code quality kinds of checks. Some of those configurations are works-in-progress — those are the ones allowed to fail so if/when they fail, it doesn’t count as a “failing build.” (These configurations are all [Support Tier 2 or 3](https://julialang.org/downloads/#support_tiers_for_the_latest_stable_release_of_julia)). I only list this all out here because I think it’s helpful to see the scope of what’s behind the green- or red- ![image](https://global.discourse-cdn.com/julialang/original/3X/f/f/ff559693fd44c447317099da1d33590fe01c5259.png).

In this particular pipeline, one required configuration did fail — the x86-64 windows build failed. That’s why the box is red. Why did that fail? The logs report that it “Received cancellation signal, interrupting.” Why did that happen? 🤷 I have no idea, but if you’re interested in supporting and improving the testing and testing infrastructure, you can join the Continuous Integration working group: [Working Groups](https://julialang.org/community/working-groups/#list_of_working_groups). As you might imagine, this all reflects a good amount of effort!