microsoft/SynapseML

Python tests on build server are not using local maven repo to get scala code

Open

#1.474 geöffnet am 12. Apr. 2022

Auf GitHub ansehen
 (2 Kommentare) (0 Reaktionen) (1 zugewiesene Person)Scala (5.228 Stars) (861 Forks)batch import
area/buildbuggood first issuehelp wanted

Beschreibung

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior, code snippets encouraged

Expected behavior A clear and concise description of what you expected to happen.

Info (please complete the following information):

  • SynapseML Version: [e.g. v0.17]
  • Spark Version [e.g. 2.4.3]
  • Spark Platform [e.g. Databricks]

** Stacktrace**

Please post the stacktrace here if applicable

If the bug pertains to a specific feature please tag the appropriate CODEOWNER for better visibility

Additional context Add any other context about the problem here.

AB#1745598

Contributor Guide

Tech Stack
pythonscala
Domain
devopsbuild systemci cd
Issue Type
bug
SchwierigkeitGeschätzte Implementierungsschwierigkeit für neue Contributors, von 1 für sehr kleine Änderungen bis 5 für Expertenarbeit.
3
Geschätzte ZeitEin grober Zeitrahmen, um zu recherchieren, zu implementieren, zu testen und einen Pull Request vorzubereiten.
1-3 hours
AktivitätsstatusWie verfügbar das Issue gerade wirkt: frisch, aktiv, stale, blockiert oder wartet auf Maintainer-Input.
stale
KlarheitWie klar das Issue die erwartete Änderung, Akzeptanzkriterien und den nächsten Schritt erklärt.
needs investigation
Voraussetzungen
Understanding of Maven build systemBasic knowledge of Scala and PythonFamiliarity with CI/CD concepts
EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.
20
Research-Richtung
Investigate the build process for Python tests in SynapseML. The issue states that Python tests on the build server are not using the local Maven repository for Scala code. Look at the CI configuration files (e.g., .github/workflows) and the build scripts to understand how Maven repositories are set up. Examine any recent changes to the build system that might have caused this regression. Check the comments on the issue for any additional context or attempts to fix. No pull requests are linked, so the issue is open and may require reproducing the problem locally to identify the root cause.