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 second command should drop a `chalk` binary that is usable by tests. You can also manually build with `nimble build`, but this is not recommended as it doesn't guarantee that the architecture will be compatible with the `tests` container.
WARNING: Debug builds are very slow, so it is not recommended to run the entire test suite on a debug build.
but that doesn't seem to work:
$ git clone --depth 1 https://github.com/crashappsec/chalk /tmp/chalk
$ cd /tmp/chalk
$ git log -1 --onelineca217bd (grafted, HEAD -> main, origin/main, origin/HEAD) test(fd_cache): make tests self-contained, and enable in CI (#276)
$ make debugrm -f chalk chalk.bckmake chalkmake[1]: Entering directory '/tmp/chalk'cp CHANGELOG.md src/docs/CHANGELOG.mddocker compose run --rm chalk nimble -y build[...]+ strip chalk+ ./chalk --debug --no-use-external-config --skip-command-report load default[...]make[1]: Leaving directory '/tmp/chalk'
$ file chalkchalk: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped
The fact that strip runs above shows that -d:debug isn't passed to nimble build:
Thanks. That does cause make debug to pass --define:debug to the build command, with the output containing:
docker compose run --rm chalk nimble -y build --define:debug
However, strip still runs. Unfortunately, it turns out that nimble still doesn't support checking a custom define in the nimble file (see upstream ticket).
The
README.md
for the pytest-based testing says thatmake debug
is the way to produce a debug build of chalk:chalk/tests/functional/README.md
Lines 47 to 55 in ca217bd
but that doesn't seem to work:
The fact that
strip
runs above shows that-d:debug
isn't passed tonimble build
:chalk/chalk.nimble
Lines 78 to 81 in 46ffecd
In the
Makefile
:chalk/Makefile
Lines 47 to 52 in ca217bd
The text was updated successfully, but these errors were encountered: