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.

Sign up for GitHub

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

Jump to bottom

Support @TEST-ENV #112

Open
awelzel opened this issue Feb 3, 2025 · 0 comments
Open

Support @TEST-ENV #112

awelzel opened this issue Feb 3, 2025 · 0 comments

Comments

@awelzel
Copy link
Contributor

awelzel commented Feb 3, 2025

In certain cases, it could be useful to set an environment variable for all TEST-EXEC / TEST-EXEC-FAIL commands.

Instead of repeating it on each line, I wonder if @TEST-ENV could be a useful keyword.

# @TEST-ENV: OPENSSL_ENABLE_SHA1_SIGNATURES=1

# @TEST-EXEC: zeek -b ...
# @TEST-EXEC: zeek -b ...

Thoughts? I wonder how often this comes up? Setting a custom canonifier for btest-diff is another case where I could see that useful.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@awelzel