* WASM: Pump timer queue in xharness when running unit tests
We only pumped the threadpool but we didn't pump the timer queue inside the xharness runner, so in the case of Task.Delay() it'll schedule a callback on the timer queue and that will never happen which leads to the infinite loop waiting for the test to finish.
To fix that we call an internal method to pump the timer queue like we do for the threadpool.
Requires an xharness bump to include https://github.com/dotnet/xharness/pull/290
Fixes https://github.com/dotnet/runtime/issues/38931
* Don't nullref if no timers were started
* Suppress initial cred issues
* Another bunch of supresses
* Clean up
* Another bunch of supresses
* Revert to suppression messages
* Clean up
* Apply suggestions from code review
Co-authored-by: Jeremy Barton <jbarton@microsoft.com>
* Revert passwords literals
* Fix suppression justification comment
Co-authored-by: Jan Jahoda <jajahoda@.microsoft.com>
Co-authored-by: Jeremy Barton <jbarton@microsoft.com>
Uses the xharness tool to drive the test execution rather than calling v8 directly.
Also includes a fix for running the tests in JavaScriptCore which doesn't provide performance.now().
* Enable dotnet test
* Update docs
* Use vstest in F5 scenarios
* Make dotnet test without framework switch work
* Code cleanup
* Only run code coverage conditionally
* Fix F5 condition for netcoreapp
* Downgrade sdk to check for helix submission failures
* Fix wrong conditions
* Add blame data collector
If D (private key) is supplied but not the public key (Q), permit
this and allow the platform to re-calculate the public key from
the private key.
* Windows uses CNG blobs with the Q.X and Q.Y values set to (0,0).
* LInux uses the ECC math module to recompute Q from D and G.
* macOS is TBD.
* Implicitly build when invoking the test target
To get closer to the VSTest behavior this changes the Test target to
implicitly invoke the Build target unless /p:TestNoBuild is passed in.
(VSTest uses VSTestNoBuild which is controlled by the
dotnet test --no-build flag)
* Fix error logging for test outputs
* Update dotnet msbuild to build docs
* Update ReportGenerator global tool version
Updating ReportGenerator's version to 4.5.0 which removes unnecessary
logging (args passed in).
* Delete System.Data.SqlClient package
* Delete unnecessary SqlClient references
* Unify System.Data.SqlClient package reference
* Add System.Data facade test
* Add System.Data.SqlClient references
- Add System.Data.SqlClient package references for tests that need it
- Use System.Data.SqlClient reference assembly to build the System.Data shim
- Disable ILLinker for the shims since it does not work well with incremental builds and it is not necessary anyway
* Disable tests on Mono
Fixes https://github.com/dotnet/corefx/issues/40846
* Add Libraries Testing framework package as inline
The existing package Microsoft.DotNet.CoreFxTesting lived in Arcade
because of no infrastructure being available to compile local tasks in
the repository. As the runtime repository now offers that we can inline
the testing framework.
* Hardcode configuration for installer.tasks
* Update ReportGenerator global tool version
* Add vstest support
* Update binary serialization blobs
Alexander Köplinger
Jan Jahoda
Viktor Hofer
Egor Bogatov
Santiago Fernandez Madero
Kevin Jones
Jan Kotas
Marie Píchová
Marco Rossignoli
dotnet-bot