The screentest "module-with-one-vuln" is currently failing at tip, as seen in the most recent trybot occurrence in CL 598524.
This test case was very recently fixed in CL 598035 (CC @tatianab), reflecting that it's no longer the latest published version of the module, but it seems it broke quite quickly since then. In the updated image, the screenshot's badge said "Main | passing" which matches https://pkg.go.dev/github.com/stacklok/minder@v0.0.47 now but might not whenever that project's main branch has a problem. The coverage percentage badge changed from 53% to 54% and members badge text went 134 → 133, contributing to the overall visual diff.
The main source of flakiness in this test case seems that the badges in the README change whenever the tip version of the minder module changes, causing visual diffs.
The screentest "module-with-one-vuln" is currently failing at tip, as seen in the most recent trybot occurrence in CL 598524.
This test case was very recently fixed in CL 598035 (CC @tatianab), reflecting that it's no longer the latest published version of the module, but it seems it broke quite quickly since then. In the updated image, the screenshot's badge said "Main | passing" which matches https://pkg.go.dev/github.com/stacklok/minder@v0.0.47 now but might not whenever that project's main branch has a problem. The coverage percentage badge changed from 53% to 54% and members badge text went 134 → 133, contributing to the overall visual diff.
The main source of flakiness in this test case seems that the badges in the README change whenever the tip version of the minder module changes, causing visual diffs.
CC @golang/pkgsite.