Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Local Java affected runs include nonexecutable selections and silently skipped fixture coverage

Aperta
  • Qualcosa non va?
#36,142 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java, python
Ambito
testing-qa, tooling

Direzione di ricerca

Start with .github/scripts/plan_local_java_tests.py::_integration_test_classes and inspect how it selects the named integration tests and reports missing or skipped coverage. Compare the ordinary affected run with the focused Maven invocation in the issue, then trace the benchmark gate, K8s guard and embedding-provider setup in the named tests. Done means selections are reported accurately and the app and embedding tests execute their intended assertions without hiding skip reasons.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

The local affected-test summary can list tests that did not exercise behavior. During an Ontology Studio affected run, the following source/fixture gaps required separate reconciliation. This issue tracks the harness gaps; it does not attribute the run's unrelated failures to them.

Current source was checked against main 5cbc32a8c916ac86f7f343fd99c73bbcd5398dd0. The planner, stub, benchmark, embedding test and shared bootstrap/POM match the inspected branch. Main has expanded DataRetentionAppIT since that branch but retains the same K8s guard.

  • .github/scripts/plan_local_java_tests.py::_integration_test_classes selects McpServiceResourceIT.java by filename even though the file contains only a package statement and TODO, with no executable class. The summary reports a missing XML file for a test that cannot run. Existing implementation follow-up: #33528.
  • WritePathBenchmarkIT#benchmarkSingleThreadWrites is selected as ordinary parallel coverage but aborts unless -Dbenchmark.run=true. The planner recognizes class-level property gates (for example RdfCatalogScaleIT), but does not classify this opt-in method consistently. Keep the opt-in benchmark explicit; an ordinary affected run should not imply it executed.
  • DataRetentionAppIT, SearchIndexPromotionIT and SearchIndexingFieldsParityIT abort when TestSuiteBootstrap.isK8sEnabled() is true. They are JUnit-isolated but share the parallel Failsafe process with a test that starts K3s. The archived run recorded all six selected methods skipped after K3s startup. A fresh focused process without the K8s setup is needed to exercise them; isolation should prevent persistent backend state from silently dropping coverage.
  • PatchTableEmbeddingIT enables natural-language search but never configures an embedding provider. In PostgreSQL/OpenSearch the engine assumption passes, then the test skips with Bedrock configuration is required when using bedrock provider. Configure a local test provider (as the DJL fixture in VectorEmbeddingIntegrationIT does) and require the intended assertion to execute without external credentials.

Reproduce the affected planner's selection and inspect the resulting skipped/missing-report section. For the K8s-sensitive tests, compare the ordinary shared parallel run with a fresh invocation:

env -u ENABLE_K8S_TESTS mvn -B verify -pl :openmetadata-integration-tests -am \
  -Pmysql-elasticsearch -DintegrationTests.lane=parallel \
  -Dit.test=DataRetentionAppIT,SearchIndexPromotionIT,SearchIndexingFieldsParityIT \
  -Dfailsafe.failIfNoSpecifiedTests=false -Dtest=NoUnitTestsInThisRun \
  -Dsurefire.failIfNoSpecifiedTests=false

The focused retry is still being reconciled; this report does not claim its result. Acceptance: nonexecutable/opt-in selections are reported accurately, the app tests execute regardless of unrelated K3s order, and the embedding test executes a real local-provider assertion. Preserve skip reasons and do not turn them into passing coverage.

Lingua principale
TypeScript
Stelle
15.4k
Fork
2.4k
Merge medio
22h 38m
PR unite (30g)
693

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di open-metadata/OpenMetadata

Tutte le issue di open-metadata/OpenMetadata

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.