Open david-cortes-intel opened 1 day ago
This worked for a local build, but it seems it was not enough for the CI job named "Docs": https://dev.azure.com/daal/daal4py/_build/results?buildId=40827&view=logs&j=7e620c85-24a8-5ffa-8b1f-642bc9b1fc36&t=dadee17e-671e-5fd8-4599-c783ec4d74d0
It still fails to import daal4py
during the doc build step. Wonder if the issue might be that it is not building it.
Description
This PR resolves many warnings that pop out when building the
daal4py
docs and which prevent the CI jobs from building those docs correctly.Note that it doesn't solve all of the warnings - after this PR, one would still see many of these cases:
(I'm not sure what to do about those)
PR should start as a draft, then move to ready for review state after CI is passed and all applicable checkboxes are closed. This approach ensures that reviewers don't spend extra time asking for regular requirements.
You can remove a checkbox as not applicable only if it doesn't relate to this PR in any way. For example, PR with docs update doesn't require checkboxes for performance while PR with any change in actual code should have checkboxes and justify how this code change is expected to affect performance (or justification should be self-evident).
Checklist to comply with before moving PR from draft:
PR completeness and readability
Testing
Performance
Not applicable.