-
Notifications
You must be signed in to change notification settings - Fork 7.1k
[vsgqt] New port #47899
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
base: master
Are you sure you want to change the base?
[vsgqt] New port #47899
Conversation
v8:x64-windows-static=fail | ||
v8:x64-windows=fail | ||
v8:x86-windows=fail | ||
# https://github.com/vsg-dev/vsgQt/pull/53 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This means that it isn't a problem with our build lab and is a problem with the port, so it should probably be a "supports"
right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, I expect upstream to merge the PR and CI to remind us of the changed result when the port is updated.
I dislike the chance of the port being updated with the supports
clause preventing test in CI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not worth forcing a rebuild to the nitpick suggestion. But curious about the ci.baseline.txt thing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer supports but it only affects android and I'm happy to leave that optimistic for now...
https://repology.org/project/vsgqt/versions
CC @gwaldron (related: #46945)