Bug Description
The PR tcp-benchmark-compile CI job has no repository-level timeout around its configure/build path. If TCP benchmark configure or target build hangs, the job can occupy CI until the GitHub Actions platform default timeout instead of failing within a repo-controlled bound.
Environment
- Elio Version: main at
d7b1d521f57d2931a59f597a2d6fb39b83025f69
- Compiler: GitHub Actions CI
- OS: Ubuntu 24.04 GitHub Actions runner
- Kernel Version: GitHub-hosted runner kernel
- Build Type: Release TCP benchmark compile job
- CMake Version: GitHub Actions runner CMake
Build and Dependency Configuration
- Full CMake configure command:
.github/workflows/ci.yml Configure TCP benchmark build
- Changed
ELIO_* options: ELIO_BUILD_EXAMPLES=ON, ELIO_BUILD_TCP_BENCHMARKS=ON, TLS/HTTP/HTTP2 disabled
- Consumption mode: source checkout in GitHub Actions PR CI
- Relevant logs: static workflow review
Steps to Reproduce
- Open a PR that changes TCP benchmark-affecting paths.
- Let
tcp-benchmark-compile run.
- If configure or build stalls, observe that the job has no explicit
timeout-minutes or command-level timeout bound.
Minimal Reproducible Example
Not a code API issue; this is visible in .github/workflows/ci.yml.
Expected Behavior
The TCP benchmark compile job should have an explicit repository-controlled timeout appropriate for a compile-only check.
Actual Behavior
tcp-benchmark-compile runs CMake configure and build without an explicit job or command timeout.
Error Messages
Not applicable.
ASAN/TSAN Output
Not applicable.
Additional Context
Evidence:
.github/workflows/ci.yml defines tcp-benchmark-compile at the job level.
- Its configure/build steps run CMake directly.
- The job lacks
timeout-minutes, and those steps are not wrapped with shell timeout.
- Other benchmark runtime steps in CI do use explicit command-level timeout wrappers.
Related Issues
Possible Solution
Add a concrete timeout-minutes to tcp-benchmark-compile, or wrap the configure/build commands with fixed shell timeouts.
Checklist
Bug Description
The PR
tcp-benchmark-compileCI job has no repository-level timeout around its configure/build path. If TCP benchmark configure or target build hangs, the job can occupy CI until the GitHub Actions platform default timeout instead of failing within a repo-controlled bound.Environment
d7b1d521f57d2931a59f597a2d6fb39b83025f69Build and Dependency Configuration
.github/workflows/ci.ymlConfigure TCP benchmark buildELIO_*options:ELIO_BUILD_EXAMPLES=ON,ELIO_BUILD_TCP_BENCHMARKS=ON, TLS/HTTP/HTTP2 disabledSteps to Reproduce
tcp-benchmark-compilerun.timeout-minutesor command-leveltimeoutbound.Minimal Reproducible Example
Not a code API issue; this is visible in
.github/workflows/ci.yml.Expected Behavior
The TCP benchmark compile job should have an explicit repository-controlled timeout appropriate for a compile-only check.
Actual Behavior
tcp-benchmark-compileruns CMake configure and build without an explicit job or command timeout.Error Messages
Not applicable.
ASAN/TSAN Output
Not applicable.
Additional Context
Evidence:
.github/workflows/ci.ymldefinestcp-benchmark-compileat the job level.timeout-minutes, and those steps are not wrapped with shelltimeout.Related Issues
Possible Solution
Add a concrete
timeout-minutestotcp-benchmark-compile, or wrap the configure/build commands with fixed shell timeouts.Checklist