Remove assert from tracking provider

[igchor]

This assert would be triggered every time a memory is leaked by the application. Currently this happens in certain SYCL tests.
Ref: https://github.com/intel/llvm/actions/runs/9024914892/job/24800360426?pr=13343

Description

Checklist

• Code compiles without errors locally
• All tests pass locally
• CI workflows execute properly

• CI workflows, not executed per PR (e.g. Nightly), execute properly
• New tests added, especially if they will fail without my changes
• Added/extended example(s) to cover this functionality
• Extended the README/documentation
• All newly added source files have a license
• All newly added source files are referenced in CMake files
• Logger (with debug/info/... messages) is used

[bratpiorka]

Igor, please rebase. I think you need #473

[vinser52]

But it is triggered only in debug build.
Does llvm uses debug version of UMF?

[igchor]

But it is triggered only in debug build. Does llvm uses debug version of UMF?

I believe the build type is inherited from llvm.

[vinser52]

But it is triggered only in debug build. Does llvm uses debug version of UMF?

I believe the build type is inherited from llvm.

Is it because the UMF sources today are just fetched by UR and UR is built as a part of compiler build?

Anyway I am not against removing this assert

[igchor]

But it is triggered only in debug build. Does llvm uses debug version of UMF?

I believe the build type is inherited from llvm.

Is it because the UMF sources today are just fetched by UR and UR is built as a part of compiler build?

Anyway I am not against removing this assert

Yes, that's correct.

[igchor]

Igor, please rebase. I think you need #473

I am rebased: see my branch https://github.com/igchor/unified-memory-framework/tree/remove_assert

[igchor]

@bratpiorka restarting the CI solved the issue