SShortSingh.
Back to feed

Engineer tests six LLM eval frameworks in CI merge queue; only two proved reliable

0
·1 views

A software engineer ran six open-source LLM evaluation frameworks inside a real GitHub Actions merge queue over eight months, testing them against production pull requests. The core criterion was determinism: a gate had to return the same pass or fail verdict on unchanged inputs every single time. Frameworks relying heavily on LLM-as-judge scoring failed this test, as judge-assigned scores drifted between runs without any code changes, causing false blocks and eroding team trust in the gate. Promptfoo and DeepEval were the only two frameworks that consistently met the bar, largely because they kept deterministic checks in the blocking path and treated judge scores as non-blocking signals. The author concludes that a flaky CI gate is worse than no gate, since teams learn to bypass it, rendering it meaningless.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingHacker News ·

Kontigo, YC S24 Startup, Seeks Head of Security

Kontigo, a startup that participated in Y Combinator's Summer 2024 batch, is currently hiring for a Head of Security role. The job listing was posted on Y Combinator's company job board. No further details about the position's requirements or compensation were included in the announcement. The posting received no points or comments on Hacker News at the time of publication.

0
ProgrammingDEV Community ·

CS Undergrad Builds Production-Grade Distributed API Gateway From Scratch

A computer science undergraduate has developed a fully functional, production-grade API gateway built on Node.js, featuring reverse proxy routing to multiple microservices and per-client rate limiting using a Redis token-bucket algorithm. The system enforces JWT authentication at the gateway level and handles asynchronous request logging through BullMQ worker queues connected to a MongoDB database. Live traffic metrics are streamed to a React dashboard via Socket.io, displaying data such as total requests, requests per minute, average response time, and error rate. The project was built in seven phases, progressing from basic reverse proxy setup through authentication, rate limiting, async analytics, and a real-time frontend. The developer has published the project on GitHub and is seeking community feedback on the queue worker design and rate limiting strategy.

0
ProgrammingDEV Community ·

DEV Summer Bug Smash Offers $500 Sentry Prize for Best App Performance Fix

DEV has launched its Big Summer Bug Smash, a community event focused on fixing bugs and improving performance in existing software projects. A dedicated 'Best Use of Sentry' prize category rewards participants who use Sentry's error-monitoring tools to enhance their applications. Three winners in this category will each receive $500, a limited-edition Sentry skateboard, and an exclusive winner badge. For developers new to Sentry, a live demo and Q&A session is scheduled for July 30 at 11am PT on the DEV homepage and YouTube. Attendees can submit questions in advance via the comments section of the official post.

0
ProgrammingDEV Community ·

Why Rust enforces one writer and many readers to prevent memory bugs

Rust enforces a principle called Aliasing XOR Mutation, meaning a piece of data can either have multiple readers or one writer at any given time, but never both simultaneously. This rule is checked at compile time, preventing entire classes of memory safety bugs before a program ever runs. In languages like C and C++, combining aliasing and mutation freely leads to serious issues such as data races, where two threads overwrite each other's changes to shared memory, and iterator invalidation, where a pointer references memory that has already been moved or deleted. Researchers studying such crashes over decades found that aliasing alone and mutation alone are each harmless — it is only their combination that causes problems. Rust's creator Graydon Hoare built this constraint into the language's core design to make memory-safe systems programming possible without a garbage collector.

Engineer tests six LLM eval frameworks in CI merge queue; only two proved reliable · ShortSingh