You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Affected Puppet, Ruby, OS and module versions/distributions
Puppet: 7, 8
Ruby: 2.7, 3.x
Distribution: Archlinux and all other
Module version: 10.0.0
How to reproduce (e.g Puppet code you use)
Run acceptance on one of the operating system
What are you seeing
All Oses run a test with default version and N for the supported version
In most case it run twice with the some version, in other case like Archlinux run only with operating system repo version of package that not in the supported list.
What behaviour did you expect instead
Run acceptance test only one per version
Run acceptance only on supported version
Need a plan to use in the best way acceptance test, Probabli custom matrix not solve the problem, but run test on Archlinux with parameter zabbix_version 5 and 6 with the installed package as 6.4 isn't the best we can do
The text was updated successfully, but these errors were encountered:
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
Run acceptance on one of the operating system
What are you seeing
All Oses run a test with default version and N for the supported version
In most case it run twice with the some version, in other case like Archlinux run only with operating system repo version of package that not in the supported list.
What behaviour did you expect instead
Run acceptance test only one per version
Run acceptance only on supported version
Output log
https://archlinux.org/packages/extra/x86_64/zabbix-agent/
zabbix-agent 6.4.12-2
Any additional information you'd like to impart
Need a plan to use in the best way acceptance test, Probabli custom matrix not solve the problem, but run test on Archlinux with parameter zabbix_version 5 and 6 with the installed package as 6.4 isn't the best we can do
The text was updated successfully, but these errors were encountered: