惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

GbyAI
GbyAI
Y
Y Combinator Blog
Martin Fowler
Martin Fowler
D
Docker
N
Netflix TechBlog - Medium
酷 壳 – CoolShell
酷 壳 – CoolShell
WordPress大学
WordPress大学
L
LangChain Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
博客园 - 三生石上(FineUI控件)
博客园_首页
量子位
罗磊的独立博客
Blog — PlanetScale
Blog — PlanetScale
云风的 BLOG
云风的 BLOG
Microsoft Azure Blog
Microsoft Azure Blog
宝玉的分享
宝玉的分享
Apple Machine Learning Research
Apple Machine Learning Research
D
DataBreaches.Net
I
InfoQ
Engineering at Meta
Engineering at Meta
The Cloudflare Blog
H
Help Net Security
V
V2EX

LWN.net comments

tcmalloc's weird hack [LWN.net] Fixed? [LWN.net] mpd [LWN.net] Userspace AX.25 [LWN.net] RIP [LWN.net] My two cents... [LWN.net] pipx [LWN.net] Tragedy [LWN.net] A young man destined for glory [LWN.net] And 'less' won't let you search [LWN.net] A great loss [LWN.net] Sad and shocking news [LWN.net] Easy migration from Clementine [LWN.net] Sad coincidence [LWN.net] GNOME is actually usable thanks to Seth et al [LWN.net] Sad news :( [LWN.net] armhf supports preempt_rt [LWN.net] MusicBrainz accurracy [LWN.net] On open source maintainership [LWN.net] Let's stop here [LWN.net] Not a new thing [LWN.net] uv is indeed great pgmoneta Some comments on this on a Postgres blog feed [LWN.net] uv [LWN.net] going to Debian [LWN.net] Upgrading 64-bit-capable systems to 64-bit kernels? [LWN.net] Free Software foundations Maintainers can wait for code review but not for publish review? A reasonably extreme point of view [LWN.net]
Things to watch for in LLM-authored changes [LWN.net]
farnz · 2026-05-29 · via LWN.net comments

Things to watch for in LLM-authored changes

Posted May 28, 2026 18:54 UTC (Thu) by farnz (subscriber, #17727)
In reply to: Editing session recording as a throttling mechanism by kleptog
Parent article: Arias: Human proof for FOSS contributions

One nasty thing I've caught reviewing LLM-authored changes (in a Rust codebase at work) is the LLM adding #[ignore] to existing tests (and obfuscating it if you tell it not to do that, via things like #[cfg_attr], comment markers or if false), or even deleting them outright, while adding a decent number of new tests that make sense.

If you don't spot what it's done to your test suite, you get surprised because the patched code compiles and passes all tests, and yet some of the things you "know" you test don't work.

I'd expect this to be even worse for the kernel, where tests are often wrong if they exist at all, and so an LLM producing a plausible comment explaining why the test is bad will result in someone accepting the removal at face value.