-
Notifications
You must be signed in to change notification settings - Fork 132
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
smoke-tests: Minimal set of tests without the need of downloading #2844
Comments
There are a couple issues at play here:
How are distro-maintainers testing other source-built dev platforms like .NET (e.g. OpenJDK, Python, etc)? Don't other dev platforms face similar issues? Are they able to test online or bring a set of test prereqs/prebuilts? cc @dotnet/distro-maintainers - Please share your thoughts/experiences on this. |
As can be seen in the This kind of naïve testing does seem to be the norm in Homebrew, though. You can see the |
On Alpine's side, we use the Redhat's |
Smoke tests should be small tests that verify things are not completely broken. dotnet-regular-tests has many regression tests. dotnet-regular-tests also has some rid related tests. We shouldn't need these, source-build should be able to check it can work well when faced with unknown rids (#297). |
[Triage] @mirespace - per our discussions, my impression is that this is not a requirement and that you have a solution in place to test. Is that correct? Can this issue be closed? |
Hi!
Describe the Problem
I would like to use the smoke test suite as part of the test build stage when packaging dotNet6 from source-build on Ubuntu (for the 22.04 series currently) but with a minimal set of tests that don't require downloading anything from the internet to pass, as our CI infra doesn't allow it.
I locally build the last tag version v6.0.104 and I can also use the tests:
but unfortunately, our CI does not allow the use of external downloads and it breaks:
In fact, with the old smoke-test.sh, using the
--minimal --excludeOnlineTests --excludeOmniSharpTests
options gave the idea of no need to download configurations or packages (in practice, this was not the case and internet access was needed to pass this minimal set of tests).Describe the Solution
Ideally, the tarball should store everything needed to run at least that minimum test suite along with the smoke test suite.
Thanks in advance for considering this,
Miriam
The text was updated successfully, but these errors were encountered: