Howto add autopkgtest for OpenCL software , using the rocm-opencl-icd
* List of packages
https://codesearch.debian.net/search?q=path%3Adebian%2Ftests%2Fcontrol+pyopencl&literal=1
https://codesearch.debian.net/search?q=path%3Adebian%2Fcontrol+pocl-opencl-icd&literal=1&perpkg=1
https://codesearch.debian.net/search?q=path%3Adebian%2Fcontrol+pyopencl&literal=1
https://codesearch.debian.net/search?q=path%3Adebian%2Fcontrol+opencl&literal=1 -> TODO find interesting packages.
Package |
OpenCL unit test |
OpenCL autopkgtest |
Rocm autopkgtest |
Upstream |
pas de tests |
|
|
||
|
X |
|||
|
X |
|||
|
X |
|||
|
X |
|||
X |
X |
|||
X |
X |
|||
X |
X |
|||
X |
X |
X |
||
X |
X |
|||
|
||||
|
||||
X |
X |
|||
pas de tests |
||||
pas d'opencl test ni de rocm |
||||
X |
|
|||
pas de tests opencl ni rocm |
||||
/ |
||||
pas de test |
||||
/ |
||||
|
X |
|||
|
X |
|||
no tests |
= Autres tests =
Inventaire de tous les autres tests des pkg
Fichiers de tests : test_swap_quadrants.py / test_memin.py / test_fft.py / check-gradient / check-multipage-readers / test-142.sh / test-149.sh / test-153.sh / test-161.sh / test-177.sh /test-core-149.sh /test-file-write-regression.sh /test-gradient.sh /test-multipage-readers.sh /test-nlm.sh /
Fichiers de tests: testutils.py utils.py tests.py nabu/preproc/tests nabu/io/tests nabu/estimation/tests nabu/misc/tests nabu/pipeline/tests nabu/processing/tests nabu/reconstruction/tests nabu/resources/tests nabu/stitching/tests
Fichiers de tests:master/debian/tests/nabu-pocl pynx/-/blob/master/.gitlab-ci.yml pynx/cdi/test pynx/holotomo/test pynx/processing_unit/test pynx/ptycho/test pynx/scattering/test pynx/scripts/pynx_test.py pynx/-/tree/master/pynx/test pynx/-/tree/master/pynx/utils/test pynx/-/tree/master/pynx/wavefront/test
Fichiers de tests: pocl/-/tree/main/cmake pocl/-/tree/main/examples/PyOpenCL pocl/-/tree/main/examples/ViennaCL pocl/-/tree/main/examples/chipStar pocl/-/tree/main/examples/shoc pocl/-/tree/main/tests pocl/-/tree/main/tools/scripts pocl/-/tree/main/tools/docker pocl/-/tree/main/tools/data
Fichiers de tests: examl/-/tree/master/testData
Fichiers de tests:clblast/-/tree/debian/sid/.github/workflows clblast/-/tree/debian/sid/test clblast/-/blob/debian/sid/doc/testing.md clblast/-/blob/debian/sid/scripts/generator/generator/routine.py clblast/-/blob/debian/sid/doc/testing.md
Fichiers de tests:clpeak/-/tree/main/android/app/src/androidTest
Fichiers de tests:genx/-/blob/debian/master/doc_source/source/_templates/test genx/-/tree/debian/master/genx/tests genx/genx/models/lib/testing.py genx/tests/data/test.conf genx/genx/plugins/add_ons/Test.py genx/genx/examples/widget_test.ipynb
Fichiers de tests:.github/workflows/test.yml TESTS.txt explore/beta/testPolyDiseperseSphricalBeta.m sasmodels/model_test.py data_files/testPolydisperseGaussianSphere.dat explore/beta/data_files/testPolydisperseGaussianSphere2.dat pytest.ini conftest.py debian/patches/0005-Clean-up-model-files-from-tests.patch
Fichiers de tests:tools/test.pl tools/test.sh tools/test_rules.pl tools/rules-test-cases.yaml src/selftest.c include/selftest.h tools/test_modules tools/cl_tests tools/pdf_tests tools/tc_tests tools/vc_tests?ref_type=heads
Fichiers de tests:tests examples/swig_python/test.py examples/hmctest examples/matrixtest examples/complextest examples/tinytest examples/oddstatetest examples/synthetictest
Fichiers de tests:test .test-conda-env-py3.yml
Fichiers de tests:compyle/tests/test_jit.py .github/workflows/tests.yml
Fichiers de tests:gpyfft/test debian/patches/0001-add-also-the-CPU-devices-for-tests.patch debian/tests/control
Fichiers de tests:/doc/source/scripts pyvkfft/test doc/source/api/testing.rst pyvkfft/scripts/pyvkfft_test_suite.py examples/pyvkfft-tests-CUDA.ipynb doc/source/examples/pyvkfft-tests-OpenCL.nblink
/
Fichiers de tests: tests
/
Fichiers de tests:pysph/base/tests pysph/sph/tests .github/workflows/tests.yml pysph/solver/tests pysph/parallel/tests pysph/tools/tests requirements-test.txt pysph/examples/tests/test_examples.py
Fichiers de tests:src/pyFAI/test
Fichiers de tests: src/silx/app/test_.py src/silx/test src/silx/gui/test src/silx/image/test/test_bb.py src/silx/io/test src/silx/utils/test src/silx/gui/plot3d/test/test_gl.py src/silx/gui/_glutils/test/test_gl.py src/silx/math/fft/test src/silx/math/test/test_combo.py src/silx/opencl/test/test_image.py
Fichiers de tests:tests/raycing examples/withRaycing/_QookBeamlines/testGrating.xml examples/withRaycing/_QookBeamlines/testAlignment.xml
- FIN
Bug Reports
severity :
tags :
Subject : Missing OpenCL/ROCm autopkgtest (no unit tests or autopkgtests)
Hello,
I am currently working on packaging python-xrt.
I’ve noticed that there are: No OpenCL unit tests/ No OpenCL autopkgtests / No ROCm-related tests or validation
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL/ROCm implementations), it would be very useful to include these tests.
Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards, Clément Longeac
severity :
tags :
Subject : Missing OpenCL unit tests /ROCm autopkgtest Hello,
I am currently working on packaging nabu.
I’ve noticed that there are: No OpenCL unit tests/ No ROCm-related tests or validation
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL/ROCm implementations), it would be very useful to include these tests.
Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards, Clément Longeac
severity :
tags :
Subject : Missing OpenCL unit tests /ROCm autopkgtest Hello,
I am currently working on packaging pynx.
I’ve noticed that there are: No OpenCL unit tests/ No ROCm-related tests or validation
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL/ROCm implementations), it would be very useful to include these tests.
Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards, Clément Longeac
severity :
tags :
Subject : Missing OpenCL unit tests /ROCm autopkgtest Hello,
I am currently working on packaging pocl.
I’ve noticed that there are: No OpenCL unit tests/ No ROCm-related tests or validation
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL/ROCm implementations), it would be very useful to include these tests. Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards, Clément Longeac
severity :
tags :
Subject : Missing OpenCL unit tests /ROCm test Hello,
I am currently working on packaging examl.
I’ve noticed that there are: No OpenCL unit tests/ No ROCm-related tests or validation
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL/ROCm implementations), it would be very useful to include these tests.
Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards,
severity :
tags :
Subject : Missing OpenCL ROCm test Hello,
I am currently working on packaging clblast.
I’ve noticed that there are: No ROCm-related tests or validation
To help downstream maintainers and ensure runtime compatibility (especially across different ROCm implementations), it would be very useful to include these tests. Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards,
clpeak severity :
tags :
Subject : clpeak lacks unit tests Hello,
I am currently working on packaging clpeak.
I’ve noticed that there are: No OpenCL unit tests
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL it would be very useful to include these tests to help catch regressions .
Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards,
severity :
tags :
Subject : Missing Rocm autopkgtest Hello,
I am currently working on packaging genx.
I’ve noticed that there are: No Rocm autopkgtest
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL it would be very useful to include Rocm autopkgtest , have more reliable test ?OpenCl and better validation results on Gui
Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards,
severity :
tags :
Subject : add unit tests for OpenCL/ROCm integrations
I am currently working on packaging genx.
I’ve noticed that there are: No Rocm autopkgtest
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL it would be very useful to include more Rocm autopkgtest and openCLtest.
Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards,
severity :
tags :
Subject : add unit tests for OpenCL/ROCm integrations
I am currently working on packaging genx.
I’ve noticed that there are: No Rocm autopkgtest
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL it would be very useful to include Rocm autopkgtest.OpenCL unit tests are not detected correctly when running autopkgtest with an incomplete POCL environment.
Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards,
severity :
tags :
Subject : Missing OpenCL unit tests /ROCm test Hello,
I am currently working on packaging hashcat.
I’ve noticed that there are: No OpenCL unit tests and autopkgtest/ No ROCm-related tests or validation
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL/ROCm implementations), it would be very useful to include these tests.
Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards,
severity :
tags :
Subject : Missing OpenCL unit tests and autopkgtest /ROCm test
Hello,
I am currently working on packaging libhmsbeagle.
I’ve noticed that there are: No OpenCL unit tests and autopkgtest/ No ROCm-related tests or validation
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL/ROCm implementations), it would be very useful to include these tests.
Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards,
severity :
tags :
Subject : Missing Rocm autopkgtest Hello,
I am currently working on packaging pyopencl.
I’ve noticed that there are: No Rocm autopkgtest
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL it would be very useful to include Rocm autopkgtest. Autopkgtests involving pyopencl fail, it would be useful to add an explicit check. Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards,
severity :
tags :
Subject : Missing OpenCL unit tests and autopkgtest /ROCm test Hello,
I am currently working on packaging compyle.
I’ve noticed that there are: No OpenCL unit tests and autopkgtest/ No ROCm-related tests or validation
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL/ROCm implementations), it would be very useful to include these tests.
Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards,
severity :
tags :
Subject : Missing OpenCL unit tests and autopkgtest /ROCm test Hello,
I am currently working on packaging gpyfft.
I’ve noticed that there are: No ROCm-related tests or validation
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL/ROCm implementations), it would be very useful to include this test and it would be useful to add an explicit check because sometimes the error isnt visible.
Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards,
Missing Rocm autopkgtest Hello,
I am currently working on packaging genx.
I’ve noticed that there are: No Rocm autopkgtest/no autopkgtest opencl properly
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL it would be very useful to include Rocm and opencCl autopkgtest .
Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards,
severity :
tags :
Subject : Missing Rocm autopkgtest Hello,
I am currently working on packaging pyopencl.
I’ve noticed that there are: No Rocm autopkgtest
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL it would be very useful to include Rocm autopkgtest. Autopkgtests involving pyopencl fail, it would be useful to add an explicit check. Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards,
severity :
tags :
Subject : Missing OpenCL unit tests and autopkgtest /ROCm test Hello,
I am currently working on packaging compyle.
I’ve noticed that there are: No OpenCL unit tests and autopkgtest/ No ROCm-related tests or validation
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL/ROCm implementations), it would be very useful to include these tests.
Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards,
severity :
tags :
Subject : Missing OpenCL unit tests and autopkgtest /ROCm test Hello,
I am currently working on packaging gpyfft.
I’ve noticed that there are: No ROCm-related tests or validation
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL/ROCm implementations), it would be very useful to include this test and it would be useful to add an explicit check because sometimes the error isnt visible.
Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards,
Missing Rocm autopkgtest Hello,
I am currently working on packaging genx.
I’ve noticed that there are: No Rocm autopkgtest/no autopkgtest opencl properly
To help downstream maintainers and ensure runtime compatibility (especially across different OpenCL it would be very useful to include Rocm and opencCl autopkgtest .
Would you consider adding such test coverage in future releases?
Thanks in advance, and thank you for the work on this project.
Best regards,
= Setup =
Commandes pour dgit -gbp sbuild : sbuild
Consider moving your ~/.sbuildrc to ~/.config/sbuild/config.pl
schroot -l sbuild-update -ud testing
Commandes pour /usr/bin/autopkgtest -B ufo-filters --test-name=reconstruct -- unshare --release unstable --arch amd64 :
sudo apt install mmdebstrap sudo nano /etc/subuid longeac:100000:65536 sudo nano /etc/subuid longeac:100000:65536 /usr/bin/autopkgtest -B ufo-filters --test-name=reconstruct -- unshare --release unstable --arch amd64
Désactivation IPV6
sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1 sudo sysctl -w net.ipv6.conf.default.disable_ipv6=1 net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 sudo apt-get -o Acquire::ForceIPv4=true update sudo apt-get -o Acquire::ForceIPv4=true upgrade Acquire::ForceIPv4 "true"; ping -4 deb.debian.org echo 'Acquire::ForceIPv4 "true";' | sudo tee /etc/apt/apt.conf.d/99force-ipv4 sudo apt-get update
La connexion ne veut pas s'établir avec deb.debian.org 80
Trying 146.75.74.132... Connection failed: Connexion terminée par expiration du délai d'attente Trying 2a04:4e42:82::644... telnet: Unable to connect to remote host: Ne peut attribuer l'adresse demandée
LES MAILS
>Pour debian science ** Info for Rocm command add-on:
Subject: rocm test launcher modifications when there is other non-AMD GPU cards.
Dear Sir or Madame,
We have several NVIDIA cards and one AMD and want to test only on one, the AMD Radeon RX 6400 using this command rocm-test-launcher /debian/test/opencl. We encounter a problem when we want to run the test only on the AMD. The command takes all available cards, including NVDIA and AMD. We were able to solve the problem by lacing this command: OCL_ICD_VENDORS=/etc/OpenCL/vendors/amdocl64.icd rocm-test-launcher debian/tests/script, we would have to hide NVIDIA in order to test only on AMD Radeon RX 6400 . Rather than making a specific command for testing on the AMD or a specific card, would it be possible to add an option to the rocm-test-launcher /debian/test/opencl command, allowing specific selection of one or more cards for the test phases? Should we select the specific card we're interested in?
Best regards, Clément LONGEAC
> Discussion des tags debian pour ajouter les bugs pour rocm
Subject: Debian tag proposal for ROCm bug tracking
Hello,
I'am working on an overview of code compatibility with various AMD graphics cards, the codes on all the AMD boards available in the CI rocm. To equip the rocm package, I'm going to use the rocm-test-launcher script to enable installation/uninstallation tests on a blank virtual machine, the autopkgtest.A GSOC on the subjetc and the project was created by a confirmed Mentor: Cordell Bloorand and I'd like to know how to coordinate so as not to duplicate work.
I propose introducing a specific Debian tag to make it easier to track ROCm-related bugs, especially for packages that use OpenCL and autopkgtest.
I propose the tag: rocm-compat or rocm-testing
This would make it easier to coordinate efforts on ROCm support and to identify specific compatibility issues, ROCm-related bugs and missing or failed tests (?OpenCl , autopkgtest).
Does this type of tag seem relevant to you? Is there a previous tag?
Best regards, Clément LONGEAC
TODO...
se presenter et l'objet du stage sur debian-science FAIT
preparer un email explicant le probleme des machines avec plusieurs cartes graphiques, et si il etait possible de les cacher via le script de lancement rocm-test-launcher.FAIT
discuter sur debian-science d'un tag debian pour ajouter les bug pour rocm. Le mail est préparé au sujet du tag
trouver les test OpenCL s'il y en a. FAIT
si l'upstream utilise OpenCL mais n'a pas de test OpenCL, faire un bug report a l'upstream pour qu'il en fournisse. En cours BugReport
- Ajouter ce bug/url report dans une colonne upstream.
- si on trouve des test unitaires, ajouter un bug report Debian avec le bon tag.
- jouer les tests localement et reporter les bug...
pytools, compyle, gpyfft, pyvkfft, python-dtcwt, xpra, pysph, pynx, pyfai, sasmodels, silx, python-xrt
* running test via command line
AUTOPKGTEST_TMP=/tmp OCL_ICD_VENDORS=/etc/OpenCL/vendors/amdocl64.icd rocm-test-launcher debian/tests/script
* autopkgtest setup