| Age | Commit message (Collapse) | Author |
|---|
|
Use example.com and example.org instead.
Fixes https://github.com/mono/mono/issues/14585
Note that not all of the things I replaced make an actual network request but I thought it'd be nice to be consistent.
|
|
* [tests] Change timezone so it doesn't fail on UTC+2 systems
Change to remote UTC-1
* [interp] Enable System.XML tests
|
|
|
|
* [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.
|
|
Fixes bug-60621 (#6014)
|
|
* [runtime] Fix mkbundle compilation on OSX
* [runtime] Add aot arguments to mkbundle
* [runtime] Enable compiling aot with mkbundle
* [runtime] Add new dedup interface to mkbundle
* [runtime] Fix path resolving for mkbundle
* [runtime] Use mkbundle in BCL tests
* [runtime] Skip building System.Security, System.IdentityModel tests on testing_aot_full
* [runtime] Fix in-tree building for mkbundle
* [runtime] Move testing dll into profile
* [runtime] Add target to mkbundle all tests before CI
* [runtime] Build stripper and use with mkbundle
Preliminary linker support ran into dependency-finding bug
with the monolinker.exe binary. Fix postponed until later.
* [runtime] Skip not supported tests with mkbundle
* [runtime] Don't re-aot when running BCL tests
* [runtime] Provide config to mkbundle
* [runtime] Fix mkbundle internationalization test results, build all
* [runtime] Clean up temp mkbundle aot directory
* [runtime] Add mkbundle support for dedup
* [runtime] Fix tracking of dedup module in mkbundle
* [runtime] Document mkbundle AOT options in man pages
* [runtime] Fix CADMessage generic method argument marshalling
|
|
This reverts commit 9a287c04126d095e7371afee32632febd0dafd93, reversing
changes made to 4a79280b3bef8d5f15da9ddd2a2af3a03e194b03.
It breaks tons of tests.
|
|
|
|
They were either replaced by the autogenerated csproj files
or just completely broken for years.
|
|
Most of them used multiline C# string literals which
means they contained the line ending character of the file.
Updated to make the tests resilient to having CRLF instead of LF.
Some of the mcs tests used a checksum to compare files,
ensured those are checked out using LF.
|
|
To be consistent with the other MONO_FEATURE_* defines.
|
|
|
|
Apparently nunitlite is more strict here so we need to allow subclasses as well
and test for the more specific type.
|
|
It is always set in all profiles that we support so we can remove it.
|
|
|
|
They weren't updated in the last 6 years and aren't helpful anymore (e.g. by causing unrelated matches during git grep searches).
|
|
|
|
|
|
It is not simply replacement because we have to workaround dynamic codegen
for Xamarin.iOS.
Also there were several tests failing with MS implementation (e.g. for
W3C DOM conformance), so we had to disable them.
There is one regression that rather needs to be fixed in Reflection.Emit.
Also, some WCF tests fail with this implementation. They need to be
investigated, reviewed and appropriately fixed.
|
|
Clean up mcs build system
|
|
|
|
* Removed all old profiles from VALID_PROFILE checks.
* Removed most logic under checks like ifeq (net_2_0), $(PROFILE)) as
it is dead code now that those old profiles are gone.
* Simplified the list of assemblies in mcs/class/Makefile now that we
only have one profile.
* LIBRARY_NEEDS_POSTPROCESSING has been removed as it was only used by
old 1.x assemblies that no longer exist.
* Build logic that sets MONO_PATH now points to mcs/class/lib/net_4_5
instead of mcs/class/lib/net_2_0.
|
|
|
|
This is not used anymore.
|
|
|
|
Added test case that proves this change (by baulig).
|
|
declaration.
|
|
A couple of the test suites didn't follow the MonoTests.<namespace of class under test> naming convention for the namespace.
|
|
They were once part of a special Java target profile, but this is no longer used today.
|
|
Fixes Xamarin Bug 16742: XmlConvert.ToDateTime(string, XmlDateTimeSeria...
|
|
|
|
|
|
|
|
XmlDateTimeSerializationMode) throws index out of bounds exception
Fix for bug + added tests for method
XmlConvert.ToDateTime(string, XmlDateTimeSerializationMode)
|
|
iOS devices). Use the temporary directory and open files in read-only
|
|
This reverts commit 93e2d1dc48339be472300910e9290939ee253177.
|
|
|
|
|
|
was not set (0h 0m 0s)
|
|
|
|
* The default implementation throws NotImplementedException.
* Added nunit tests.
|
|
|
|
- Move the setting of newline_handling early enough that Initialize()
can see it.
- Reduce the set of characters that trigger the slow path for
attribute values for the NewLineHandling.None case.
- Rewrite the handling of \t, \r and \n to match the MS docs
(which match the observed behavior of their implementation)
- Add some tests.
|
|
WriteWhitespace() is ignored.
|
|
to determine a string as an absolute URI.
It's a bit difficult decision, as the "relative URI" could be any path string
that contain colons as a *valid* path (especially on *nix land).
We historically did allow such string that contain "http:" etc. as to be
treated as absolute (which historically worked long time).
But this test case uncovered possible other cases.
Hopefully this does not bring issues that is pretty much anticipated. Such
issues could also happen in older code anyways.
|
|
|
|
|
|
|
|
Fixed bug #676020.
|
|
|
