apache / apache/lucene

Failing test: TestSpellChecking.testGeneratedSuggestions — ComparisonFailure with expected suggestion list

Open
#14,741 2 comments 0 reactions 0 assignees View on GitHub
type:bug
Dominant language
Java
Stars
3.6k
Forks
1.4k
Avg merge
2d 11h
Merged PRs (30d)
88

Description

### Description

I'm encountering a consistent test failure when running the following test:

```
org.apache.lucene.analysis.hunspell.TestSpellChecking.testGeneratedSuggestions
```

**Git hash**: `ca427071708e3b7d17bc654a31712a5cdbb1bd7d`

**System Info**:
- OS: Windows 10 10.0 amd64
- Java: Eclipse Adoptium 24.0.1 (64-bit)
- Locale: `kam`, Timezone: `Europe/Uzhgorod`
- CPUs: 1, Threads: 1

**Error**:
```
org.junit.ComparisonFailure: Suggester=default expected: Theater, Heather, T...> but was: Theater, Heather, T...>
```

**Reproduction Command**:
(Note: the original line printed had issues with quoting. Below is the corrected form)

```bash
gradlew :lucene:analysis:common:test --tests "org.apache.lucene.analysis.hunspell.TestSpellChecking.testGeneratedSuggestions" -Ptests.jvms=2 "-Ptests.jvmargs=-XX:+UseParallelGC -XX:ActiveProcessorCount=1" -Ptests.seed=320EBC31DC094689 -Ptests.useSecurityManager=false -Ptests.gui=false -Ptests.file.encoding=UTF-8 -Ptests.vectorsize=512 -Ptests.forceintegervectors=true
```

The printed `Reproduce with:` line had two bugs:
- JVM args weren’t quoted
- It was missing `-Ptests.jvmargs=` prefix

Let me know if I can help further debug this.

### Version and environment details

Lucene commit hash: ca427071708e3b7d17bc654a31712a5cdbb1bd7d
OS: Windows 10 10.0 amd64
JVM: Eclipse Temurin OpenJDK 24.0.1+9 (64-bit)
Locale: kam
Timezone: Europe/Uzhgorod
CPUs: 1

Contributor guide

Open the contributing guide

Research direction

Start by running the exact Gradle command against org.apache.lucene.analysis.hunspell.TestSpellChecking.testGeneratedSuggestions and inspect the generated suggestion comparison. Then examine how the test reports its “Reproduce with:” command, including the JVM-argument quoting and missing prefix described in the issue. Done means the failure is understood or fixed and the reproduction command is emitted correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
search, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.