Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

./tests/.libs/tests: not found #139

Open
binarymaster opened this issue Nov 30, 2022 · 1 comment
Open

./tests/.libs/tests: not found #139

binarymaster opened this issue Nov 30, 2022 · 1 comment

Comments

@binarymaster
Copy link
Member

Noticed it while porting Travis CI build script to GitHub Actions.

If I understand correctly, tests is a binary which subsequently starts all tests, and which also have some parameters for debugging (e.g. ./tests/.libs/tests --no_catch_system_errors).

It has been introduced in 2016 (3fd66d6), however it doesn't exist anymore. Perhaps it has been changed in the automake tools at some point.

See following lines here:

if [[ ${{ runner.os }} == "Linux" ]]; then

I have encountered test crashes on macOS (reported in #138), but it doesn't seem to affect the ability to obtain stack traces there. It may affect Linux builds though.

Cc @SoapGentoo and @Malvineous

@mywave82
Copy link
Contributor

mywave82 commented Mar 5, 2023

There has been changes in the past in the structure
dabd423

Most likely, automake "check" feature has changed a lot in the internal design. The current modern version atleast seems to be driven by sh scripts that are project agnostic.

Looking at adplug/.github/workflows/build.yml , it seems like it assumes that core dumping is default enabled for Linux, which has been untrue for most Linux distributions for some time.

Last problem is that the current test-suite is running multiple different programs, so if we are to use the core-dump, it needs to be matched with the correct binary.

Possible "workaround" would be for the tests to always be ran in the context of gdb/lldb if present already from automake view some-how

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants