Feature/gsk 1618 run python tests on windows builder#1382
Conversation
6660d1a to
0d776dc
Compare
65fe18d to
18f1d4c
Compare
ab3f3f2 to
5b1d640
Compare
72cab32 to
a4389e9
Compare
6a8f6f6 to
05da514
Compare
ba88330 to
c5b1099
Compare
c5b1099 to
d8c4276
Compare
|
|
||
| - name: Install dependencies | ||
| working-directory: python-client | ||
| run: pdm install -G :all |
There was a problem hiding this comment.
we don't probably need all groups here (dev for example) do we? prod, test and doc should be fine
There was a problem hiding this comment.
Dev is needed to run linting at least.
Also, I fear that lots of test will fail if I do that, since the split between test and dev deps is not that good yet (ie I just saw pytest-xdist in dev)
There was a problem hiding this comment.
but it can be a good motivation to move the dependencies in the right groups and make sure that people don't make mistakes in the future (for example if you add something to dev and not to test the unit test will fail)
There was a problem hiding this comment.
I will split that into a separated PR then, if it's ok : https://linear.app/giskard/issue/GSK-1717/use-gradle-build-action-instead-of-calling-gradlew
| mlflow.log_artifact(local_path) | ||
| elif mlflow_client and mlflow_run_id: | ||
| mlflow_client.log_artifact(mlflow_run_id, local_path=local_path) | ||
| # Note(Bazire): Should we have a raising else here ? |
There was a problem hiding this comment.
I'd say yes, to make sure there's no case where one of client or run_id are None
WDYT @rabah-khalek
613b28a to
916eefb
Compare
916eefb to
783daeb
Compare
|
Kudos, SonarCloud Quality Gate passed! |








Description
Related Issue
Type of Change
Checklist
CODE_OF_CONDUCT.mddocument.CONTRIBUTING.mdguide.make codestyle.