Open jbcoe opened 6 years ago
dotnet tests take considerably longer than any others (including Java). This seems odd and should be at least understood if not amended.
Test project /Users/jon/DEV/FFIG/build Start 1: test_cppmodel 1/15 Test #1: test_cppmodel .................... Passed 0.63 sec Start 2: test_python_bindings 2/15 Test #2: test_python_bindings ............. Passed 0.57 sec Start 3: test_cpp_mocks 3/15 Test #3: test_cpp_mocks ................... Passed 0.01 sec Start 4: test_cpp_circle 4/15 Test #4: test_cpp_circle .................. Passed 0.01 sec Start 5: test_tree_capi 5/15 Test #5: test_tree_capi ................... Passed 0.01 sec Start 6: test_cpp_tree 6/15 Test #6: test_cpp_tree .................... Passed 0.01 sec Start 7: test_dotnet_shape_output 7/15 Test #7: test_dotnet_shape_output ......... Passed 0.06 sec Start 8: test_dotnet_tree_output 8/15 Test #8: test_dotnet_tree_output .......... Passed 0.05 sec Start 9: test_dotnet 9/15 Test #9: test_dotnet ...................... Passed 2.71 sec Start 10: test_java_asset 10/15 Test #10: test_java_asset .................. Passed 0.00 sec Start 11: test_d_tree_output 11/15 Test #11: test_d_tree_output ............... Passed 0.05 sec Start 12: test_swift_tree_output 12/15 Test #12: test_swift_tree_output ........... Passed 0.04 sec Start 13: test_asset_lua 13/15 Test #13: test_asset_lua ................... Passed 0.00 sec Start 14: test_ruby_bindings 14/15 Test #14: test_ruby_bindings ............... Passed 0.18 sec Start 15: test_go_Shape 15/15 Test #15: test_go_Shape .................... Passed 0.98 sec
dotnet tests take considerably longer than any others (including Java). This seems odd and should be at least understood if not amended.