-
Notifications
You must be signed in to change notification settings - Fork 98
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
Expand ${variable}
in benchcomp variant env
#2981
Labels
[C] Feature / Enhancement
A new feature request or enhancement to an existing feature.
Comments
karkhaz
added
the
[C] Feature / Enhancement
A new feature request or enhancement to an existing feature.
label
Jan 22, 2024
karkhaz
added a commit
to karkhaz/kani
that referenced
this issue
Mar 18, 2024
The values of environment variables in the benchcomp configuration file can now contain strings of the form '${var}'. Benchcomp will replace these strings with the value of the environment variable 'var'. This is intended to allow users to have several benchcomp variants, each of which differs only in the environment. This fixes model-checking#2981.
karkhaz
added a commit
to karkhaz/kani
that referenced
this issue
Mar 18, 2024
The values of environment variables in the benchcomp configuration file can now contain strings of the form '${var}'. Benchcomp will replace these strings with the value of the environment variable 'var'. This is intended to allow users to have several benchcomp variants, each of which differs only in the environment. This fixes model-checking#2981.
karkhaz
added a commit
to karkhaz/kani
that referenced
this issue
Mar 18, 2024
The values of environment variables in the benchcomp configuration file can now contain strings of the form '${var}'. Benchcomp will replace these strings with the value of the environment variable 'var'. This is intended to allow users to have several benchcomp variants, each of which differs only in the environment. This fixes model-checking#2981.
karkhaz
added a commit
to karkhaz/kani
that referenced
this issue
Mar 19, 2024
The values of environment variables in the benchcomp configuration file can now contain strings of the form '${var}'. Benchcomp will replace these strings with the value of the environment variable 'var'. This is intended to allow users to have several benchcomp variants, each of which differs only in the environment. This fixes model-checking#2981.
karkhaz
added a commit
to karkhaz/kani
that referenced
this issue
Mar 19, 2024
The values of environment variables in the benchcomp configuration file can now contain strings of the form '${var}'. Benchcomp will replace these strings with the value of the environment variable 'var'. This is intended to allow users to have several benchcomp variants, each of which differs only in the environment. This fixes model-checking#2981.
karkhaz
added a commit
to karkhaz/kani
that referenced
this issue
Mar 19, 2024
The values of environment variables in the benchcomp configuration file can now contain strings of the form '${var}'. Benchcomp will replace these strings with the value of the environment variable 'var'. This is intended to allow users to have several benchcomp variants, each of which differs only in the environment. This fixes model-checking#2981.
tautschnig
pushed a commit
that referenced
this issue
Mar 22, 2024
The values of environment variables in the benchcomp configuration file can now contain strings of the form '${var}'. Benchcomp will replace these strings with the value of the environment variable 'var'. This is intended to allow users to have several benchcomp variants, each of which differs only in the environment. This fixes #2981.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Requested feature: The value of the
env
key in Benchcomp's config file should expand strings of the form${variable}
to the value of that environment variable.Use case: Benchcomp variants often require a different value of
$PATH
for each variant. Currently users set$PATH
in thecommand_line
, which obscures the difference between variants. This feature would allow the user to do this:Link to relevant documentation (Rust reference, Nomicon, RFC): N/A
Test case:
Running benchcomp with the below config file should terminate successfully. Note that
${USER}
is assumed to be set by the Unix session so should always be available, and thewhoami
command is also assumed to be available.The text was updated successfully, but these errors were encountered: