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
Sometimes a workload (probably more likely when testing candidate or edge releases) may not have a clean semantic version, but may have non-standard prerelease or build information. For example we observed workload version 19.2.0~git20240301.4c76c50 for ceph-mon on squid/candidate channel.
COU currently passes the versions directly to packaging.version.Version, which requires version strings to conform to PEP 440. So in this example, COU crashes with an InvalidVersion error.
COU should support comparing these dirty versions. This could be implemented by transforming them to something compatible with Version. Eg. in the case of the ceph-mon example here, it should strip the ~git.... postfix, so it can use 19.2.0 as the version to compare.
The text was updated successfully, but these errors were encountered:
Sometimes a workload (probably more likely when testing candidate or edge releases) may not have a clean semantic version, but may have non-standard prerelease or build information. For example we observed workload version
19.2.0~git20240301.4c76c50
for ceph-mon on squid/candidate channel.COU currently passes the versions directly to packaging.version.Version, which requires version strings to conform to PEP 440. So in this example, COU crashes with an InvalidVersion error.
COU should support comparing these dirty versions. This could be implemented by transforming them to something compatible with Version. Eg. in the case of the ceph-mon example here, it should strip the
~git....
postfix, so it can use19.2.0
as the version to compare.The text was updated successfully, but these errors were encountered: