Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Lane 3 · android] Precision/Recall/F1 — Android target parity check (enable host tests for skainet-backend-cpu)

Abierto
  • ¿Algo no está bien?
#1,230 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
58/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Tranquilo
Stack tecnológico
android, kotlin
Área
mobile-dev, testing

Línea de trabajo

Start by checking the Android target configuration for skainet-backends/skainet-backend-cpu and the KMP/Android conventions under build-logic/convention/. Run the listed Gradle tasks command to confirm host-test availability, then identify and run the resulting Android host-test task; report any test failures rather than fixing unrelated ones. Done means posting the exact task and results, toolchain versions, and any target-specific findings on #1222, opening a separate linked bug if needed.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

coding good first issue platform size:s skill:android sub-issue

Sub-issue of #1222 (Precision, Recall and F1Score metrics).

Lane: 3 · Platform verification · Android
Skill needed: Android build tooling — running a Kotlin Multiplatform module's tests on this target. No tensor-internals or metrics knowledge required. The code under test is pure commonMain Kotlin over Double counters; this is a smoke check, not new implementation.
Size: s (~1–2 h — see Notes: host tests are not enabled for this module yet, so the first step is a small build change)
Blocked by: #1229 (F1Score merged to develop), or check out its branch early.

What to do

  1. Check whether skainet-backends/skainet-backend-cpu runs commonTest on the Android
    target at all. As of today it does not: ./gradlew :skainet-backends:skainet-backend-cpu:tasks --all
    warns "The commonTest source directory exists, but android host tests are not
    enabled. To enable android host tests, add withHostTest {} to your android target
    configuration"     and lists no Android test task.
  2. Add withHostTest {} to the module's Android target configuration (the
    com.android.kotlin.multiplatform.library plugin, applied via sk.ainet.multiplatform
    / libs.plugins.androidMultiplatformLibrary — check whether it belongs in the
    convention plugin under build-logic/convention/ so every module gets it, and say
    which you chose in the PR).
  3. Run the resulting host-test task (something like
    ./gradlew :skainet-backends:skainet-backend-cpu:testAndroidHostTest — take the name
    from the task list) and, if you have a device or emulator, the instrumented variant too.

Then, in every case:

  • Confirm the metric tests (sk.ainet.exec.metrics.*) pass and the values match the JVM run
    bit-for-bit — pure Long counting and Double division, so any drift is itself a finding.
  • Report on #1222: target, toolchain versions, pass/fail, wall-clock, anything
    target-specific you hit (an expect/actual gap, a disabled test source set, a task
    that doesn't exist).

Acceptance

  • Result posted on #1222 with the exact Gradle task(s) run
  • If something is wrong, a separate bug issue opened and linked — don't block the
    parent on investigating it here

Notes

Enabling host tests may surface other failing tests in commonTest that have never run
on Android before. If so, that is a real finding: report the list on the parent and open
one bug for it; do not try to fix them in this PR. The kmp / Android conventions live
in build-logic/convention/ — see Explanation → Android NEON kernels via JNI for how
the Android target is wired.

Lenguaje dominante
Kotlin
Estrellas
52
Forks
15
Merge medio
1 d 15 h
PR fusionados (30 d)
36

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de SKaiNET-developers/SKaiNET

Todos los issues de SKaiNET-developers/SKaiNET

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.