Make sure ":reliable" tests on GDK are actually stable
As in the previous issue (#1657 (closed)), we should make sure that the tests run reliably against GDK, at least as well as they run in other environments/pipelines.
Investigate each failure in the e2e-test-on-gdk
reliable pipeline in the last 15 days and
-
Check if the failure is unique to the GDK environment [last 15 days] -
Check if failure is consistent with package-and-test
environment [last 15 days] -
Add test failure reporting to reliable
job in schedule pipelines -
Enable GDK reliable
job asblocking MRs
for only a subset of MRs (perhaps start with groupthreat insights ) -
Test that fast quarantine works in MR GDK pipeline.
Goal
Achieve as close to a green dashboard as possible in: https://dashboards.quality.gitlab.net/d/bfc1cd97-97ef-4651-9d23-f063f05f9ae3/jobs-by-run-type?orgId=1&refresh=5m&var-run_type=e2e-test-on-gdk&var-job_name=All&from=now-30d&to=now
Edited by Harsha Muralidhar