Closed MatthijsBurgh closed 1 year ago
The test don't seem to be run in GH actions. See https://github.com/jbeder/yaml-cpp/pull/1170 for that one. CI run on my fork: https://github.com/MatthijsBurgh/yaml-cpp/actions/runs/4074000407
Though that one show the added tests don't fail, which means we haven't found a way yet to reproduce the issue of #833 in a clean environment.
Although this test doesn't exposes the issue of #833, this is still a good addition to the tests.
Ping @jbeder
This should be a valid test for the issues described in https://github.com/jbeder/yaml-cpp/issues/833.
So these tests should fail. Otherwise these test are not valid or there is a different in how the tests are build versus how users build against this library.