174bf521

Report each suppression in an unread file, not the file

A suppression in a file no rule is ever run over was one complaint per file,
pointing at line one. What somebody has to go and remove is a comment, so a
comment is what the report has to point at, and two suppressions in one such
file are two things to remove rather than one.

The scan now answers with a span per suppression. It asks meansToBeOne itself
rather than matching the same markers a second time, which also means a line
that mentions an allowlist before writing a real suppression is read the way the
parser would read it.

Agent Instructions

Each run corresponds to one flake attribute. Click a run for its logs and status.

Example: https://staging.nix-ci.com/gh:NorfairKing:hopinion/master/174bf521bc367fc877d7e4aec6303721b014d298/46051f9b-543b-48c5-8cfb-79e341bf2682

Wait for suite to complete:

curl --netrc -N https://staging.nix-ci.com/gh:NorfairKing:hopinion/master/174bf521bc367fc877d7e4aec6303721b014d298/wait

This page is also available in machine-friendly formats. Request one with the Accept header:

• curl --netrc -H 'Accept: application/json' https://staging.nix-ci.com/gh:NorfairKing:hopinion/master/174bf521bc367fc877d7e4aec6303721b014d298
• curl --netrc -H 'Accept: text/markdown' https://staging.nix-ci.com/gh:NorfairKing:hopinion/master/174bf521bc367fc877d7e4aec6303721b014d298

For more instructions, fetch https://staging.nix-ci.com/instructions .