testng-team/testng

The GraphOrchestrator afterExecute method should handle null IWorker<T> r parameter

Open

#3,243 opened on Oct 6, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Java (1,025 forks)github user discovery
Feature: parallelgood first issue

Repository metrics

Stars
 (2,053 stars)
PR merge metrics
 (PR metrics pending)

Description

In some rare cases when exception occurs during runtime in the TestNGFutureTask in this line https://github.com/testng-team/testng/blob/d50b2ad2d6809d52131a07071fe229b1b901e08c/testng-core/src/main/java/org/testng/internal/thread/graph/TestNGFutureTask.java#L30 then the result remains null. The BiConsumer should handle null first param. It causes NPE and the real exception remains hidden. Just via debug you can find the real problem.

Please fix this.

Contributor guide

Research direction
Inspect the GraphOrchestrator.afterExecute method and add a null check for the IWorker<T> r parameter to prevent NPE.
Tech stack
java
Domain
testing
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Java
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60