Handle possible NULL return from DPCTLDevice_GetMaxWorkGroupSize1d, 2d

oleksandr-pavlyk commented 1 month ago

Python code now checks that the return value of DPCTLDevice_GetMaxWorkGroupSize1d and DPCTLDevice_GetMaxWorkGroupSize2d is not NULL before dereferencing.

[x] Have you provided a meaningful PR description?
[ ] Have you added a test, reproducer or referred to an issue with a reproducer?
[ ] Have you tested your changes locally for CPU and GPU devices?
[ ] Have you made sure that new changes do not introduce compiler warnings?
[ ] Have you checked performance impact of proposed changes?
[ ] If this PR is a work in progress, are you opening the PR as a draft?

github-actions[bot] commented 1 month ago

Deleted rendered PR docs from intelpython.github.com/dpctl, latest should be updated shortly. :crossed_fingers:

coveralls commented 1 month ago

coverage: 87.943% (-0.03%) from 87.971% when pulling 3952ef7e9e54f010295f9c40e466f257f144f2e0 on handle-possible-errors into 183bfd77d6537d71146c23262e47dc84ae5ae336 on master.

github-actions[bot] commented 1 month ago

Array API standard conformance tests for dpctl=0.18.0dev0=py310h15de555_8 ran successfully. Passed: 889 Failed: 16 Skipped: 91

IntelPython / dpctl

Handle possible NULL return from DPCTLDevice_GetMaxWorkGroupSize1d, 2d #1690