Skip to main content

Browse the archive

Revision 32b1305c78c353c7b9241a2f1bac43788041240f authored by Elliot Saba on 21 March 2022, 20:33:24 UTC, committed by GitHub on 21 March 2022, 20:33:24 UTC 
More flexible test affinity setting (#44677)
 
* More flexibly test affinity setting

When running on a machine with `cpusets` applied, we are unable to
assign CPU affinity to CPUs 1 and 2; we may be locked to CPUs 9-16, for
example.  So we must inspect what our current cpumask is, and from that
select CPUs that we can safely assign affinity to in our tests.

* Import `uv_thread_getaffinity` from `print_process_affinity.jl`

* Call `uv_thread_getaffinity` only if `AFFINITY_SUPPORTED`

* Fix a syntax error

Co-authored-by: Takafumi Arakaki <aka.tkf@gmail.com>
1 parent 1eae65b
Raw File
.codecov.yml 
coverage:
  status:
    project: off
    patch: off
back to top