I just wanted to make sure. You left this comment on the release-cuda issue:

H'm well it seems to make sense at least for

nix eval nixpkgs#cudaPackages.cudnn_8_0.brokenConditions
{ "CUDA version is too new" = true; ... }

Did I understand correctly, that you are okay with

• moving cudnn.brokenConditions."CUDA version is too old/new" to badPlatformsConditions
• moving nsight_systems.brokenConditions."CUDA too old (<11.8)" to badPlatformsConditions
• moving nvidia_driver.brokenConditions."Package is not supported; use drivers from linuxPackages" to badPlatformsConditions
• adding tensorrt.hydraPlatforms = none

?

As I've mentioned, you can see the exact code I am talking about here.

I just wanted to make sure. You left this comment on the release-cuda issue:

H'm well it seems to make sense at least for

nix eval nixpkgs#cudaPackages.cudnn_8_0.brokenConditions
{ "CUDA version is too new" = true; ... }

Did I understand correctly, that you are okay with

• moving cudnn.brokenConditions."CUDA version is too old/new" to badPlatformsConditions
• moving nsight_systems.brokenConditions."CUDA too old (<11.8)" to badPlatformsConditions
• moving nvidia_driver.brokenConditions."Package is not supported; use drivers from linuxPackages" to badPlatformsConditions
• setting tensorrt.hydraPlatforms = none (because it can't be built on Hydra)

?

As I've mentioned, you can see the exact code I am talking about here.

I just wanted to make sure. You left this comment on the release-cuda issue:

H'm well it seems to make sense at least for

nix eval nixpkgs#cudaPackages.cudnn_8_0.brokenConditions
{ "CUDA version is too new" = true; ... }

Did I understand correctly, that you are okay with

• moving cudnn.brokenConditions."CUDA version is too old/new" to badPlatformsConditions
• moving nsight_systems.brokenConditions."CUDA too old (<11.8)" to badPlatformsConditions
• moving nvidia_driver.brokenConditions."Package is not supported; use drivers from linuxPackages" to badPlatformsConditions
• setting tensorrt.hydraPlatforms = none (because it can't be built on Hydra)

?

We can keep the Qt 5 missing (<2022.4.2.1)/Qt 6 missing (>=2022.4.2.1) as brokenConditions, because they aren't currently producing eval errors and it makes sense that we want to detect these conditions in CI.

As I've mentioned, you can see the exact code I am talking about here.

I just wanted to make sure. You left this comment on the release-cuda issue:

H'm well it seems to make sense at least for

nix eval nixpkgs#cudaPackages.cudnn_8_0.brokenConditions
{ "CUDA version is too new" = true; ... }

Did I understand correctly, that you are okay with

• moving cudnn.brokenConditions."CUDA version is too old/new" to badPlatformsConditions
• moving nsight_systems.brokenConditions."CUDA too old (<11.8)" to badPlatformsConditions
• moving nvidia_driver.brokenConditions."Package is not supported; use drivers from linuxPackages" to badPlatformsConditions
• setting tensorrt.hydraPlatforms = none (because it can't be built on Hydra)

?

We can keep the Qt 5 missing (<2022.4.2.1)/Qt 6 missing (>=2022.4.2.1) as brokenConditions, because they aren't currently producing eval errors and it makes sense that we want to detect these conditions in CI.

As I've mentioned, you can see the exact changes I am talking about here.

I just wanted to make sure. You left this comment on the release-cuda issue:

H'm well it seems to make sense at least for

nix eval nixpkgs#cudaPackages.cudnn_8_0.brokenConditions
{ "CUDA version is too new" = true; ... }

Did I understand correctly, that you are okay with

• moving cudnn.brokenConditions."CUDA version is too old/new" to badPlatformsConditions
• moving nsight_systems.brokenConditions."CUDA too old (<11.8)" to badPlatformsConditions
• moving nvidia_driver.brokenConditions."Package is not supported; use drivers from linuxPackages" to badPlatformsConditions
• setting tensorrt.hydraPlatforms = none (because it can't be built on Hydra)

?

We can keep the Qt 5 missing (<2022.4.2.1)/Qt 6 missing (>=2022.4.2.1) as brokenConditions, because they aren't currently producing eval errors and it makes sense that we want to detect these conditions in CI.

You can see the exact changes I am talking about here.

I just wanted to make sure. You left this comment on the release-cuda issue:

change brokenConditions to badPlatformsConditions

H'm well it seems to make sense at least for

nix eval nixpkgs#cudaPackages.cudnn_8_0.brokenConditions
{ "CUDA version is too new" = true; ... }

Did I understand correctly, that you are okay with

• moving cudnn.brokenConditions."CUDA version is too old/new" to badPlatformsConditions
• moving nsight_systems.brokenConditions."CUDA too old (<11.8)" to badPlatformsConditions
• moving nvidia_driver.brokenConditions."Package is not supported; use drivers from linuxPackages" to badPlatformsConditions
• setting tensorrt.hydraPlatforms = none (because it can't be built on Hydra)

?

We can keep the Qt 5 missing (<2022.4.2.1)/Qt 6 missing (>=2022.4.2.1) as brokenConditions, because they aren't currently producing eval errors and it makes sense that we want to detect these conditions in CI.

You can see the exact changes I am talking about here.

I just wanted to make sure. You left this comment on the release-cuda issue:

change brokenConditions to badPlatformsConditions

H'm well it seems to make sense at least for

nix eval nixpkgs#cudaPackages.cudnn_8_0.brokenConditions
{ "CUDA version is too new" = true; ... }

Did I understand correctly, that you are okay with

• moving cudnn.brokenConditions."CUDA version is too old/new" to badPlatformsConditions
• moving nsight_systems.brokenConditions."CUDA too old (<11.8)" to badPlatformsConditions
• moving nvidia_driver.brokenConditions."Package is not supported; use drivers from linuxPackages" to badPlatformsConditions
• setting tensorrt.hydraPlatforms = none (because it can't be built on Hydra)

?

You can see the exact changes I am talking about here.

We can keep the Qt 5 missing (<2022.4.2.1) / Qt 6 missing (>=2022.4.2.1) as brokenConditions, because they aren't currently producing eval errors and it makes sense that we want to detect these conditions in CI.