Skip to main content

2021-q4

Tuning from the web app can now use shared or private batch definitions, milestones are protected from deletion, and bit-accuracy checks also compare the inputs. Batches files gained a default database and more flexible paths.

Users

Shared and private batches for tuning

When starting a tuning experiment, batches can come from the commit's batches files, from a form shared with all users, or from your own private form. The merged batch definitions are saved with the tuning batch.

Learn more →
Users

Protected milestones

Commits with milestones get a star in the commit list, and the web app disables the menus that would delete their batches, so milestone results can't be deleted by mistake.

Learn more →
Project integration

Bit-accuracy checks compare inputs

Runs now save a manifest of their input files in manifest.inputs.json, and qa check-bit-accuracy reports when the inputs differ from the reference's, not only the outputs.

Learn more →
Project integration

More flexible batches files

A batches file can set a default database for all its batches, database paths can use {project} and {subproject}, and inputs.allow_duplicate_batches lets subprojects define the same batch names.

Learn more →

Web app​

  • The diff viewer is hidden when both files are identical, and the reference video is hidden when it is the same as the new one. Video sync is less strict.
  • The commit list date range can be set in the URL with ?from=YYYY-MM-DD&to=YYYY-MM-DD, and no longer jumps around.
  • Batch logs show the ID of each command, and concatenate the commands of a tuning batch.
  • Better link to the docs.

CLI and project setup​

  • Matrix batches support indexing, like ${matrix.param[0]} or ${matrix.param[key]}.
  • The CLI shows nicer tracebacks, and better messages when runs are killed, for instance by LSF.
  • qa batch always prints the URLs of the results, and warns when batches files are empty.
  • Bit-accuracy checks handle non-default output directory names, long paths, and several reference folders with results.
  • The CLI handles network errors, not only HTTP errors.
  • The Jenkins integration no longer requires JENKINS_AUTH to be set.

Fixes​

  • Fixed qa get, including qa get output_dir.
  • Fixed imports when not running under a QA-Board project directory.
  • Fixed commit messages with two line breaks, None batches and relative database paths.
  • Fixed deleting artifacts of subprojects, and interpolating {subproject} in the web app.
  • Fixed output manifests on Windows.