ice0
ice0
@rodolforg `std::cerr.precision(8)` is just not enough to show the problem here. I changed it to `12` so now it shows more precise values: ``` expected 2, but got 1.99999998097 ```...
@nattymbt Hi! Can you describe the original issue?
@morevnaproject @rodolforg any ideas here?
It ~should~ fails on synfig tests. @rodolforg please check.
> > Yes, it fails for `synfig::Node`. > > Question is: should we remove the test or fix the (possible) problem? It's up to you. You can comment it until...
> Sadly we can't see the exact failing test :( I didn't check it, but I thought it was `app_layerduplicate` ``` make[2]: Entering directory '/home/runner/work/synfig/synfig/_debug/synfig-studio/test' make[3]: Entering directory '/home/runner/work/synfig/synfig/_debug/synfig-studio/test' FAIL:...
Interesting. It's the same test. It fails, but not always: ``` ➜ build ctest --output-on-failure -R test_synfig_node Test project /home/ice/projects/synfig/build Start 12: test_synfig_node 1/1 Test #12: test_synfig_node ................. Passed 0.01...
> What is the clock() resolution? We are using `std::chrono::steady_clock` for `clock`. (https://en.cppreference.com/w/cpp/chrono/steady_clock) It's resolution is not defined, but it looks it should be nanoseconds on Linux. ``` struct steady_clock...
> So do we have a way to fix it? :( Sure. I will back to it soon.
@sharewithvirus In 1.5.1 Lottie exporter moved to Export menu:  