Skip to content

Commit

Permalink
Changelog and documentation for BenchExec 3.14
Browse files Browse the repository at this point in the history
  • Loading branch information
PhilippWendler committed Nov 7, 2022
1 parent aae8eb3 commit 010afd3
Show file tree
Hide file tree
Showing 2 changed files with 24 additions and 2 deletions.
21 changes: 21 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,27 @@ SPDX-License-Identifier: Apache-2.0

# BenchExec Changelog

## BenchExec 3.14

- Added a workaround for the known glibc deadlock described in [#656](https://github.com/sosy-lab/benchexec/issues/656).
In most cases BenchExec should detect the deadlock
and continue benchmarking after a timeout of 60s.
- We noticed a [performance problem in Python](https://github.com/python/cpython/issues/98493)
that affects `benchexec` in container mode on machines with many cores
and added an optimization that reduces its impact.
- Improved handling of non-existent mount points.
This makes BenchExec easier to use within Podman containers,
and we now recommend Podman over Docker in our
[documentation](https://github.com/sosy-lab/benchexec/blob/main/doc/container.md#using-benchexec-in-a-dockerpodman-container).
- `table-generator` no longer attempts to spawn a large number of threads
(failing due to the limit on open files)
on machines with many cores.
- Many new and improved tool-info modules.

This release does not change the minimum supported Python version,
but we would like to remind you
that BenchExec will soon stop supporting Python 3.6.

## BenchExec 3.13

- More robust handling of child cgroups created within a run
Expand Down
5 changes: 3 additions & 2 deletions doc/container.md
Original file line number Diff line number Diff line change
Expand Up @@ -268,8 +268,9 @@ such as `--hidden-dir` or `--read-only-dir`.

### BenchExec sometimes hangs if many parallel runs are executed
This happens if we clone the Python process while it is in an inconsistent state.
Make sure to use BenchExec 1.22 or newer,
where [#435](https://github.com/sosy-lab/benchexec/issues/435) is fixed.
Make sure to use BenchExec 3.14 or newer,
where [#435](https://github.com/sosy-lab/benchexec/issues/435) is fixed
and a workaround for [#656](https://github.com/sosy-lab/benchexec/issues/656) is present.
If it still occurs, please attach to all child process of BenchExec
with `sudo gdb -p <PID>`, get a stack trace with `bt`,
and [report an issue](https://github.com/sosy-lab/benchexec/issues/new) with as much information as possible.
Expand Down

0 comments on commit 010afd3

Please sign in to comment.