All issues

Search results

Service startup errors should identify the failing service

Status: Open.

#93 In hermeticbuild/rules_itest;

· Spikhalskiy opened on Sep 7, 2026

Command health checks can hang on inherited output pipes

Status: Open.

#92 In hermeticbuild/rules_itest;

· Spikhalskiy opened on Sep 7, 2026

Any experimentation with providing services as containers?

Status: Open.

#87 In hermeticbuild/rules_itest;

· kayliespace opened on Aug 28, 2026

Proposal: opt-in lazy shared services for independent test-suite members

Status: Open.

#74 In hermeticbuild/rules_itest;

· yaroslavvoloshchuk-codaio opened on Jul 19, 2026

data race

Status: Open.

#71 In hermeticbuild/rules_itest;

· blampe opened on Jun 17, 2026

Allow for swapping out services with externally-provided ones

Status: Open.

#70 In hermeticbuild/rules_itest;

· scottpledger opened on Jun 16, 2026

Support a port reservation system?

Status: Open.

#61 In hermeticbuild/rules_itest;

· jasonprado opened on Feb 10, 2026

Killing a run service doesn't cause svcinit to fail

Status: Open.

#60 In hermeticbuild/rules_itest;

· samschlegel opened on Feb 5, 2026

when running an itest_service, exec.CommandContext sends SIGKILL before graceful shutdown can run

Status: Open.

#58 In hermeticbuild/rules_itest;

· samschlegel opened on Feb 5, 2026

Test args are not respected by service_test

Status: Open.

#54 In hermeticbuild/rules_itest;

· engnatha opened on Nov 21, 2025

Resource allocation?

Status: Open.

#37 In hermeticbuild/rules_itest;

· manuelnaranjo opened on Oct 23, 2024

How are multiple dependencies on one itest_service handled?

Status: Open.

#27 In hermeticbuild/rules_itest;

· peakschris opened on Aug 27, 2024