Hyperrefs in table-generator tables

[matthiaskettl]

Table generator provides the possibility to include hard-coded hrefs in the table definitions.
Example from SV-COMP:

<?xml version='1.0' ?>
<!DOCTYPE table PUBLIC "+//IDN sosy-lab.org//DTD BenchExec table 1.0//EN"
        "http://www.sosy-lab.org/benchexec/table-1.0.dtd">
<table>
    <!-- .... -->
    <column title="witness" href="PLACEHOLDER">wit</column>
    <column title="inspect witness" href="PLACEHOLDER">inspect</column>
    <!-- .... -->

    <!-- result files -->
</table>

In this case, table generator will create hyperrefs to "PLACEHOLDER" which we have to replace retrospectively and manually with a post-processing script.

It would be convenient to have the possibility to make the href dependent on the value of the current column and row. This could, for example, look like this:

<?xml version='1.0' ?>
<!DOCTYPE table PUBLIC "+//IDN sosy-lab.org//DTD BenchExec table 1.0//EN"
        "http://www.sosy-lab.org/benchexec/table-1.0.dtd">
<table>
    <!-- .... -->
    <column title="witness" href="${value}">wit</column>
    <column title="inspect witness" href="${value}">inspect</column>
    <!-- .... -->

    <!-- result files -->
</table>

[saurabh12nxf]

Hi! @matthiaskettl I'd like to work on this issue.

I understand that currently, the table generator requires post-processing scripts to replace placeholder hrefs, and this feature would allow dynamic href generation using variables like ${value} to reference the current cell's content.

My approach would be:

Investigate the current href handling in the table generator code
Implement variable substitution for the href attribute (starting with ${value})
Ensure backward compatibility with existing hard-coded hrefs
Add tests to verify the functionality
Update documentation if needed
Could you please assign this issue to me? I'm excited to contribute!

[anaslari23]

Hi @matthiaskettl ,

I’d like to take up this issue if it’s still open.

My plan is to:

• Analyze the current logging flow in BenchExec and identify where excessive output is generated.
• Introduce clearer control over log verbosity using Python’s logging levels.
• Ensure that certain failure conditions cause BenchExec to stop early with a clear error message instead of continuing execution.
• Add/update tests to validate both reduced logging output and correct fail-fast behavior.

I’ll keep the changes minimal, backward-compatible, and well-tested.
Please let me know if this approach sounds reasonable or if you’d prefer a specific direction before I start.

Thanks!

[anaslari23]

I have submitted a Pull Request (#1246) that implements support for value-dependent hyperlinks using the ${value} placeholder in the table generator.

The implementation:

• Updates _create_link to support ${value} substitution.
• • Passes cell values from prepare_value and clean_up_results.
• • • Includes unit tests for the substitution logic.
• • • • Maintains backward compatibility for static strings.
        I've verified the changes with tests on my local environment. Looking forward to your feedback!