Re: Reflection Issue

.135 was 2017-06 commit 6425f06ff697f516990729d3f4058f10e68966ef
.167 was 2017-06 commit 6b8abfeb7cc89e512f4b6da927d1012ea6e7360f

I think mono --version should include the commit id but that depends on how Mono was built (source tarballs from https://download.mono-project.com/sources/mono/ should include the commit in the version output, as do git checkout builds).

-Aleksey

On 8/29/17, 16:04, "Mono-devel-list on behalf of Neale Ferguson" <[email protected]<mailto:[email protected]> on behalf of [email protected]<mailto:[email protected]>> wrote:

Somewhere between 5.4.0.135 and .167 something has changed that causes a
customer test to fail while doing reflection. Is there a commit number
that corresponds to those levels such that we can do a bisect?

Neale

_______________________________________________
Mono-devel-list mailing list
[email protected]<mailto:[email protected]>
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.dot.net%2Fmailman%2Flistinfo%2Fmono-devel-list&data=02%7C01%7Calklig%40microsoft.com%7C591a16c88f61490643c408d4ef191fc5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636396338595025476&sdata=7O4ed6fr9BJky4zTFGejI09GtwkdyuX%2FnrjULzO5odI%3D&reserved=0

_______________________________________________
Mono-devel-list mailing list
[email protected]
http://lists.dot.net/mailman/listinfo/mono-devel-list