Mono.Options test no longer builds
Vincent Povirk <[email protected]> Mon, 1 May 2017 15:09:16 -0500
| Newsgroups | gmane.comp.gnome.mono.devel |
|---|---|
| Message-ID | <CAG_NDKo9a80K1+H1xVSiG+B=-mKVyH=6G6AFY9qx69VzOykWbQ@mail.gmail.com> |
The Mono.Options tests no longer compile for the net_4_x profile after this commit: https://github.com/mono/mono/commit/7e2571ed334e9cee3f0d3bafeef02852310f4d3b This is because the test depends on the constructor that was removed. I don't think the test should be changed because it correctly indicates that the API was broken. I have 2 questions. 1. Was there any good reason to change the existing constructor in the net_4_x profile? After the commit, we still have a constructor that provides the functionality that's missing from PCL, in the net_4_x profile. So why switch to doing it in a different way? 2. Why didn't continuous integration catch this? The test isn't even failing, it's not building at all. This shouldn't be difficult for an automated system to notice. _______________________________________________ Mono-devel-list mailing list [email protected] http://lists.dot.net/mailman/listinfo/mono-devel-list