skills.rest
jbalcomb
jbalcombCOMMUNITY
Explore all skills by this author →
GitHub

terminate-stuck-test-executables

Terminate stuck Windows test executables from CTest configs after user confirmation.

26|3|Updated Feb 17, 2021
Search Tags:#build automation#Windows#CTest#termination#stuck executables
One-click install
npx skills add https://github.com/jbalcomb/ReMoM --skill terminate-stuck-test-executables
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: terminate-stuck-test-executables
Source: https://github.com/jbalcomb/ReMoM/tree/main/.claude/skills/terminate-stuck-test-executables
Command: npx skills add https://github.com/jbalcomb/ReMoM --skill terminate-stuck-test-executables

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps users safely terminate stuck test executables that block rebuilds or CTest runs on Windows, allowing continuous development and testing processes.

Core Features & Use Cases

  • Detect and terminate stuck executables: Automatically identify and terminate any executable that is blocking the rebuild or CTest run on Windows.
  • User confirmation required: Always asks the user for permission before terminating any executable to ensure safety.
  • List discovered executables: Optionally lists all discovered executables without terminating them, giving users an overview.

Quick Start

Run the script with the path to the build directory and the executable name to terminate it, or use the --list flag to see all discovered executables.

Frequently Asked Questions about terminate-stuck-test-executables

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I terminate stuck test executables blocking a CTest run on Windows?▼

To terminate stuck test executables on Windows, this Skill reads the executable list from the generated CTest config, identifies the blocked binaries, and asks for your permission before safely killing the processes.

Why does my build automation fail when a test binary is locked or still running?▼

Build automation fails when a test binary is locked or still running because the stuck executable blocks rebuilds and continuous CTest runs. This Skill resolves the blockage by detecting and terminating the offending process.

Can I list discovered executables in a CTest build directory without terminating them?▼

Yes, you can list discovered executables without terminating them by running the script with the build directory path and the `--list` flag, giving you an overview of all discovered test binaries.

Does this process automatically kill stuck executables without user confirmation?▼

No, the process does not automatically kill stuck executables. It always requires user confirmation and asks for your explicit permission before terminating any identified executable to ensure system safety.

What is the best way to safely stop a locked test executable during a Windows build?▼

The best way to safely stop a locked test executable is to use a script that reads the CTest config, targets the specific locked binary, and requests user permission before terminating the process to accelerate the build flow.

Related Skills

Explore More Software Engineering Skills→
robwestzrobwestz

repo-rescue

Automate a five-phase workflow to diagnose and fix broken repositories.

Community
Advanced
hector-mannyhector-manny

cpp-testing

Configure and automate C++ testing workflows with GoogleTest, GoogleMock, and CTest.

Community
Advanced
mbadozmbadoz
2

cpp-testing

Automate C++ test setup, execution, and validation with GoogleTest/CTest and CMake.

Community
Advanced
steelan9199steelan9199
9

win11-program-launcher

Generate Windows batch scripts using start and taskkill for application launch and termination.

Community
Basic