libignition-physics v5_5.0.0

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date. Notes for merging this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version. Checklist before merging this PR:
   • [ ] Dependencies have been updated if changed: see upstream
   • [ ] Tests have passed
   • [ ] Updated license if changed and license_file is packaged

Note that the bot will stop issuing PRs if more than 3 Version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.

NEW: If you want these PRs to be merged automatically, make an issue with code>@conda-forge-admin,</codeplease add bot automerge in the title and merge the resulting PR. This command will add our new bot automerge feature to your feedstock!

Closes: #20

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase code>@<space/conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable. Finally, feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/autotick-bot/actions/runs/1294258038, please use this URL for debugging}

Dependency Analysis

We couldn't run dependency analysis due to an internal error in the bot. :( Help is very welcome!

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[traversaro]

%PREFIX%\Library\include\eigen3\Eigen\src\Core\CoreEvaluators.h(910) : fatal error C1002: compiler is out of heap space in pass 2

These are the great errors that one loves. : )

[Tobias-Fischer]

Should we just remove the offending tests?

[traversaro]

Should we just remove the offending tests?

Yes, I think it make sense.

[traversaro]

Should we just remove the offending tests?

Yes, I think it make sense.

I actually now tried to force the use of just one build and to avoid parallel builds, let's see if that improves the situation.

[traversaro]

Should we just remove the offending tests?

Yes, I think it make sense.

I actually now tried to force the use of just one build and to avoid parallel builds, let's see if that improves the situation.

Build seems to be stuck since 1 hour at:

[47/161] cmd.exe /C "cd . && %BUILD_PREFIX%\Library\bin\cmake.exe -E vs_link_exe --intdir=test\integration\CMakeFiles\INTEGRATION_ExamplesBuild_TEST.dir --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100220~1.0\x64\rc.exe --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100220~1.0\x64\mt.exe --manifests  -- C:\PROGRA~2\MICROS~2\2019\ENTERP~1\VC\Tools\MSVC\1429~1.301\bin\Hostx64\x64\link.exe  test\integration\CMakeFiles\INTEGRATION_ExamplesBuild_TEST.dir\ExamplesBuild_TEST.cc.obj  /out:bin\INTEGRATION_ExamplesBuild_TEST.exe /implib:lib\INTEGRATION_ExamplesBuild_TEST.lib /pdb:bin\INTEGRATION_ExamplesBuild_TEST.pdb /version:0.0 /machine:x64 /INCREMENTAL:NO /subsystem:console  lib\ignition-physics5.lib  lib\gtest.lib  lib\gtest_main.lib  %PREFIX%\Library\lib\ignition-math6.lib  %PREFIX%\Library\lib\ignition-utils1.lib  lib\gtest.lib  %PREFIX%\Library\lib\ignition-plugin1-loader.lib  %PREFIX%\Library\lib\ignition-plugin1.lib  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib &&...

[traversaro]

Incredible, in the end the Windows build took 3h 18m 31s (against ~15m for Linux/macOS) but it ended successful and the test passed. So the idea of using just one thread worked, but I do not think it is convenient in practice. I will merge this PR and then open a new one to exclude the integration test and reduce the Windows build time.