Skip to content

fix(core): gonka_tests use super::* misses build_provider_from_entry — unit tests fail to compile with --features full #3633

@bug-ops

Description

@bug-ops

Description

PR #3632 introduced 4 new unit tests in crates/zeph-core/src/provider_factory.rs inside a nested #[cfg(feature = \"gonka\")] mod gonka_tests. These tests call build_provider_from_entry via use super::*, but super resolves to mod tests — which only imports effective_embedding_model and stable_skill_embedding_model, not build_provider_from_entry. As a result, cargo nextest run --workspace --features full --lib --bins fails to compile zeph-core.

Reproduction Steps

  1. git checkout b0a07602
  2. cargo nextest run --config-file .github/nextest.toml --workspace --features full --lib --bins
  3. Observe 4 errors: cannot find function build_provider_from_entry in this scope

Expected Behavior

All tests compile and pass.

Actual Behavior

error[E0425]: cannot find function `build_provider_from_entry` in this scope
  --> crates/zeph-core/src/provider_factory.rs:633:26
  --> crates/zeph-core/src/provider_factory.rs:647:26
  --> crates/zeph-core/src/provider_factory.rs:663:26
  --> crates/zeph-core/src/provider_factory.rs:677:26
error: could not compile `zeph-core` (lib test) due to 4 previous errors

Fix

In mod tests, add:

use super::build_provider_from_entry;

Or move the use into gonka_tests directly:

use super::super::build_provider_from_entry;

Environment

  • Commit: b0a0760
  • Features: full (gonka enabled)

Logs / Evidence

Detected in CI-687 live testing pre-flight (cargo nextest run step).

Metadata

Metadata

Assignees

Labels

P0Blocking — security advisory or compile errorbugSomething isn't workingllmzeph-llm crate (Ollama, Claude)

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions