[enh] Conda recipe update and CI OS version pinning

[Alexsandruss]

Description

Scikit-learn-intelex conda recipe update.

Changes:

• Update content of recipe, building and testing scripts to sync with conda-forge feedstock
• Add recipe building on Linux and Windows to CI
• Pin CI images versions
• Add hint for CMake to get python executable from $PYTHON if set

Conda-forge checks: conda-forge/scikit-learn-intelex-feedstock#38

---

Checklist to comply with before moving PR from draft:

PR completeness and readability

• I have reviewed my changes thoroughly before submitting this pull request.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect the changes or created a separate PR with update and provided its number in the description, if necessary.
• Git commit message contains an appropriate signed-off-by string (see CONTRIBUTING.md for details).
• I have added a respective label(s) to PR if I have a permission for that.
• I have resolved any merge conflicts that might occur with the base branch.

Testing

• The unit tests pass successfully.
• I have run it locally and tested the changes extensively.

Performance

• I have measured performance for affected algorithms using scikit-learn_bench and provided at least summary table with measured data, if performance change is expected.
• I have provided justification why performance has changed or why changes are not expected.

[Alexsandruss]

/intelci: run

[Alexsandruss]

/intelci: run

[Alexsandruss]

/intelci: run

[Alexsandruss]

/intelci: run

[Alexsandruss]

/iintelci: run

[icfaust]

Overall pretty useful addition. I would beef up the description, separate out some of the other changes, and possibly drop sklearn 1.1 or 1.2 from the standard test matrix. The reason being is that by adding these two recipes, we are starting to really push our luck on azure pipeline runners. I'll let others weigh in on this @samir-nasibli @ethanglaser .

[icfaust]

Looks to be some sort of windows python conda issue. Your previous responses were sufficient for me. I found one issue with a re-enablement that may require running private CI, maybe some clarity could explain it away as an alternate solution. If we solve these small issues, I think it would be ready.

[icfaust]

/intelci: run

[samir-nasibli]

@Alexsandruss please rebase your branch.

[Alexsandruss]

/intelci: run

[Alexsandruss]

/intelci: run

[Alexsandruss]

/intelci: run

[Alexsandruss]

/intelci: run

[icfaust]

Just some last questions from me. Thanks for the updates based off the previous comments.

[david-cortes-intel]

Question: are the commands in meta.yaml for executing tests actually needed if it will end up calling the run_test.sh/bat scripts in the end? E.g. do they execute somewhere else too?

[napetrov]

can we point to general VS/compiler requirements so we would have single place to track/update?

[Alexsandruss]

Not really in case of conda recipe, vs2022 is default for this repo and included in CI Windows image, vs2019 - for conda-forge feedstock, and build config change is required to set another version and there is no guarantee it will work as expected (but it is unlikely someone will use version other than 2019 or 2022).

I will add mention how to change compiler for conda-build on Win.

[Alexsandruss]

/intelci: run

[icfaust]

@Alexsandruss This was merged with an error in the WindowsCondaEnv Python3.12_Sklearn1.5 step

[david-cortes-intel]

@Alexsandruss This was merged with an error in the WindowsCondaEnv Python3.12_Sklearn1.5 step

The error appears to be sporadic though.