- 04 2月, 2022 13 次提交
-
-
由 Tomáš Rylek 提交于
Previously I refactored these tests by moving the entrypoints from the shared body_xxx source files into the test-specific expl_* and seq_* source files but I didn't realize I'd also need to put them into new uniquely named classes as we clearly cannot distinguish 30 methods named AA.TestEntrypoint(). Thanks Tomas
-
由 Tomáš Rylek 提交于
-
由 Andy Gocke 提交于
* Update mac Helix queues * Adjust test to account for Mac RID changes * Disable DllImport probing test on Mac * Disable profiler.multiple on Mac
-
由 SingleAccretion 提交于
"fgValueNumberBlockAssignment" had a very interesting oddity: it re-VNs the source tree of the assignment. This is unnecessary, and is in fact a pessimization, as it means we will fail to VN assignments from sources it does not understand. This change fixes that, bringing along some positive diffs from numbering stores from field indirections. "fgValueNumberBlockAssignment" also needs to maintaint the invariant that a location's VN will always match its type. It was failing to do that in cases where the assignment's source was not local. This change fixes that. Finally, this change unifies the code common to numbering "CopyBlk" and "InitBlk" cases. There is no need for them to be different.
-
由 Tomáš Rylek 提交于
This change converts a small number of special tests to use the [Fact] style. These tests are atypical in using various internal types declared in their source code as fields in the test class; bumping up test class visibility to public requires transitive modifications to visibility of the helper types. Thanks Tomas
-
由 Kevin Jones 提交于
-
由 John Salem 提交于
This only applies to CoreCLR Unix processes.
-
由 Maryam Ariyan 提交于
* Adds support to `@` signed prefixed parameters Fixes #60968 * Move repetitive logic to a new property * Remove NeedsAtSign
-
https://github.com/dotnet/linker由 dotnet-maestro[bot] 提交于
Microsoft.NET.ILLink.Tasks From Version 7.0.100-1.22078.1 -> To Version 7.0.100-1.22081.3 Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
-
由 dotnet-maestro[bot] 提交于
[main] Update dependencies from dotnet/icu dotnet/arcade dotnet/emsdk dotnet/roslyn-analyzers (#64678) * Update dependencies from https://github.com/dotnet/icu build 20220201.1 Microsoft.NETCore.Runtime.ICU.Transport From Version 7.0.0-preview.2.22081.1 -> To Version 7.0.0-preview.2.22101.1 * Update dependencies from https://github.com/dotnet/roslyn-analyzers build 20220201.5 Microsoft.CodeAnalysis.NetAnalyzers From Version 7.0.0-preview1.22081.3 -> To Version 7.0.0-preview1.22101.5 * Update dependencies from https://github.com/dotnet/arcade build 20220130.1 Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.Build.Tasks.Workloads , Microsoft.DotNet.Build.Tasks.Templating , Microsoft.DotNet.Build.Tasks.TargetFramework.Sdk , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.ApiCompat , Microsoft.DotNet.XUnitExtensions , Microsoft.DotNet.GenAPI , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.GenFacades , Microsoft.DotNet.SharedFramework.Sdk , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.PackageTesting , Microsoft.DotNet.Helix.Sdk From Version 2.5.1-beta.22075.6 -> To Version 2.5.1-beta.22080.1 * Update dependencies from https://github.com/dotnet/emsdk build 20220202.3 Microsoft.NET.Workload.Emscripten.Manifest-7.0.100 From Version 7.0.0-alpha.2.22078.1 -> To Version 7.0.0-alpha.2.22102.3 * Update dependencies from https://github.com/dotnet/roslyn-analyzers build 20220202.1 Microsoft.CodeAnalysis.NetAnalyzers From Version 7.0.0-preview1.22081.3 -> To Version 7.0.0-preview1.22102.1 Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com> Co-authored-by: NViktor Hofer <viktor.hofer@microsoft.com>
-
由 Maxim Lipnin 提交于
Related issues: [mono][arm6][linux] System.Net.Ping.Functional.Tests failed #64673 [mono][arm6][linux] System.Net.Tests.ServicePointManagerTest.FindServicePoint_Collectible failed. #64674 [mono][arm6][linux] System.Reflection.Tests.ModuleTests.GetField failed #64675 Co-authored-by: NAdeel Mujahid <3840695+am11@users.noreply.github.com>
-
由 Radek Zikmund 提交于
-
由 Parker Bibus 提交于
* Add dotnet install and run to test if new dotnet version can be installed similar to how it is done in the Maui repo. * Download and use local dotnet version. * Use updated dotnet for more of the pipeline. * Test with made runtime packs and and add ios arm pack substitution. * Try building instead of publishing. * Reenable everything for full test run. * Package name now seems to default to lower case, at least for maui.
-
- 03 2月, 2022 23 次提交
-
-
由 Alexander Köplinger 提交于
See https://github.com/dotnet/xharness/issues/385, we use the cache dir instead on API 30. Also add `a:exported="true"` which is required when targetting a newer minSdkVersion.
-
由 Egor Bogatov 提交于
-
由 Viktor Hofer 提交于
* Consume renamed TargetFramework package * Rename CoreLibs generator parent dir Projects under src/libraries/ which are located under a "gen" directory are automatically treated as source generator projects. Because the CoreLib generator was placed under a different directory "generators", it was treated as a RuntimeAssembly which gets binplaced into the runtime path. The runtime tests then take the assemblies from there and copy them into their CORE_ROOT directory. Renaming the CoreLib source generators parent directory fixes that so that it is treated as source generator and it brings consistency into src/libraries.
-
由 Meri Khamoyan 提交于
-
由 Egor Bogatov 提交于
Co-authored-by: NJakob Botsch Nielsen <Jakob.botsch.nielsen@gmail.com>
-
由 Michał Zegan 提交于
The command `src/tests/build[.cmd|.sh] nativeaot [Debug|Release] tree nativeaot` seems not to work as expected. Namely it seems to build not only the nativeaot smoke tests. Fixed to be `src\tests\build[.cmd|.sh] -nativeaot [Debug|Release] -tree:nativeaot`
-
由 Michal Strehovský 提交于
Fixes issue discovered in https://github.com/dotnet/runtime/pull/64404#discussion_r797220167. The existing code worked but there is an off chance that a different kind of delegate (not multicast) could be storing a number in `m_extraFunctionPointerOrData` that matches the length of this delegate (length is stored in `m_extraFunctionPointerOrData`), making us fail with `InvalidCast`. We should only compare invocation lists once we know both delegates are multicast.
-
由 Michal Strehovský 提交于
Matches crossgen2.
-
由 Larry Ewing 提交于
-
由 Ankit Jain 提交于
-
由 Michal Strehovský 提交于
The compiler avoids dealing with things that don't resolve and we have handling for those in place to turn them into runtime exceptions. We hit a situation when it doesn't kick in: * We're working with a nested type that is fine, but it's owning type is not (it implements an interface that doesn't resolve). * The protections within the compiler kick in and avoid bringing the containing type into compilation. * Once we're done compiling, we need to generate native reflection metadata for the nested type and that requires generating native metadata for the owning type. We don't have protections there because it's too late to do anything about it. I'm adding code that skips problematic parts of the metadata. This is a slight compat problem because doing a `typeof(NestedType).DeclaringType` would throw on JIT-based CoreCLR, but will now succeed on NativeAOT-based CoreCLR. The returned type will have an empty interface list. The compat in this corner case probably doesn't matter much.
-
由 Ankit Jain 提交于
* [wasm][debugger] Fix racy page reload test `BreakpointTests.CreateGoodBreakpointAndHitGoToWasmPageWithoutAssetsComeBackAndHitAgain` 1. the test loads the regular app page 2. then it reloads the page by calling `load_wasm_page_without_assets()` a. then waits for 1 sec 3. then it reloads again by calling `reload_wasm_page()` a. then `insp.WaitFor(Inspector.READY)` the READY notification after the second reload is never read. Instead, it tries to wait for the notification after the third reload, but that immediately returns because of the second one, instead of waiting for a new one. Fix is to correctly wait for a READY after the second reload. Another way to do this might be to clear the notifications when a new page gets loaded (`executionContextCreated`?), but that would be a bit magical, and isn't needed by any test right now. Fixes https://github.com/dotnet/runtime/issues/64585 * [wasm][debugger] Fix racy test - ExceptionTestAllWithReload This test is set up to pause on all exceptions. So, it has some code to hit `Debugger.resume` 100 times, hoping to skip all the non-user code exceptions. But this can sometimes not be enough, and you might have more exceptions which breaks rest of the test. Instead, we try to resume till we won't get paused for a period of 10secs. And after that, we can call the user code, and execute rest of the test. Fixes https://github.com/dotnet/runtime/issues/62666 . * Revert "[wasm][debugger] Fix racy test - ExceptionTestAllWithReload" This reverts commit 10d40720dec3410bc9944d159d374223a53f7d67.
-
由 Radek Doulik 提交于
* Initial changes for emscripten 2.0.34 * Use emcc-link.rsp in build targets * Use updated docker images * Fix compiler warnings Co-authored-by: NZoltan Varga <vargaz@gmail.com> * Put `--profiling-funcs` to `_EmccLinkFlags` * Fix build src/mono/mono/mini/mini-runtime.c:3407:25: error: ‘invoke’ undeclared (first use in this function); did you mean ‘revoke’? 3407 | invoke = mono_marshal_get_runtime_invoke_dynamic (); * Add shell to the environment Environment setting https://github.com/emscripten-core/emscripten/blob/2.0.34/src/settings.js#L616-L641 From emscripten 2.0.25 release notes - Support for the 'shell' environment is now disabled by default. Running under `d8`, `js`, or `jsc` is not something that most emscripten users ever want to do, so including the support code is, more often than not, unnecessary. Users who want shell support can enable it by including 'shell' in `-s ENVIRONMENT` (#14535). Example of the the size increase for bench sample: -a--- 12/10/2021 3:35 PM 382113 dotnet.js -a--- 12/13/2021 10:37 AM 383589 dotnet.js * Add emcc-link.rsp to PlatformManifestFileEntry * Feedback https://github.com/emscripten-core/emscripten/blob/2fda25eea756c78c8cb024aa5b6c2b188bf7990f/src/settings.js#L1173-L1176 -s EXPORT_ES6 is link option * Use new Emscripten workload * Remove unused variable * Add the emcc-link.rsp * Bump dotnet icu * Feedback * Do not add linker flags to compilation * Split `_EmccLDFlags` To avoid these errors: WasmApp.Native.targets(342,5): error : Failed to compile .../Microsoft.CodeAnalysis.CSharp.dll.bc -> /datadisks/disk1/work/B9F209B7/w/B1710A2F/e/wasm_build/obj/wasm/for-build/Microsoft.CodeAnalysis.CSharp.dll.o WasmApp.Native.targets(342,5): error : emcc: warning: linker setting ignored during compilation: 'TOTAL_MEMORY' [-Wunused-command-line-argument] WasmApp.Native.targets(342,5): error : emcc: warning: linker setting ignored during compilation: 'ERROR_ON_UNDEFINED_SYMBOLS' [-Wunused-command-line-argument] * Bump emscripten workload * Update windows helix queues * [wasm] Fix WBT running with nodejs When running with nodejs, the managed app would exit with code 42, but node would exit with 1. Use `process.exit` for node, instead of `mono_wasm_exit`. Co-authored-by: NRadek Doulik <radekdoulik@google.com> Co-authored-by: NZoltan Varga <vargaz@gmail.com> Co-authored-by: NLarry Ewing <lewing@microsoft.com> Co-authored-by: NAnkit Jain <radical@gmail.com> Co-authored-by: NSteve Pfister <steve.pfister@microsoft.com>
-
由 Steve Pfister 提交于
-
由 Přemek Vysoký 提交于
-
由 Tanner Gooding 提交于
* Change the BitArray(bool[]) constructor to use the xplat intrinsics * Change the And, Or, Xor, and Not methods to use the xplat intrinsics
-
由 Ankit Jain 提交于
-
由 Jan Kotas 提交于
* Delete InternalAssemblyBuilder * Delete InternalModuleBuilder These wrapper types were required for CAS (Code Access Security). They should not be needed anymore. Mono does not have them either.
-
由 Kloizdena 提交于
* Member resolving fix for derived attributes (#62937) * Added property with simple [Required] attribute
-
由 Thays Grazia 提交于
* Implement Set Next Instruction Pointer. * Addressing @radical comments. * Checking if the line number is inside the same function. Adding test for it. Adding test for moving the IP to a line that has already a breakpoint. * Creating tests in async function and lambda as suggested by @radical * Addressing @radical comments. * Addressing @radical comments offline * Adding comment to explain dual invocations. * Removing unnecessary code. * Addressing @radical comments. * Update src/mono/wasm/debugger/BrowserDebugProxy/MonoSDBHelper.cs Co-authored-by: NAnkit Jain <radical@gmail.com> * Addressing @radical comments. * Apply suggestions from code review Co-authored-by: NAnkit Jain <radical@gmail.com> * Removing unnecessary code.Addressing @radical comments. * Addressing @radical comments. * Added test as suggested offline by @radical * Creating tests as suggested by @radical. * Adding test as suggested by @radical. Fixing behavior of this new test: moving IP to a nested function. * Changing order in test. * Creating new test suggested by @radical. * Update src/mono/wasm/debugger/BrowserDebugProxy/MonoProxy.cs Co-authored-by: NAnkit Jain <radical@gmail.com> * Addressing @radical comments. * Addressing @radical comments. Co-authored-by: NAnkit Jain <radical@gmail.com>
-
由 Maryam Ariyan 提交于
-
由 Larry Ewing 提交于
-
由 Aaron Robinson 提交于
* Add tests for `ref` field overlap with OBJECTREF and non-aligned `ref` fields.
-
- 02 2月, 2022 4 次提交
-
-
由 Andrii Kurdiumov 提交于
I fix only most trivial where I fully understand what's going on. I will take a look at other too, maybe in subsequent PRs. This is related to https://github.com/dotnet/runtimelab/issues/106
-
由 Andrew Au 提交于
-
由 Michal Strehovský 提交于
The method itself is not unresolved - there's something wrong within the method body.
-
由 Alexander Köplinger 提交于
They fail there, see https://github.com/dotnet/runtime/issues/64446
-