| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
* Bump corert
* Bump API snapshot submodule
|
|
|
|
|
|
|
|
* [I18N] Add CP737 (Greek) and CP775 (Baltic)
Fixes https://bugzilla.xamarin.com/show_bug.cgi?id=45901
* Bump API snapshot submodule
|
|
* Fix some ThreadPool performance counters.
https://bugzilla.xamarin.com/show_bug.cgi?id=41294
The bug is that some performance counters are always zero.
Because we do not update them.
This addresses two of them: Work items added and thread count.
There is PerformanceCounter class and you can Increment instances,
however its metadata and some of the implementation is in System.dll.
Most of the code is in native.
ThreadPool is in mscorlib.dll, so can't use System.dll.
A few options exist to address this.
We could move and forward the type. We could duplicate and rename
and possibly subset the type.
Here we add a new icall very specifically for the scenario.
There is slight cost for the icall, and for the atomic increment.
There is an attempt to measure but the results were unclear.
Note that the count of work items is not specifically for QueueUserWorkItem
as one might expect, but also for any async calls.
Fix a little bit of typos.
* Take command lines from command line per PR feedback.
* newline at end of file
|
|
|
|
Fixes #6264.
|
|
Regression test for https://github.com/mono/mono/issues/6192
|
|
with Delegate.CreateDelegate (). Fixes https://github.com/mono/mono/issues/6255.
|
|
runtime (#6062)
* Checkpoint: Implement SynchronizationContext.Wait
* Add missing check for null synchronization context
* Update bug 60568 fix to cover WaitAll and add test cases
* Add missing file
|
|
|
|
|
|
category.
|
|
(#6225)
|
|
|
|
|
|
Multiple fixes to the wasm backend
|
|
* [runtime] Implement a few broken getters on ModuleBuilder
* [runtime] Implement ModuleBuilder.GetCustomAttributes
* [runtime] Test GetMethods, GetCustomAttributes, and GetFields for ModuleBuilder
* [runtime] Specify and test use of typebuilders with Custom Attributes + add more tests
|
|
|
|
|
|
runtime logs for instrumentation (#6083)
* [sdks] Fix Android pick of mono runtime
* [android] Have Console.{Out,Error} go through the runtime log mechanism to ease their interception
* [sdks] Intercept runtime logs instead of Console to send back for instrumentation
* [sdks] Intercept Android test runner logging
|
|
|
|
The test was added in https://github.com/mono/mono/commit/375471820c02ff0bab025bff75b5da7efc95d3cd.
We were seeing some flakyness in the this test, looking at it I
noticed that we were passing executeOnlyOnce = false to
(Unsafe)RegisterWaitForSingleObject. This means that the delegate
would be executed again whenever the AutoResetEvent `evt` is signaled or
the timeout elapsed. The problem is that evt is never signaled by design
and we set a timeout of 1ms which means we'd execute it in a tight loop.
Setting executeOnlyOnce = true fixes this and I verified it doesn't
change the intent of the test (i.e. the test still fails after the
original commit is reverted).
Bumped the timeout for the CountdownEvent as well to be safe
since it's quite short.
|
|
different ways on different configurations. (#6095)
* [bcl] Remove the test for ExecutingAssembly.EntryPoint, it behaves in different ways on different configurations.
* Simplify ifdef
|
|
|
|
* [bcl] Build some assemblies with -warnaserror
This ensures that we keep the build warning free.
We'll only opt-in a few assemblies that already have zero warnings.
We also only apply this when using csc as mcs might raise different warnings.
For now just opt-in assemblies in the net_4_x profile.
|
|
Corefx bump
|
|
|
|
|
|
cryptography tests. (#6091)
|
|
be needed any more, and it prevents the tests from compiling on the monotouch profile. (#6079)
|
|
|
|
the mono sdk. (#6064)
These tests are disabled explicitly on xamarin.ios by xharness.exe: https://github.com/xamarin/xamarin-macios/blob/6fcf4ab7f4c7e2f736a278ca138ab567c1ff6bae/tests/xharness/BCLTestInfo.cs#L16
|
|
* [corlib] Move System.Runtime.InteropServices.RuntimeInformation to corlib to match .net 4.7.1 api
* Bump API snapshot submodule
|
|
|
|
Fixes bug-60621 (#6014)
|
|
|
|
Unity-Technologies/winrt-time-zone-adjustment-rules
Fix TimeZoneInfo rule population for WinRT
|
|
|
|
successful case is ERROR_SUCCESS (0). Adjust failure case to be for return values non 0.
|
|
In Unix, assume our current directory contains:
`test`, a directory
`test/test2`, another directory
`test/test2/test_file`, a file
`test3`, a symbolic link pointing to `test/test2`
Then the path "test3/../test3" has two interpretations depending on the processor:
* The OS (the `lstat` syscall, `ls`, etc.) will find it invalid (as it evaluates to: enter `test/test2`, go up one level, try to enter `test3` which is another level down
* We (.NET, at least CoreCLR) should find it valid (enter `test3`, go up one level, enter `test3`).
This ensures that for Directory.Exists, we process the path `..`'s on the .NET level before passing it for native processing.
|
|
lewurm/fix-DefaultThreadCurrentCultureIsIgnoredWhenCultureFlowsToThread
[corlib] fix DefaultThreadCurrentCultureIsIgnoredWhenCultureFlowsToThread test
|
|
this test case was broken for an unknown time, but surfaced with a
recent change in nunit-lite (2255c54966b541095a93be16627e92acebf87215)
that runs every test in a new `ExecutionContext`. Previously, the
pre-condition for this test was implicility fulfilled by another test.
The test failed already when executed only on its own. With the change
around `ExecutionContext`, each test is "isolated" regarding said
pre-condition.
The fix is to explicitly fulfil the pre-condition in the test.
|
|
UnsafeRegisterWaitForSingleObject is used. Fixes #60029 (#6013)
|
|
|
|
echoes input characters correctly when TermInfoDriver is initialized instead of suppressing them. Fixes bug #40699.
|
