Skip to content

ci

ci #77

Manually triggered April 9, 2026 07:03
Status Cancelled
Total duration 1d 0h 2m 28s
Artifacts

ci.yml

on: workflow_dispatch
Spec  /  Setup Test Matrix
21s
Spec / Setup Test Matrix
Matrix: Spec / spec
Acceptance  /  Setup Test Matrix
13s
Acceptance / Setup Test Matrix
Matrix: Acceptance / acceptance
Fit to window
Zoom out
Zoom in

Annotations

44 errors and 32 warnings
Acceptance / Acceptance tests (SLES-12, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Debian-12, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (CentOS-8, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (RedHat-7, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Debian-12, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Windows-2016, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Rocky-8, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Debian-11, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (AlmaLinux-8, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Ubuntu-22.04, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (SLES-12, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Windows-2022, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (RedHat-9, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (RedHat-9-arm, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Ubuntu-22.04, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Windows-2019, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (RedHat-9, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (AlmaLinux-8, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Windows-2022, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (RedHat-7, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Windows-2016, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Debian-12-arm, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Ubuntu-22.04-arm, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Windows-2019, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Ubuntu-24.04-arm, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Ubuntu-24.04, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (CentOS-7, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Ubuntu-22.04-arm, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (RedHat-9-arm, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (RedHat-8, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Debian-10, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (OracleLinux-7, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (CentOS-8, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Debian-11, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (RedHat-8, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (OracleLinux-7, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (CentOS-7, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Ubuntu-24.04-arm, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Rocky-8, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Scientific-7, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Debian-12-arm, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Ubuntu-24.04, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Scientific-7, puppet7-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Acceptance / Acceptance tests (Debian-10, puppet8-nightly)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Spec / Setup Test Matrix
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Spec / Setup Test Matrix
AIX-7.1 no provisioner found
Spec / Setup Test Matrix
Windows-2012 R2 no provisioner found
Spec / Setup Test Matrix
Windows-2012 no provisioner found
Spec / Setup Test Matrix
Windows-10 no provisioner found
Spec / Spec tests (Puppet: ~> 8.0, Ruby Ver: 3.2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Spec / Spec tests (Puppet: ~> 8.0, Ruby Ver: 3.2): spec/unit/provider/reboot/windows_spec.rb#L197
Puppet::Type::Reboot::ProviderWindows when detecting if a reboot is pending Component-Based Servicing ignores on Vista and earlier Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 8.0, Ruby Ver: 3.2): spec/unit/provider/reboot/windows_spec.rb#L68
Puppet::Type::Reboot::ProviderWindows when checking if the `when` property is insync issues a shutdown command when a reboot is pending Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 8.0, Ruby Ver: 3.2): spec/unit/provider/reboot/windows_spec.rb#L62
Puppet::Type::Reboot::ProviderWindows when checking if the `when` property is insync does not reboot when setting the `when` property to refreshed Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 8.0, Ruby Ver: 3.2): spec/unit/provider/reboot/windows_spec.rb#L58
Puppet::Type::Reboot::ProviderWindows when checking if the `when` property is insync is absent by default Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 8.0, Ruby Ver: 3.2): spec/unit/provider/reboot/windows_spec.rb#L47
Puppet::Type::Reboot::ProviderWindows when resolving the shutdown command raises an error if shutdown.exe cannot be found Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 8.0, Ruby Ver: 3.2): spec/unit/provider/reboot/windows_spec.rb#L41
Puppet::Type::Reboot::ProviderWindows when resolving the shutdown command uses 'shutdown.exe' Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 8.0, Ruby Ver: 3.2): spec/unit/provider/reboot/windows_spec.rb#L35
Puppet::Type::Reboot::ProviderWindows when resolving the shutdown command falls back to system32 Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 8.0, Ruby Ver: 3.2): spec/unit/provider/reboot/windows_spec.rb#L30
Puppet::Type::Reboot::ProviderWindows when resolving the shutdown command tries to disable file system redirection Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 8.0, Ruby Ver: 3.2): spec/unit/provider/reboot/windows_spec.rb#L24
Puppet::Type::Reboot::ProviderWindows self.instances returns an empty array Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 8.0, Ruby Ver: 3.2): spec/unit/provider/reboot/windows_spec.rb#L19
Puppet::Type::Reboot::ProviderWindows is an instance of Puppet::Type::Reboot::ProviderWindows Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 7.24, Ruby Ver: 2.7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Spec / Spec tests (Puppet: ~> 7.24, Ruby Ver: 2.7): spec/unit/provider/reboot/windows_spec.rb#L197
Puppet::Type::Reboot::ProviderWindows when detecting if a reboot is pending Component-Based Servicing ignores on Vista and earlier Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 7.24, Ruby Ver: 2.7): spec/unit/provider/reboot/windows_spec.rb#L68
Puppet::Type::Reboot::ProviderWindows when checking if the `when` property is insync issues a shutdown command when a reboot is pending Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 7.24, Ruby Ver: 2.7): spec/unit/provider/reboot/windows_spec.rb#L62
Puppet::Type::Reboot::ProviderWindows when checking if the `when` property is insync does not reboot when setting the `when` property to refreshed Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 7.24, Ruby Ver: 2.7): spec/unit/provider/reboot/windows_spec.rb#L58
Puppet::Type::Reboot::ProviderWindows when checking if the `when` property is insync is absent by default Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 7.24, Ruby Ver: 2.7): spec/unit/provider/reboot/windows_spec.rb#L47
Puppet::Type::Reboot::ProviderWindows when resolving the shutdown command raises an error if shutdown.exe cannot be found Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 7.24, Ruby Ver: 2.7): spec/unit/provider/reboot/windows_spec.rb#L41
Puppet::Type::Reboot::ProviderWindows when resolving the shutdown command uses 'shutdown.exe' Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 7.24, Ruby Ver: 2.7): spec/unit/provider/reboot/windows_spec.rb#L35
Puppet::Type::Reboot::ProviderWindows when resolving the shutdown command falls back to system32 Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 7.24, Ruby Ver: 2.7): spec/unit/provider/reboot/windows_spec.rb#L30
Puppet::Type::Reboot::ProviderWindows when resolving the shutdown command tries to disable file system redirection Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 7.24, Ruby Ver: 2.7): spec/unit/provider/reboot/windows_spec.rb#L24
Puppet::Type::Reboot::ProviderWindows self.instances returns an empty array Skipped: Not on Windows platform
Spec / Spec tests (Puppet: ~> 7.24, Ruby Ver: 2.7): spec/unit/provider/reboot/windows_spec.rb#L19
Puppet::Type::Reboot::ProviderWindows is an instance of Puppet::Type::Reboot::ProviderWindows Skipped: Not on Windows platform
Acceptance / Setup Test Matrix
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Acceptance / Setup Test Matrix
AIX-7.1 no provisioner found
Acceptance / Setup Test Matrix
Windows-2012 R2 no provisioner found
Acceptance / Setup Test Matrix
Windows-2012 no provisioner found
Acceptance / Setup Test Matrix
Windows-10 no provisioner found