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

What kind of testing is done by the project #923

Closed
MikeGitb opened this issue Apr 9, 2017 · 4 comments
Closed

What kind of testing is done by the project #923

MikeGitb opened this issue Apr 9, 2017 · 4 comments
Labels
category:documentation To resolve the issue, documentation will need to be updated category:vcpkg-feature The issue is a new capability of the tool that doesn’t already exist and we haven’t committed

Comments

@MikeGitb
Copy link
Contributor

MikeGitb commented Apr 9, 2017

As there is no visible ci going on I was wondering if the MS Team actually checks if all the portfiles work correctly (on which platform / with which compiler / are you running any tests / any test projects?). And if the library versions in the master branch play "nice" together or if there are any incompatibilities.

Especially when less experienced people like me are trying to write a non-trivial portfile or upgrading an existing one it would be nice to have more feedback than just: "It seems to work on my machine"

@KindDragon
Copy link
Contributor

It's not possible to compile all ports in the reasonable time. We had discussion about that in issue #72

@MikeGitb
Copy link
Contributor Author

MikeGitb commented Apr 9, 2017

@KindDragon: Thank you for the link.
I understand that a "classic" public github CI (e.g. via appveyor) doesn't work here or is at least difficult to implement. However, MS should have more than enough ressources to internally build all libraries e.g. once a day and report any failures.

Also from the FAQ (under "Why not Conan?"):

We believe this will result in a set of high quality packages that are heavily tested with each other and form a fantastic base for any private modifications you need.

Of course this testing will - to a large degree - happen organically by the users but relying on the users of your SW as the only/primary means of testing is imho not really a situation one should be content with.

@KindDragon
Copy link
Contributor

I agree with you. It would be nice to automatically test changed ports in PR.

I think better continue discussion in the old issue

@ras0219-msft ras0219-msft added category:documentation To resolve the issue, documentation will need to be updated category:vcpkg-feature The issue is a new capability of the tool that doesn’t already exist and we haven’t committed labels Apr 10, 2017
@ras0219-msft
Copy link
Contributor

Continued in #72 -- thanks for deduplicating, @KindDragon!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:documentation To resolve the issue, documentation will need to be updated category:vcpkg-feature The issue is a new capability of the tool that doesn’t already exist and we haven’t committed
Projects
None yet
Development

No branches or pull requests

3 participants