# flaky tests Published articles for flaky tests. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Your Donations at Work: One Year of Sponsored Servo Development DevFeed: [Your Donations at Work: One Year of Sponsored Servo Development]() Original publisher: [Read original article]() Author: The Servo Project Developers Published: 2026-09-15T00:00:00Z Content type: article Language: en Sources: [Servo Blog]() Topics: [servo](), [Maintainers](), [pull-requests](), [Development]() Tags: [contributions](), [development](), [documentation](), [flaky-tests](), [maintainers](), [pull-requests](), [rust](), [servo](), [servo-engine](), [servo-rendering-engine](), [sponsored](), [web-browser](), [web-browser-engine](), [web-engine](), [web-rendering-engine]() ### AI overview A Servo maintainer reviews a year of part-time work funded by monthly donations, including nominating new maintainers, reviewing pull requests, filing contributor-focused issues, writing documentation, improving flaky tests, and supporting JavaScript engine integration work. ### Source excerpt Last September, the Servo project announced that long-time maintainer Josh Bowman-Matthews (@jdm) would work part-time on improving the Servo contributor experience, entirely funded by the monthly donations on OpenCollective and GitHub. In his own words, here is a look back over the past year! First of all, I am enormously grateful to everyone who financially supports Servo, as those donations have enabled me to devote significant time to a project that I care a lot about. Some highlights from that funded work that I'm proud of: I nominated 8 new maintainers I reviewed 1150 pull requests I filed 114 issues targeted at newer contributors (92% of them have been fixed) I wrote new documentation about borrow hazards, experimental features, the AI policy, finding things to do, and fixing stable and intermittent test failures On top of that, I spent time diagnosing unexpected failures in others' PRs and fixed numerous intermittent test failures that made merging PRs more difficult for everyone. A few pieces of work from this period that stand out to me: supporting a large scale rewrite of Servo's JS engine integration to address intermittent panics related to garbage collection--I reviewed lots of pull requests, but also filed many issues that enabled the work addressing the panics to be spread across many other contributors getting tagged in to help understand test failures, uncovering our broken window.open behaviour, and eventually making a lot of flaky tests more stable supporting another contributor's grant proposal to work on Servo that was approved! This role I've carved out means a lot to me--I've found a healthy balance that allows me to spend time with my family as well as make meaningful contributions to Servo, and I get to spend a lot of time looking for ways to make the project more accessible for others. A big thank you to everybody supporting the project and my work; each individual monthly donation makes a big difference! I'm excited to see what's possible i ## Lessons Learned from Fixing Flaky Tests with Claude DevFeed: [Lessons Learned from Fixing Flaky Tests with Claude]() Original publisher: [Read original article]() Author: Henrik Warne Published: 2026-08-15T15:50:33Z Content type: article Language: en Sources: [Henrik Warne]() Topics: [Claude](), [Testing]() Tags: [claude](), [flaky-tests](), [integration](), [learning](), [llm](), [net-9](), [parallel](), [programming](), [running](), [testing](), [tests]() ### AI overview The article describes lessons learned from using Claude to diagnose and fix flaky integration tests after parallelizing a test suite. It explains that blindly accepting plausible fixes was ineffective, while understanding and reviewing each change was important. ### Source excerpt We recently sped up our integration tests by a factor of ten by running many of them in parallel. There were several flaky tests in the new test suite. Claude was really useful in getting rid of almost all flakyness, ... Continue reading -> ## Test & Set DevFeed: [Test & Set]() Original publisher: [Read original article]() Author: Jesse Wilson Published: 2026-07-13T22:22:27Z Content type: tutorial Language: en Sources: [Public Object]() Topics: [Concurrency](), [Concurrent Programming](), [Code](), [function](), [business logic]() Tags: [business-logic](), [code](), [concurrency](), [flaky-tests](), [function](), [programming](), [tests](), [threads]() ### AI overview An article about managing concurrency in threaded programs. It discusses the limits of simple and stress tests, describes a trusted concurrency pattern, and presents a helper function that separates business logic from concurrency logic while retrying after a lost race. ### Source excerpt Working with threads always feels hazardous to me. Non-determinism limits how much we can exercise with simple tests. Stress tests can shake out some bugs, but they're slow and potentially flaky. I don't like flaky tests. So I have a few concurrency patterns that I trust, and I ## Evolution of Developer Productivity at Square - Part Four DevFeed: [Evolution of Developer Productivity at Square - Part Four]() Original publisher: [Read original article]() Author: Korhan Bircan Published: 2024-02-26T17:00:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [code productivity](), [Testing](), [Test automation](), [release engineering](), [Mobile]() Tags: [crash-reporting](), [developer](), [engineering](), [flaky-tests](), [mobile](), [mobile-performance](), [operational](), [release-engineering]() ### AI overview The fourth and final part of Square's developer productivity series describes its shift toward reliability and test engineering as its codebase and customer base grew. It covers reliability reviews, service-level objectives, performance-focused task forces, mobile release engineering, automated crash reporting, and efforts to improve testing infrastructure and flaky tests. ### Source excerpt Investing in reliability and test engineering