Skip to content

automation/eclair: do not allow failure for triggered analyses

Federico Serafini xen-devel 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 9 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3automation/eclair: tag Rule 7.2 as clean and temporarily remove Rules 1.1 and 8.2automation/eclair_analysis/ECLAIR/tagging.ecl+1 -11 reply
2/3automation: do not allow failure for triggered analysesautomation/gitlab-ci/analyze.yaml+0 -11 reply
3/3automation/eclair: make explicit there are no adopted files by defaultautomation/eclair_analysis/ECLAIR/analysis.ecl+4 -01 reply

Reviews trailers per patch

All 3 patches have a Reviewed-by or Acked-by.

PatchStefano Stabellini
1/3A-b
2/3A-b
3/3A-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [XEN PATCH 0/3] automation/eclair: do not allow failure for triggered analyses

Patch 1/3 does some preparation work.

Patch 2/3, as the title says, removes allow_failure = true for triggered analyses.

Patch 3/3 makes explicit that initally no files are tagged as adopted, this is needed by the scheduled analysis.

Federico Serafini (3):
automation/eclair: tag Rule 7.2 as clean and temporarily remove Rules

    1.1 and 8.2

automation: do not allow failure for triggered analyses automation/eclair: make explicit there are no adopted files by default

 automation/eclair_analysis/ECLAIR/analysis.ecl | 4 ++++
 automation/eclair_analysis/ECLAIR/tagging.ecl  | 2 +-
 automation/gitlab-ci/analyze.yaml              | 1 -
 3 files changed, 5 insertions(+), 2 deletions(-)
Signature · 1 line
2.34.1