Skip to content
Gate

update meaning of the "automated" status in control files #11921

Sign in to view logs

update meaning of the "automated" status in control files

update meaning of the "automated" status in control files #11921

Triggered via pull request March 4, 2024 14:16
@vojtapolasekvojtapolasek
opened #11646
vojtapolasek:update_automated_requirement_doc
Status Success
Total duration 43m 20s
Artifacts –

gate.yaml

on: pull_request
Build, Test on CentOS 7 (Container)
6m 4s
Build, Test on CentOS 7 (Container)
Build, Test on SLE 15 (Container)
43m 9s
Build, Test on SLE 15 (Container)
Build, Test on OpenSUSE Leap 15 (Container)
7m 5s
Build, Test on OpenSUSE Leap 15 (Container)
Build, Test on Debian 10 (Container)
3m 8s
Build, Test on Debian 10 (Container)
Build, Test on Ubuntu 20.04
3m 15s
Build, Test on Ubuntu 20.04
Build, Test on Ubuntu 22.04
4m 15s
Build, Test on Ubuntu 22.04
Build, Test on Fedora Rawhide (Container)
12m 6s
Build, Test on Fedora Rawhide (Container)
Build on Windows
4m 40s
Build on Windows
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Build, Test on CentOS 7 (Container)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.