[CI] issue: 4684071Terminate Valgrind gracefully

[NirWolfer]

Description

Valgrind today is being terminated with -9 which prevents it from printing all the summaries at the end which are needed for debuging.

What

Change -9 signal to -SIGINT af the first try of shutting down Valgrind

Why ?

HPCINFRA-3989

How ?

It is optional but for complex PRs please provide information about the design,
architecture, approach, etc.

Change type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Tests
• Other

Check list

• Code follows the style de facto guidelines of this project
• Comments have been inserted in hard to understand places
• Documentation has been updated (if necessary)
• Test has been added (if possible)

[NirWolfer]

bot:retest

[NirWolfer]

bot:retest

[greptile-apps]

Greptile Summary

Changed Valgrind process termination signal from SIGKILL (-9) to SIGINT to allow graceful shutdown and enable Valgrind to print debugging summaries.

• Replaced pkill -9 with pkill -SIGINT on line 98 of contrib/jenkins_tests/vg.sh
• Existing fallback mechanism ensures reliability: escalates to SIGTERM after 10 seconds, then SIGKILL after 3 more seconds if needed
• Resolves HPCINFRA-3989 by preserving Valgrind output for debugging

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The change is a single-line fix that improves debugging capability without compromising functionality. The existing multi-level fallback mechanism (SIGINT → SIGTERM → SIGKILL) ensures processes are terminated even if graceful shutdown fails. The change aligns with best practices for process termination and has no impact on test logic or correctness.
• No files require special attention

Important Files Changed

Filename	Overview
contrib/jenkins_tests/vg.sh	Changed Valgrind termination from SIGKILL to SIGINT to allow graceful shutdown with fallback mechanism already in place

Sequence Diagram

sequenceDiagram
    participant Script as CI Script
    participant Process as Valgrind/sockperf
    participant System as Operating System
    
    Script->>Process: Start Valgrind with sockperf server
    Script->>Process: Start Valgrind with sockperf client
    Script->>Process: Run tests (10 seconds)
    
    alt Process still running
        Script->>System: pkill -SIGINT (graceful)
        System->>Process: Send SIGINT signal
        Process->>Process: Cleanup & print summaries
        Process-->>System: Exit gracefully
        Script->>Script: Wait 10 seconds
        
        alt SIGINT didn't work
            Script->>System: pkill -SIGTERM
            System->>Process: Send SIGTERM signal
            Process-->>System: Force exit
            Script->>Script: Wait 3 seconds
            
            alt SIGTERM didn't work
                Script->>System: pkill -SIGKILL
                System->>Process: Send SIGKILL signal
                Process--xSystem: Immediate termination
            end
        end
    end
    
    Script->>Script: Analyze Valgrind logs
    Script->>Script: Report results

Loading