Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

URGENT: CI is broken, Win Installer #23495

Closed
edsantiago opened this issue Aug 2, 2024 · 3 comments
Closed

URGENT: CI is broken, Win Installer #23495

edsantiago opened this issue Aug 2, 2024 · 3 comments
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@edsantiago
Copy link
Member

Looks like all CI jobs are failing. Restart does not help:

Verifying that the machine provider configuration is correct...
Expected "hyperv" as default machine provider but got "wsl"
At C:\Users\Administrator\AppData\Local\cirrus-ci-build\repo\contrib\win-installer\test-installer.ps1:91 char:9
+         throw "Expected `"$expected`" as default machine provider but ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Expected "hyper...r but got "wsl":String) [], RuntimeException
    + FullyQualifiedErrorId : Expected "hyperv" as default machine provider but got "wsl"

(and vice-versa, expected wsl got hyperv). Logs:

The relevant code claims to have a parameter, $provider, but all calls to this function are parameterless.

function Test-Podman-Machine-Conf-Content {
param (
[ValidateSet("wsl", "hyperv")]
[string]$expected=$provider
)
Write-Host "Verifying that the machine provider configuration is correct..."
$machineProvider = Get-Content $MachineConfPath | Select-Object -Skip 1 | ConvertFrom-StringData | ForEach-Object { $_.provider }
if ( $machineProvider -ne "`"$expected`"" ) {
throw "Expected `"$expected`" as default machine provider but got $machineProvider"

Needs a Windows expert.

@edsantiago
Copy link
Member Author

Also Macintosh is down too.

@l0rd
Copy link
Member

l0rd commented Aug 5, 2024

I have opened a PR to temporarily disable the test that's failing and opened a dedicated issue to continue investigating the problem.

@Luap99
Copy link
Member

Luap99 commented Aug 5, 2024

We can close this then

@Luap99 Luap99 closed this as completed Aug 5, 2024
@stale-locking-app stale-locking-app bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Nov 4, 2024
@stale-locking-app stale-locking-app bot locked as resolved and limited conversation to collaborators Nov 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

3 participants