bxl.ps1 is used to run this test build in RunCheckinTests.cmd. But that test build doesn't have the mounts that bxl.ps1 expects. Silence the warning for that build specifically
The "PartB" validation isn't hooked up to the shared cache, so it always times out after 5 seconds and emits a warning. Disable usage of the shared cache.
I don't expect much impact on dev builds since folks aren't running this suite locally.
Enable shared compilation by default for bxl self-host. It can be still turned off explicitly by doing:
bxl.cmd -UseManagedSharedCompilation:$false
In order to slowly roll out this feature, shared compilation is always turned off for non-internal builds and whenever /ado is passed (to catch azdevops scenarios and keep them unchanged).
An extra step in the bxl rolling build is already added to also populate the shared cache with shared compilation on.
Removals:
- building minimal end-to-end BuildXL on .NET Core (which only builds the Collections assembly)
- building .NET Core example
- building again for net472 just for the purpose of running the distributed test (instead, use previously built win-x64 bits)
Additionally:
- ignore VirusScanEnabledForPath warnings when running in /lab
The new LKG contains changes to how nuget/cgmanifest.json is generated. To avoid breaking our validation, the LKG and the generated nuget/cgmanifest.json must be updated together (this is a one-off manual update).
Previously, a ReaderWriterLock was used.
On .NET Core, errors like "Attempt to release a lock that is not owned by the calling thread" were happening regularly in our CI validations.
This PR replaces this lock with a regular exclusive lock, since in our particular uses of ConcurrentBoundedSortedCollection we never have only concurrent reads, so it's questionable if we were getting any benefits from use a read-write lock.
AB#1533036