Skip to main content

2025-04

You can find a run by its ID in the commit page's search box, and qa batch now stops before flooding QA-Board with more than 1,000 runs at once.

Users

Search runs by ID

Type id:1234 in the commit page's filter box to show only the run with that ID, for instance when a colleague or a log gives you a run ID.

Project integration

A limit of 1,000 runs per qa batch

qa batch now fails when it would send more than 1,000 runs at once, which is usually a mistake in a batch definition. Set QA_BATCH_ALLOW_MANY_RUNS=1 when you really need more, or use qa --offline batch to run without reporting to QA-Board.

Learn more →

Server and administration​

  • The server updates the "latest results" time of commits and projects at most every few seconds, which avoids database lock contention when many runs report their results together.

Fixes​

  • qa run no longer crashes when writing the outputs manifest fails, it only warns.
  • Fixed qa optimize crashing when it sets QA_OPTIM_DIR.