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

Training job unit tests can outlive their service mocks and hang teardown

Abierto Apto para principiantes
  • ¿Algo no está bien?
#7,208 1 comentario 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
72/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
gcp, python
Área
testing

Línea de trabajo

Empieza con test_run_called_twice_raises en los archivos de pruebas unitarias de AutoML para forecasting, image, tabular, text y video, y con test_run_returns_none_if_no_model_to_upload en las pruebas de custom training job. En cada caso asíncrono, une el primer job con job.wait() después de la aserción de la ejecución duplicada, como ya hacen las pruebas de custom training sin sincronización. Ejecuta el script de diagnóstico del issue. Está terminado cuando pasa en los 22 casos y el teardown ya no espera reintentos reales del cliente de pipelines.

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

Descripción

api: vertex-ai

The async cases of test_run_called_twice_raises in the AutoML forecasting, image, tabular, text and video modules can return while the first training job is still running. The second run() correctly raises RuntimeError, but the test does not wait for the first job before pytest removes the service mocks.

The same lifetime issue also occurs in test_run_returns_none_if_no_model_to_upload for CustomTrainingJob, CustomContainerTrainingJob and CustomPythonPackageTrainingJob. Those tests assert that run() returns None, then return without joining the job.

During a bounded investigation, a forecasting worker entered the real PipelineServiceClient.get_training_pipeline after those mocks were removed, while class teardown waited in initializer.global_pool.shutdown(wait=True). This blocked the unit-test run on RPC retries in an offline environment. A subsequent parallel run also captured a real pipeline-client retry during the custom-container no-model test, whose teardown took 80.49 seconds despite the test ultimately being reported as passed.

Environment
  • Current main: 7f08bd6c1dbb99f8a00922ae13c488bda3ece7b9.
  • Debian 12 container, Linux/WSL2, CPython 3.14.7, pip 26.2.1.
  • SDK imported from the checkout (2.4.0), with the standard unit-test dependencies. No cloud credentials or external network.
  • The existing environment's pip check reports invalid MLflow optional-extra metadata (scikit-learn >=1.0.*) on both unchanged and modified main; uv pip check passes. No dependency versions were changed for this investigation.
Reproduction

The ordinary hang depends on worker scheduling. The diagnostic below makes the lifetime error deterministic for the existing SequenceToSequencePlusForecastingTrainingJob-False case. It holds the worker just before model lookup, preserves the original duplicate-run assertion, and checks for unfinished work when the test returns. It then releases and joins the worker while the service mocks are still active, so the diagnostic fails rather than hanging in teardown.

Save the script outside the checkout as /tmp/automl-lifetime-repro.py, then run from the repository root in its unit-test environment:

python -I -B /tmp/automl-lifetime-repro.py

Expected: background work completes before the test returns. On the main commit above, the script fails with AssertionError: Test returned with background work pending. Adding an async job.wait() after the existing exception assertion makes it pass. The same barrier check across the five AutoML modules and the three custom no-model methods found 11 failing async cases and 11 passing sync cases; all 22 pass with the final cleanup, and removing the cleanup restores the same 11 failures.

Standalone diagnostic (verified on unchanged main and with the cleanup) 
"""Run from the repository root with its unit-test dependencies installed."""
import inspect
from pathlib import Path
import sys
import threading
from unittest import mock

import pytest

sys.path.insert(0, str(Path.cwd()))
from google.cloud.aiplatform import base, training_jobs


class LifetimeCheck:
    @pytest.hookimpl(hookwrapper=True, tryfirst=True)
    def pytest_runtest_call(self, item):
        entered, release = threading.Event(), threading.Event()
        jobs = []
        original_get = training_jobs._TrainingJob._get_model
        original_wait = base.FutureManager.wait

        def held_get(job, *args, **kwargs):
            if threading.current_thread() is not threading.main_thread():
                jobs.append(job)
                entered.set()
                assert release.wait(10), "Worker barrier expired"
            return original_get(job, *args, **kwargs)

        def explicit_wait(job):
            release.set()
            return original_wait(job)

        with mock.patch.object(training_jobs._TrainingJob, "_get_model", held_get), mock.patch.object(base.FutureManager, "wait", explicit_wait):
            outcome = yield
            observed = entered.wait(5)
            completed = observed and all(job._are_futures_done() for job in jobs)
            # Safely finish the worker while the test's service mocks still exist.
            release.set()
            for job in jobs:
                original_wait(job)
            outcome.get_result()
            assert observed, "Worker did not reach the model boundary"
            assert completed, "Test returned with background work pending"


print("SDK source:", inspect.getfile(training_jobs), flush=True)
raise SystemExit(pytest.main([
    "-q", "-p", "no:warnings", "-p", "no:cacheprovider",
    "tests/unit/aiplatform/test_automl_forecasting_training_jobs.py::"
    "TestForecastingTrainingJob::test_run_called_twice_raises"
    "[SequenceToSequencePlusForecastingTrainingJob-False]",
], plugins=[LifetimeCheck()]))

I have a local test-only cleanup that adds if not sync: job.wait() after the existing assertion in these eight methods across six files. The three equivalent custom-training duplicate-run tests already use that pattern. Would this be an appropriate focused test-cleanup contribution?

Lenguaje dominante
Python
Estrellas
907
Forks
469
Merge medio
1 d 14 h
PR fusionados (30 d)
37

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 googleapis/python-aiplatform

Todos los issues de googleapis/python-aiplatform

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.