apache / apache/gluten

VeloxExpandSuite failed by memory in CI

Open
#11,446 1 comment 0 reactions 0 assignees View on GitHub
bug triage
Dominant language
Scala
Stars
1.6k
Forks
657
Avg merge
2d 21h
Merged PRs (30d)
85

Description

### Backend

VL (Velox)

### Bug description

https://github.com/apache/incubator-gluten/actions/runs/21128265789/job/60753851957?pr=11441
```

org.apache.spark.sql.execution.VeloxExpandSuite *** ABORTED ***
java.lang.NullPointerException: Cannot invoke "org.apache.spark.memory.MemoryManager.maxOnHeapStorageMemory()" because the return value of "org.apache.spark.storage.BlockManager.memoryManager()" is null
at org.apache.spark.storage.BlockManager.maxOnHeapMemory$lzycompute(BlockManager.scala:244)
at org.apache.spark.storage.BlockManager.maxOnHeapMemory(BlockManager.scala:244)
at org.apache.spark.storage.BlockManager.initialize(BlockManager.scala:566)
at org.apache.spark.SparkContext.(SparkContext.scala:643)
at org.apache.spark.SparkContext.(SparkContext.scala:147)
at org.apache.spark.sql.test.TestSparkSession.(TestSQLContext.scala:30)
at org.apache.spark.sql.test.SharedSparkSessionBase.createSparkSession(SharedSparkSession.scala:110)
at org.apache.spark.sql.test.SharedSparkSessionBase.createSparkSession$(SharedSparkSession.scala:108)
at org.apache.gluten.execution.WholeStageTransformerSuite.createSparkSession(WholeStageTransformerSuite.scala:34)
at org.apache.spark.sql.test.SharedSparkSessionBase.initializeSession(SharedSparkSession.scala:126)
...
```

### Gluten version

_No response_

### Spark version

None

### Spark configurations

_No response_

### System information

_No response_

### Relevant logs

```bash

```

Contributor guide

Open the contributing guide

Research direction

Start with the failed CI job and the VeloxExpandSuite.createSparkSession entry point in WholeStageTransformerSuite.scala:34, then follow SharedSparkSessionBase.createSparkSession and SparkContext initialization in the stack trace. Reproduce the failure in the affected test suite and confirm that VeloxExpandSuite initializes successfully without the reported memory-manager exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
backend, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.