Unit tests crash on Mac OS 10.13

[garyo]

I'm running on a Macbook Pro, MacOS 10.13.4, Core i5, 8GB RAM, Intel Iris graphics. After installing deps with homebrew and building Baikal, the basic standalone viewer works fine with the Cornell box. But it crashes on the Classroom sample. Also the unit tester BaikalTest crashes:

(venv) dev-mac (~/dss/product/Radeon-Rays/RadeonProRender-Baikal/BaikalTest [master]) 11:20AM 2963=>
% ../build/bin/BaikalTest
[==========] Running 79 tests from 9 test cases.
[----------] Global test environment set-up.
[----------] 1 test from InternalTest
[ RUN      ] InternalTest.Distribuiton1D
[       OK ] InternalTest.Distribuiton1D (0 ms)
[----------] 1 test from InternalTest (0 ms total)

[----------] 2 tests from BasicTest
[ RUN      ] BasicTest.Init
[       OK ] BasicTest.Init (961 ms)
[ RUN      ] BasicTest.RenderTestScene
Program compilation time: 673 ms
Program compilation time: 315 ms
Program compilation time: 2801 ms
[2]    59853 segmentation fault  ../build/bin/BaikalTest

The stack trace from running Baikal standalone with the Classroom sample is this:

hread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libBaikalIO.dylib             	0x000000010e4e49ad tinyxml2::XMLNode::FirstChildElement(char const*) const + 13
1   libBaikalIO.dylib             	0x000000010e494f33 Baikal::MaterialIoXML::LoadMaterials(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) + 931
2   BaikalStandalone              	0x000000010e2baca8 Baikal::AppClRender::LoadScene(Baikal::AppSettings&) + 968
3   BaikalStandalone              	0x000000010e2b9e15 Baikal::AppClRender::AppClRender(Baikal::AppSettings&, unsigned int) + 533
4   BaikalStandalone              	0x000000010e2b11fd Baikal::Application::Application(int, char**) + 813
5   BaikalStandalone              	0x000000010e31a054 main + 36
6   libdyld.dylib                 	0x00007fff53981015 start + 1

[yozhijk]

@garyo UnitTest data on the web has not yet been updated to use new Uber material, we will fix that, thanks