Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes to support onemkl 2024.0 packages #61

Merged
merged 19 commits into from
Dec 7, 2023

Conversation

maria-Petrova
Copy link
Contributor

@maria-Petrova maria-Petrova commented Dec 5, 2023

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

@conda-forge-webservices
Copy link

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • pin_compatible should be used instead of pin_subpackage for dpcpp-cpp-rt because it is not a known output of this recipe: ['mkl', 'mkl-include', 'onemkl-sycl-blas', 'onemkl-sycl-datafitting', 'onemkl-sycl-dft', 'onemkl-sycl-lapack', 'onemkl-sycl-rng', 'onemkl-sycl-sparse', 'onemkl-sycl-stats', 'onemkl-sycl-vm', 'mkl-devel', 'dal', 'dal-include', 'dal-static', 'dal-devel', 'impi_rt', 'impi-devel', 'intel_repack'].
  • pin_compatible should be used instead of pin_subpackage for intel-opencl-rt because it is not a known output of this recipe: ['mkl', 'mkl-include', 'onemkl-sycl-blas', 'onemkl-sycl-datafitting', 'onemkl-sycl-dft', 'onemkl-sycl-lapack', 'onemkl-sycl-rng', 'onemkl-sycl-sparse', 'onemkl-sycl-stats', 'onemkl-sycl-vm', 'mkl-devel', 'dal', 'dal-include', 'dal-static', 'dal-devel', 'impi_rt', 'impi-devel', 'intel_repack'].
  • pin_compatible should be used instead of pin_subpackage for dpcpp-cpp-rt because it is not a known output of this recipe: ['mkl', 'mkl-include', 'onemkl-sycl-blas', 'onemkl-sycl-datafitting', 'onemkl-sycl-dft', 'onemkl-sycl-lapack', 'onemkl-sycl-rng', 'onemkl-sycl-sparse', 'onemkl-sycl-stats', 'onemkl-sycl-vm', 'mkl-devel', 'dal', 'dal-include', 'dal-static', 'dal-devel', 'impi_rt', 'impi-devel', 'intel_repack'].
  • pin_compatible should be used instead of pin_subpackage for intel-opencl-rt because it is not a known output of this recipe: ['mkl', 'mkl-include', 'onemkl-sycl-blas', 'onemkl-sycl-datafitting', 'onemkl-sycl-dft', 'onemkl-sycl-lapack', 'onemkl-sycl-rng', 'onemkl-sycl-sparse', 'onemkl-sycl-stats', 'onemkl-sycl-vm', 'mkl-devel', 'dal', 'dal-include', 'dal-static', 'dal-devel', 'impi_rt', 'impi-devel', 'intel_repack'].
  • pin_compatible should be used instead of pin_subpackage for dpcpp-cpp-rt because it is not a known output of this recipe: ['mkl', 'mkl-include', 'onemkl-sycl-blas', 'onemkl-sycl-datafitting', 'onemkl-sycl-dft', 'onemkl-sycl-lapack', 'onemkl-sycl-rng', 'onemkl-sycl-sparse', 'onemkl-sycl-stats', 'onemkl-sycl-vm', 'mkl-devel', 'dal', 'dal-include', 'dal-static', 'dal-devel', 'impi_rt', 'impi-devel', 'intel_repack'].
  • pin_compatible should be used instead of pin_subpackage for intel-opencl-rt because it is not a known output of this recipe: ['mkl', 'mkl-include', 'onemkl-sycl-blas', 'onemkl-sycl-datafitting', 'onemkl-sycl-dft', 'onemkl-sycl-lapack', 'onemkl-sycl-rng', 'onemkl-sycl-sparse', 'onemkl-sycl-stats', 'onemkl-sycl-vm', 'mkl-devel', 'dal', 'dal-include', 'dal-static', 'dal-devel', 'impi_rt', 'impi-devel', 'intel_repack'].
  • pin_compatible should be used instead of pin_subpackage for dpcpp-cpp-rt because it is not a known output of this recipe: ['mkl', 'mkl-include', 'onemkl-sycl-blas', 'onemkl-sycl-datafitting', 'onemkl-sycl-dft', 'onemkl-sycl-lapack', 'onemkl-sycl-rng', 'onemkl-sycl-sparse', 'onemkl-sycl-stats', 'onemkl-sycl-vm', 'mkl-devel', 'dal', 'dal-include', 'dal-static', 'dal-devel', 'impi_rt', 'impi-devel', 'intel_repack'].
  • pin_compatible should be used instead of pin_subpackage for intel-opencl-rt because it is not a known output of this recipe: ['mkl', 'mkl-include', 'onemkl-sycl-blas', 'onemkl-sycl-datafitting', 'onemkl-sycl-dft', 'onemkl-sycl-lapack', 'onemkl-sycl-rng', 'onemkl-sycl-sparse', 'onemkl-sycl-stats', 'onemkl-sycl-vm', 'mkl-devel', 'dal', 'dal-include', 'dal-static', 'dal-devel', 'impi_rt', 'impi-devel', 'intel_repack'].
  • pin_compatible should be used instead of pin_subpackage for dpcpp-cpp-rt because it is not a known output of this recipe: ['mkl', 'mkl-include', 'onemkl-sycl-blas', 'onemkl-sycl-datafitting', 'onemkl-sycl-dft', 'onemkl-sycl-lapack', 'onemkl-sycl-rng', 'onemkl-sycl-sparse', 'onemkl-sycl-stats', 'onemkl-sycl-vm', 'mkl-devel', 'dal', 'dal-include', 'dal-static', 'dal-devel', 'impi_rt', 'impi-devel', 'intel_repack'].
  • pin_compatible should be used instead of pin_subpackage for intel-opencl-rt because it is not a known output of this recipe: ['mkl', 'mkl-include', 'onemkl-sycl-blas', 'onemkl-sycl-datafitting', 'onemkl-sycl-dft', 'onemkl-sycl-lapack', 'onemkl-sycl-rng', 'onemkl-sycl-sparse', 'onemkl-sycl-stats', 'onemkl-sycl-vm', 'mkl-devel', 'dal', 'dal-include', 'dal-static', 'dal-devel', 'impi_rt', 'impi-devel', 'intel_repack'].
  • pin_compatible should be used instead of pin_subpackage for dpcpp-cpp-rt because it is not a known output of this recipe: ['mkl', 'mkl-include', 'onemkl-sycl-blas', 'onemkl-sycl-datafitting', 'onemkl-sycl-dft', 'onemkl-sycl-lapack', 'onemkl-sycl-rng', 'onemkl-sycl-sparse', 'onemkl-sycl-stats', 'onemkl-sycl-vm', 'mkl-devel', 'dal', 'dal-include', 'dal-static', 'dal-devel', 'impi_rt', 'impi-devel', 'intel_repack'].
  • pin_compatible should be used instead of pin_subpackage for intel-opencl-rt because it is not a known output of this recipe: ['mkl', 'mkl-include', 'onemkl-sycl-blas', 'onemkl-sycl-datafitting', 'onemkl-sycl-dft', 'onemkl-sycl-lapack', 'onemkl-sycl-rng', 'onemkl-sycl-sparse', 'onemkl-sycl-stats', 'onemkl-sycl-vm', 'mkl-devel', 'dal', 'dal-include', 'dal-static', 'dal-devel', 'impi_rt', 'impi-devel', 'intel_repack'].
  • pin_compatible should be used instead of pin_subpackage for dpcpp-cpp-rt because it is not a known output of this recipe: ['mkl', 'mkl-include', 'onemkl-sycl-blas', 'onemkl-sycl-datafitting', 'onemkl-sycl-dft', 'onemkl-sycl-lapack', 'onemkl-sycl-rng', 'onemkl-sycl-sparse', 'onemkl-sycl-stats', 'onemkl-sycl-vm', 'mkl-devel', 'dal', 'dal-include', 'dal-static', 'dal-devel', 'impi_rt', 'impi-devel', 'intel_repack'].
  • pin_compatible should be used instead of pin_subpackage for intel-opencl-rt because it is not a known output of this recipe: ['mkl', 'mkl-include', 'onemkl-sycl-blas', 'onemkl-sycl-datafitting', 'onemkl-sycl-dft', 'onemkl-sycl-lapack', 'onemkl-sycl-rng', 'onemkl-sycl-sparse', 'onemkl-sycl-stats', 'onemkl-sycl-vm', 'mkl-devel', 'dal', 'dal-include', 'dal-static', 'dal-devel', 'impi_rt', 'impi-devel', 'intel_repack'].
  • pin_compatible should be used instead of pin_subpackage for dpcpp-cpp-rt because it is not a known output of this recipe: ['mkl', 'mkl-include', 'onemkl-sycl-blas', 'onemkl-sycl-datafitting', 'onemkl-sycl-dft', 'onemkl-sycl-lapack', 'onemkl-sycl-rng', 'onemkl-sycl-sparse', 'onemkl-sycl-stats', 'onemkl-sycl-vm', 'mkl-devel', 'dal', 'dal-include', 'dal-static', 'dal-devel', 'impi_rt', 'impi-devel', 'intel_repack'].
  • pin_compatible should be used instead of pin_subpackage for intel-opencl-rt because it is not a known output of this recipe: ['mkl', 'mkl-include', 'onemkl-sycl-blas', 'onemkl-sycl-datafitting', 'onemkl-sycl-dft', 'onemkl-sycl-lapack', 'onemkl-sycl-rng', 'onemkl-sycl-sparse', 'onemkl-sycl-stats', 'onemkl-sycl-vm', 'mkl-devel', 'dal', 'dal-include', 'dal-static', 'dal-devel', 'impi_rt', 'impi-devel', 'intel_repack'].

@napetrov
Copy link
Contributor

napetrov commented Dec 5, 2023

@conda-forge-admin, please rerender

recipe/meta.yaml Outdated Show resolved Hide resolved
recipe/meta.yaml Outdated Show resolved Hide resolved
recipe/meta.yaml Outdated Show resolved Hide resolved
@conda-forge-webservices
Copy link

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
  • When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).

@napetrov
Copy link
Contributor

napetrov commented Dec 5, 2023

@conda-forge-admin, please rerender

Copy link

github-actions bot commented Dec 5, 2023

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/intel_repack-feedstock/actions/runs/7102779228.

recipe/meta.yaml Outdated
outputs:
{% if not osx %}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

my guess is that this have to be handled by line 98 ?

skip: True # [not x86 and not (linux64 or win)]

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

skip in global build section will cause all outputs to cancel.

recipe/meta.yaml Outdated
test:
commands:
- ls -A $PREFIX/lib/* # [unix]
- test -f $PREFIX/lib/libmkl_sycl_data_fitting.so # [unix]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we already use SONAME version in the filename for Windows, perhaps we should be changing for libmkl_sycl_data_filling.so.4 here too

@oleksandr-pavlyk
Copy link
Contributor

Somehow the recipe ran on OSX and produced an artifact:

INFO :: The inputs making up the hashes for the built packages are as follows:
{
  "intel_repack-2024.0.1-hbb52d48_": {
    "recipe": {
      "channel_targets": "conda-forge main",
      "llvm_openmp": "16",
      "mkl": "2023",
      "target_platform": "osx-64"
    }
  }
}

This should not be happening at all for MKL 2024, right?

@napetrov
Copy link
Contributor

napetrov commented Dec 6, 2023

Somehow the recipe ran on OSX and produced an artifact:

INFO :: The inputs making up the hashes for the built packages are as follows:
{
  "intel_repack-2024.0.1-hbb52d48_": {
    "recipe": {
      "channel_targets": "conda-forge main",
      "llvm_openmp": "16",
      "mkl": "2023",
      "target_platform": "osx-64"
    }
  }
}

This should not be happening at all for MKL 2024, right?

i think this is normal as this in intel_repack feedstock itself and not a one of package outputs

@napetrov
Copy link
Contributor

napetrov commented Dec 6, 2023

@conda-forge-admin, please rerender

@napetrov
Copy link
Contributor

napetrov commented Dec 6, 2023

Somehow the recipe ran on OSX and produced an artifact:

INFO :: The inputs making up the hashes for the built packages are as follows:
{
  "intel_repack-2024.0.1-hbb52d48_": {
    "recipe": {
      "channel_targets": "conda-forge main",
      "llvm_openmp": "16",
      "mkl": "2023",
      "target_platform": "osx-64"
    }
  }
}

This should not be happening at all for MKL 2024, right?

i think this is normal as this in intel_repack feedstock itself and not a one of package outputs

looks that it's actually not as this intel_repack output was added - 7102af3 , which shouldn't happen

@maria-Petrova
Copy link
Contributor Author

@conda-forge-admin, please rerender

@maria-Petrova
Copy link
Contributor Author

@conda-forge-admin, please rerender

@napetrov napetrov merged commit e1d0aaf into conda-forge:main Dec 7, 2023
3 of 4 checks passed
@h-vetinari
Copy link
Member

So this PR intentionally removed support for osx-64. I'm guessing that's permanent and not coming back?

@napetrov
Copy link
Contributor

So this PR intentionally removed support for osx-64. I'm guessing that's permanent and not coming back?

Correct. There is no MacOS packages created by intel starting from 2024.0 release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants