-
Notifications
You must be signed in to change notification settings - Fork 1
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
Systematically test ports #6
Comments
Have you tested if https://github.com/open-vcpkg/python-registry/blob/main/ports/vcpkg-python-scripts/import_test.py.in can fail? I had a weird issues while testing stuff like that that the script never seems to fail. |
At some point during #3 it failed, but maybe in an older version |
Would be good to have an explicitly failing test to make sure the test actual works both ways. |
From microsoft/vcpkg#37409 I noticed that the import test should only run for native builds. |
The import test script should probably be moved into the python3 port. |
For different triplets and with systematic detection of available ports, controlled by a blocklist.
Ideally code from upstream can be reused, see https://github.com/microsoft/vcpkg/blob/master/scripts/azure-pipelines/test-modified-ports.ps1 /
ci.baseline.txt
.The text was updated successfully, but these errors were encountered: