You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Investigate recent test failures, concurrent with upgrade of DPC++ to 2025.0.1 #1901
In [38]: [n for n in range(2, 265) if not test(n)]
Out[38]: [260, 261, 262, 263, 264]
In [39]: [n for n in range(2, 265) if not test(n)]
Out[39]: [256, 258, 259, 260, 261, 262, 263, 264]
In [40]: [n for n in range(2, 265) if not test(n)]
Out[40]: [257, 258, 259, 261, 262, 263]
The result is always empty for dpctl compiled with DPC++ 2025.0.0
changed the title [-]Investigate test failures with DPC++ 2025.0.1[/-][+]Investigate recent test failures, concurrent with upgrade of DPC++ to 2025.0.1[/+]on Nov 20, 2024
Activity
oleksandr-pavlyk commentedon Nov 20, 2024
With
I get
oleksandr-pavlyk commentedon Nov 20, 2024
The same thing with
oleksandr-pavlyk commentedon Nov 20, 2024
Seem to affect all data types:
Fix a lapse in logic for computing upper bound of iteration
Fix a lapse in logic for computing upper bound of iteration
Add changelog entry for fixing of gh-1901
Add a test based on example from gh-1901
[-]Investigate test failures with DPC++ 2025.0.1[/-][+]Investigate recent test failures, concurrent with upgrade of DPC++ to 2025.0.1[/+]oleksandr-pavlyk commentedon Nov 20, 2024
This failure is not related to the upgrade in the compiler, rather I introduced it recently by a code change during code maintenance: #1896
Merge pull request #1902 from IntelPython/bugfix/gh-1901-scan-algo