209a3bf302
Some logic to detect what libc the c / cxx compilers use by default, based on `-dynamic-linker`. The function `compiler.default_libc()` returns a `Spec` of the form `glibc@x.y` or `musl@x.y` with the `external_path` property set. The idea is this can be injected as a dependency. If we can't run the dynamic linker directly, fall back to `ldd` relative to the prefix computed from `ld.so.`
19 lines
982 B
INI
19 lines
982 B
INI
# content of pytest.ini
|
|
[pytest]
|
|
addopts = --durations=30 -ra --strict-markers
|
|
testpaths = lib/spack/spack/test
|
|
python_files = *.py
|
|
filterwarnings =
|
|
ignore::UserWarning
|
|
markers =
|
|
db: tests that require creating a DB
|
|
maybeslow: tests that may be slow (e.g. access a lot the filesystem, etc.)
|
|
regression: tests that fix a reported bug
|
|
requires_executables: tests that requires certain executables in PATH to run
|
|
nomockstage: use a stage area specifically created for this test, instead of relying on a common mock stage
|
|
enable_compiler_verification: enable compiler verification within unit tests
|
|
enable_compiler_execution: enable compiler execution to detect link paths and libc
|
|
disable_clean_stage_check: avoid failing tests if there are leftover files in the stage area
|
|
only_clingo: mark unit tests that run only with clingo
|
|
only_original: mark unit tests that are specific to the original concretizer
|
|
not_on_windows: mark tests that are skipped on Windows
|