You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
base_job_name without effect in ModelTrainer #6299
Describe the bug base_job_name in ModelTrainer seems to have no effect, names are seemingly generated (e.g. "pipelines-ctd6lgoe9v02-PreprocessorTraining-ssFiEMALJh", where "PreprocessorTraining" is the step-name in the pipeline). The same issue is the case for base_tuning_job_name in the HyperparameterTuner.
This is a regression in comparison to v2 behavior.
To reproduce
Use the base_job_name variable, it will have no effect on training job names, log stream names, etc.
Fixed by #6323 (merged to master). base_job_name / base_tuning_job_name are now preserved in the pipeline request for ModelTrainer and HyperparameterTuner, with regression tests added (test_pipeline_session_request_keeps_training_job_name, test_pipeline_session_request_keeps_tuning_job_name).
Activity
fix: keep job name in pipeline request for ModelTrainer and Hyperpara…
fix: keep job name in pipeline request for ModelTrainer and Hyperpara…
mufaddal-rohawala commentedon Nov 3, 2026
Fixed by #6323 (merged to master).
base_job_name/base_tuning_job_nameare now preserved in the pipeline request forModelTrainerandHyperparameterTuner, with regression tests added (test_pipeline_session_request_keeps_training_job_name,test_pipeline_session_request_keeps_tuning_job_name).