Sergey Pokhodenko

Define version to build with in build system, not recipe

1

To clarify. This should be >=1.19. Version of numpy to build with should be defined in build system. Now there is no such possibility. _Originally posted by @PokhodenkoSA in https://github.com/IntelPython/dpctl/pull/641#r738759730_

From time to time we face the situation when code is not changes but CI starts failing. This is usually happens because new development package appears on the channels. We...

CI for indicating that numba master does not break numba-dpex

6

- [ ] GitHub workflow for testing stable numba-dpex with numba master - [ ] Badge on main page - [ ] Possibility to subscribe to the status for Numba...

Draw block schema with data flow and provide info about tools available to debug each step.

- [x] Test scripts - [x] #566 - [x] #568 - [ ] #587 - [ ] #579 - [ ] Public CI

Need run GDB tests exclusively with other GPU tests. GDB for GPU hungs all other GPU tasks. _Originally posted by @PokhodenkoSA in https://github.com/IntelPython/numba-dppy/issues/568#issuecomment-926488627_

Need restart GDB test if received SIGTRAP

1

Need restart GDB test if received SIGTRAP ``` Thread 2.1 received signal SIGTRAP, Trace/breakpoint trap. [Switching to Thread 1.1073741888 (inactive)] 0x0000000000000000 in ?? () (gdb) ``` _Originally posted by @PokhodenkoSA...

Setting `debuginfo` to default value inside `compiler.Flags()` sounds like a great idea, if possible _Originally posted by @AlexanderKalistratov in https://github.com/IntelPython/numba-dppy/pull/424#discussion_r649947552_

DEBUG variable should be removed from numba_dppy.compiler. It will require replace callers code. It is for separate PR. _Originally posted by @PokhodenkoSA in https://github.com/IntelPython/numba-dppy/pull/354#r634417351_