You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Debian i386 build failed with the below test failure:
1024 8609792
2048 14700544
3072 14700544
4096 14700544
5120 11386880
6144 14532608
7168 14532608
8192 14761984
{ before = 8609792, after = 14761984 }
./tests/test-leaks.lua:24: assertion failed!
stack traceback:
[C]: in function 'assert'
./tests/test-leaks.lua:24: in upvalue 'bench'
./tests/test-leaks.lua:102: in field 'fn'
./lib/tap.lua:53: in function <./lib/tap.lua:42>
[C]: in function 'xpcall'
./lib/tap.lua:42: in upvalue 'run'
./lib/tap.lua:136: in function 'lib/tap'
tests/run.lua:35: in main chunk
not ok 25 leaks - reading file sync
This was with the app shim (dynamically linked against luv) I've previously mentioned. The test passed when using lua to directly run the tests.
The text was updated successfully, but these errors were encountered:
- Adds a 'Check' stage to the CI that runs before the general 'Test' stage
- Adds Valgrind check
- Adds LSAN/ASAN/UBSAN check
- Adds a "binding coverage" check script to catch any unbound functions when we update to new Libuv versions. Added the unbound functions in #410 as exceptions for now; they should be removed from the $skipped array as they are resolved.
- Deprecated test-leaks.lua and moved it to manual-test-leaks.lua since Valgrind/ASAN is much better at detecting leaks. This has a side benefit of speeding up our test suite a bit.
- Closes#395, #428, #429
The Debian i386 build failed with the below test failure:
This was with the app shim (dynamically linked against luv) I've previously mentioned. The test passed when using lua to directly run the tests.
The text was updated successfully, but these errors were encountered: