* Exclude omnisharp tests from CentOS 7 CI
* Update src/SourceBuild/Arcade/eng/common/templates/steps/source-build-build-tarball.yml
Co-authored-by: Chris Rummel <crummel@microsoft.com>
Co-authored-by: Chris Rummel <crummel@microsoft.com>
This fixes a regression in .NET 6 source-build compared to the .NET
5 source-build.
source-build wants to publish runtime symbols tarball for portable (eg,
linux-x64) and non-portable (eg, fedora.33-x64) RIDs here after a build.
Following .NET 5 conventions, I expected to see:
./artifacts/x64/Release/runtime/dotnet-runtime-symbols-fedora.34-x64-6.0.0.tar.gz
./artifacts/x64/Release/runtime/dotnet-runtime-symbols-linux-x64-6.0.0.tar.gz
Unfortunately, only the portable RID (linux-x64) tarball is present
after a full source-build in .NET 6.
It turns out this is a bug in our build scripts. We try and copy
binaries - including the symbol tarballs - after building each of
runtime-portable and runtime. However, the target dependency is wrong:
after `Build`, the intermediate package doesn't exist from the
just-built repo.
What ends up happening is that nothing is copied after building
runtime-portable. However, after building runtime, the runtime-portable
intermediate artifacts are found and copied over. So the end
build has portable RID symbos, but not the non-portable ones.
Fix that by changing the dependency of this target so it runs after
intermediate packages are available.
* [ArPow] Add smoke test for OmniSharp
* Try setting PATH for tests
Hopefully, this helps omnisharp find the SDK.
* edits necessary for 6.0 GA status
Co-authored-by: MichaelSimons <msimons@microsoft.com>
This is taking the approach used in previous versions of source-build: update the dependency versions of Microsoft.CodeAnalysis to the version currently being built by source-build. This is a short-term solution to get unblocked in the 6.0.0 timeframe. In the future, the previous Microsoft.CodeAnalysis versions will be available in SBRP.
Contributes to https://github.com/dotnet/source-build/issues/2420
Contributes to https://github.com/dotnet/source-build/issues/2527
* Move Omnisharp fix to the correct place.
We had some crossed PRs and this got added while the other patches were being moved. This moves it to the correct place.
* Update patch to apply to new hash.
* Another project dependency.