Hacker News with Generative AI: Continuous Integration

Rust: Doubling Throughput with Continuous Profiling and Optimization (polarsignals.com)
“68.37% of CPU [...] with a one-line code change [...] went down to 31.82%”

Rust, Optimization, Performance, Profiling, Continuous Integration

59 points by mesto1 6 days ago | 34 comments

Prefer tee -a, not >>, in CI (huonw.github.io)
Shell scripts sometimes have to append data to a file. Redirecting output with >> is the conventional way and works fine, but using tee -a instead is a usually better default, especially in continuous integration. It’s just as easy and gives automatic introspection: the same value is printed to stdout and so appears in normal logs too.

Shell Scripting, Continuous Integration, DevOps, Software Development, Best Practices

4 points by dbaupp 8 days ago | 0 comments

Compiler Fuzzing in Continuous Integration: A Case Study on Dafny [pdf] (ic.ac.uk)

Compiler Fuzzing, Continuous Integration, Software Testing, Programming Languages, Case Studies

42 points by matt_d 31 days ago | 2 comments

Mastodon Server for Apache NuttX Continuous Integration (macOS Rancher Desktop) (lupyuen.org)
We’re out for an overnight hike, city to airport. Our Build Farm for Apache NuttX RTOS runs non-stop all day, all night. Continuously compiling over 1,000 NuttX Targets: Arm, RISC-V, Xtensa, x64, …

Continuous Integration, Operating Systems, Embedded Systems, macOS

7 points by lupyuen 54 days ago | 0 comments

Faster CI with Selective Testing (mill-build.org)
Selective testing is a key technique necessary for working with any large codebase or monorepo: picking which tests to run to validate a change or pull-request, because running every test every time is costly and slow. This blog post will explore what selective testing is all about, the different approaches you can take with selective testing, based on my experience working on developer tooling and CI for the last decade at Dropbox and Databricks.

Continuous Integration, Software Testing, Software Development, CI/CD, Large Codebases

45 points by lihaoyi 56 days ago | 49 comments

Faster continuous integration builds at Canva (canva.dev)
In April 2022, the average time for a pull request (PR) to pass continuous integration (CI) and merge into our main branch was around 80 minutes.

Continuous Integration, Software Development, Engineering, Canva

21 points by SerCe 66 days ago | 6 comments

Continuous Integration Dashboard for Apache NuttX RTOS (Prometheus and Grafana) (lupyuen.github.io)
Last article we spoke about the (Twice) Daily Builds for Apache NuttX RTOS…

Continuous Integration, Apache NuttX, RTOS, Prometheus, Grafana

74 points by lupyuen 89 days ago | 2 comments

CodSpeed – integrated CI tool for performance testing (codspeed.io)
Backed by<h1>Unmatched performance testing in your CI</h1><p>Measure and optimize software performance consistently and before any release to avoid production issues, improve UX and save on infrastructure costs.</p>

Software Development, Performance Testing, Continuous Integration, CI/CD, DevOps

22 points by microflash 112 days ago | 5 comments

Working with Igalia to Improve RISC-V LLVM Continuous Integration (riseproject.dev)
The LLVM project provides a very widely used and actively developed suite of compiler and toolchain technologies: including Clang, the LLVM middle-end optimizer and backend code generator, MLIR, LLD linker, and much more. While RISC-V LLVM support has progressed significantly, a key area that needed attention was the limited level of continuous integration (CI) for the RISC-V target.

RISC-V, LLVM, Software, Open Source, Continuous Integration

30 points by thebeardisred 119 days ago | 7 comments

Your CI pipeline isn't ready for AI (morgante.net)
In developing my AI codegen agent, I’ve surprisingly been far more frustrated by CI/testing systems than any unreliable LLM API.

Artificial Intelligence, Software Development, Continuous Integration, Testing

27 points by morgante 135 days ago | 15 comments

The Many SHAs of a GitHub Pull Request (kenmuse.com)
Many people don’t realize it, but pull requests actually have multiple “identities” when an Action workflow runs. There are actually multiple SHAs that represent different parts of the lifecycle during a continuous integration build. This can be confusing for teams that are trying to implement advanced processes, and it often lead to mistakes. In some cases, it leads to a misunderstanding – thinking that the build is testing the branch itself instead of a simulated merge to the target branch.

GitHub, Continuous Integration, Software Development, Version Control

52 points by yamrzou 168 days ago | 7 comments

We managed to speed up our CI to save 168 days of execution time per month (home-assistant.io)