osrm-backend/test/data/profiles
Matthew Wigginton Bhagat-Conway d6afe91d8f
print tracebacks and line numbers for Lua runtime errors (#6564)
* print tracebacks and line numbers for Lua runtime errors

* revert format changes

* update changelog with lua traceback, #6564

* revert using protected_function for old GetStringListFromFunction and source_function #6564

* add unit test for line numbers in tracebacks, #6564

* apply clang-format (#6564)

* remove unused test helper function, #6564

* suppress leaksanitizer warnings in extract-tests, #6564

When the extractor encounters a lua runtime error, some osmium objects are not freed. In production this doesn't matter because these errors bring down OSRM. In the tests we catch them to ensure they occur, and the leaksanitizer flags them.
2023-03-23 19:18:58 +01:00
..
bad_node.lua print tracebacks and line numbers for Lua runtime errors (#6564) 2023-03-23 19:18:58 +01:00
bad_segment.lua print tracebacks and line numbers for Lua runtime errors (#6564) 2023-03-23 19:18:58 +01:00
bad_setup.lua print tracebacks and line numbers for Lua runtime errors (#6564) 2023-03-23 19:18:58 +01:00
bad_turn.lua print tracebacks and line numbers for Lua runtime errors (#6564) 2023-03-23 19:18:58 +01:00
bad_way.lua print tracebacks and line numbers for Lua runtime errors (#6564) 2023-03-23 19:18:58 +01:00