-
Notifications
You must be signed in to change notification settings - Fork 42
V0.12.x dev #1201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
V0.12.x dev #1201
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For tag checkout it's no surprise; for main we print full version during 'Configure' step.
[CI] Fix failing address sanitizer
Signed-off-by: Lukasz Dorau <[email protected]>
Add lld linker CI job
…an_error_handling_path_of_umf_ba_alloc Add missing `unlock()` in an error handling path of `umf_ba_alloc()`
Extend compatibility tests with GPU runners
Enable MT bench for disjoint_pool in fixed provider
optimize Disjoint Pool chunks
…verity check for alloc fails in disjoint pool init
Run Compatibility GPU CI jobs only on upstream, since forks do not have the required HW. Signed-off-by: Lukasz Dorau <[email protected]>
It fixes ThreadSanitizer data race in find_predecessor() vs critnib_insert() and critnib_remove(). Signed-off-by: Lukasz Dorau <[email protected]>
Check valgrind log files. Do not print an error message like: ls: cannot access './examples/umf_example_*.log': No such file or directory when only the tests log files are present for example. Signed-off-by: Lukasz Dorau <[email protected]>
…_find_ Use atomics in critnib find_*
…CI_jobs_only_on_upstream Run Compatibility GPU CI jobs only on upstream
Check valgrind log files
add missing nullcheck in critnib
Use atomics in find_successor() like in find_predecessor(). Ref: oneapi-src#1175 Signed-off-by: Lukasz Dorau <[email protected]>
Signed-off-by: Lukasz Dorau <[email protected]>
Multilevel maps are needed to support the case when one memory pool acts as a memory provider for another memory pool (nested memory pooling). Signed-off-by: Lukasz Dorau <[email protected]>
and move the step gathering info to the end (in multi numa CI).
…fFree Log pool pointer in `umfFree()`
Signed-off-by: Lukasz Dorau <[email protected]>
…ITIALIZED_error_in_cu2umf_result Handle `CUDA_ERROR_DEINITIALIZED` error in `cu2umf_result()`
Fix segfault in cu_memory_provider_get_last_native_error() when it is called after a CUDA device was destroyed. Signed-off-by: Lukasz Dorau <[email protected]>
[CI] Enable SLES in multi numa workflow
…ory_provider_get_last_native_error Fix segfault in `cu_memory_provider_get_last_native_error()`
…ults use current ctx and dev by default in CUDA prov
update benchmark scripts
Move C++ helper header to utils
…est_with_Fixed_provider Enable jemalloc pool test with Fixed provider
Install libnuma-dev in the proxy lib workflow, because it is required. It has worked correctly so far most probably, because libnuma-dev has been installed as a dependency of libhwloc-dev. It failed when libhwloc-dev was not installed. Signed-off-by: Lukasz Dorau <[email protected]>
…_the_proxy_lib_workflow Install libnuma-dev in the proxy lib workflow
Suppress false-positive in IPC tests under helgrind
Remove old SHM files /tmp/umf_file_provider_* (at the beginning of the test) left from the previous runs, because of crashes of the ipc_file_prov test. Signed-off-by: Lukasz Dorau <[email protected]>
…eft_from_the_previous_runs_because_of_crashes Remove old SHM files left from the previous runs because of crashes
fix jemalloc benchmark with fixedprovider
increase number of threads in benchmarks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Checklist