-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
New version: KhronosGroup.VulkanSDK version 1.3.261.1 #118619
New version: KhronosGroup.VulkanSDK version 1.3.261.1 #118619
Conversation
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @scribam, During installation testing, this application failed to install without user input. Did you forget to add Silent or SilentWithProgress switches? This can also happen when a dependency is missing. You can test with https://github.com/microsoft/winget-pkgs#test-your-manifest. Please investigate a fix and resubmit the Pull Request. You may also try using the Windows Package Manager Manifest Creator to determine the proper installer type. If the installer type is MSIX, MSI, or a known installer technology like NullSoft, Inno, etc. the wingetcreate tool can detect them and the winget client will know what switches to pass. If it's a .exe installer of an unknown type, you will need to search to determine the proper switches for Silent and SilentWithProgress. Template: msftbot/validationError/installation/unattended |
Manual Validation failed with:
|
manifests/k/KhronosGroup/VulkanSDK/1.3.261.1/KhronosGroup.VulkanSDK.installer.yaml
Outdated
Show resolved
Hide resolved
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @scribam, During installation testing, this application failed to install without user input. Did you forget to add Silent or SilentWithProgress switches? This can also happen when a dependency is missing. You can test with https://github.com/microsoft/winget-pkgs#test-your-manifest. Please investigate a fix and resubmit the Pull Request. You may also try using the Windows Package Manager Manifest Creator to determine the proper installer type. If the installer type is MSIX, MSI, or a known installer technology like NullSoft, Inno, etc. the wingetcreate tool can detect them and the winget client will know what switches to pass. If it's a .exe installer of an unknown type, you will need to search to determine the proper switches for Silent and SilentWithProgress. Template: msftbot/validationError/installation/unattended |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hello @scribam, During installation testing, this application failed to install without user input. Did you forget to add Silent or SilentWithProgress switches? This can also happen when a dependency is missing. You can test with https://github.com/microsoft/winget-pkgs#test-your-manifest. Please investigate a fix and resubmit the Pull Request. You may also try using the Windows Package Manager Manifest Creator to determine the proper installer type. If the installer type is MSIX, MSI, or a known installer technology like NullSoft, Inno, etc. the wingetcreate tool can detect them and the winget client will know what switches to pass. If it's a .exe installer of an unknown type, you will need to search to determine the proper switches for Silent and SilentWithProgress. Template: msftbot/validationError/installation/unattended |
This application installed and launched normally on a Windows 10 VM. |
@wingetbot waivers Add Validation-Unattended-Failed |
/AzurePipelines run |
Azure Pipelines successfully started running 1 pipeline(s). |
scribam, The check-in policies require a moderator to approve PRs from the community. Our moderators are community volunteers, please be patient and allow them sufficient time to review your submission. Template: msftbot/requiresApproval/moderator |
302bd6c
into
microsoft:master
Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present. |
winget validate --manifest <path>
?winget install --manifest <path>
?Note:
<path>
is the name of the directory containing the manifest you're submitting.Microsoft Reviewers: Open in CodeFlow