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
native-deep: first-run findings (coverage time, affinity tests under ASan, coverage-labels test) #769
The first run of the weekly report-only `native-deep.yml` workflow (from #762, run 43171495302) completed, with these findings to triage:
Coverage job time. The instrumented pytest took 2 h 25 min against the job's 240-minute timeout, which leaves little margin. Options: shard it, or cover the native tests plus a targeted Python subset.
Affinity tests under ASan and coverage. `test_the_process_pool_follows_the_affinity_mask` fails (`assert 1 == 2`) in both the extension-asan and the coverage jobs. It is probably the setarch/ASan environment narrowing CPU affinity. Either skip the test there with a stated reason, or widen the mask.
Coverage-labels test. `test_coverage_labels.py::test_label_collector_counts_concurrent_calls_and_escapes` raises StopIteration only in the coverage build.
Results to triage:
include-cleaner report (24 KB artifact);
coverage totals of about 76 % lines, 81 % functions and 76 % regions. Its dead-code list feeds the lean-plan native structure PR.
Trigger. The workflow also runs on a pull request that changes the workflow file itself. Keep that trigger, or drop it.
Activity