Skip to content

CI

CI #110

Triggered via schedule June 1, 2024 02:21
Status Failure
Total duration 58s
Artifacts

ci.yml

on: schedule
Matrix: Molecule
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 10 warnings
Molecule (rockylinux9)
Process completed with exit code 2.
Molecule (fedora39)
The job was canceled because "rockylinux9" failed.
Molecule (fedora39)
Process completed with exit code 2.
Molecule (rockylinux8)
The job was canceled because "rockylinux9" failed.
Molecule (rockylinux8)
Process completed with exit code 2.
Molecule (fedora38)
The job was canceled because "rockylinux9" failed.
Molecule (fedora38)
Process completed with exit code 2.
name[template]: tasks/reposync_removal.yml#L5
Jinja templates should only be at the end of 'name'
name[template]: tasks/reposync_removal.yml#L9
Jinja templates should only be at the end of 'name'
name[template]: tasks/reposync_removal.yml#L21
Jinja templates should only be at the end of 'name'
name[template]: tasks/reposync_removal.yml#L33
Jinja templates should only be at the end of 'name'
name[template]: tasks/reposync_service.yml#L5
Jinja templates should only be at the end of 'name'
name[template]: tasks/reposync_service.yml#L9
Jinja templates should only be at the end of 'name'
name[template]: tasks/reposync_service.yml#L17
Jinja templates should only be at the end of 'name'
name[template]: tasks/reposync_service.yml#L26
Jinja templates should only be at the end of 'name'
name[template]: tasks/reposync_service.yml#L36
Jinja templates should only be at the end of 'name'
name[template]: tasks/reposync_timer.yml#L5
Jinja templates should only be at the end of 'name'