python / python/cpython

test_dtrace leaks temporary files on "PPC64LE CentOS9 LTO + PGO 3.x" buildbot

Open
#156,701 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

tests type-bug
Dominant language
Python
Stars
77.2k
Forks
35.9k
PR merge metrics
PR metrics pending

Description

PPC64LE CentOS9 LTO + PGO 3.x: https://buildbot.python.org/#/builders/885/builds/8098

0:06:23 load avg: 7.34 mem: 67.4 MiB Run 1 test in parallel using 1 worker process (timeout: 40 min, worker timeout: 45 min)
0:06:43 load avg: 7.17 mem: 67.6 MiB [1/1/1] test_dtrace failed (env changed)
Re-running test_dtrace in verbose mode
setUpClass (test.test_dtrace.BPFTraceNormalTests) ... skipped "bpftrace not available: [Errno 2] No such file or directory: 'bpftrace'"
setUpClass (test.test_dtrace.BPFTraceOptimizedTests) ... skipped "bpftrace not available: [Errno 2] No such file or directory: 'bpftrace'"
test_filter_probe_rows_ignores_warnings (test.test_dtrace.BPFTraceOutputTests.test_filter_probe_rows_ignores_warnings) ... ok
test_check_probes (test.test_dtrace.CheckDtraceProbes.test_check_probes) ... ok
test_missing_probes (test.test_dtrace.CheckDtraceProbes.test_missing_probes) ... expected failure
skipped 'dtrace(1) failed: /usr/bin/dtrace invalid option -q\nUsage /usr/bin/dtrace [--help] [-h | -G] [-C [-I<Path>]] -s File.d [-o <File>]'
setUpClass (test.test_dtrace.DTraceOptimizedTests) ... skipped 'dtrace(1) failed: /usr/bin/dtrace invalid option -q\nUsage /usr/bin/dtrace [--help] [-h | -G] [-C [-I<Path>]] -s File.d [-o <File>]'
setUpClass (test.test_dtrace.SystemTapNormalTests) ... skipped 'stap timed out during usability check'
setUpClass (test.test_dtrace.SystemTapOptimizedTests) ... skipped 'stap timed out during usability check'

----------------------------------------------------------------------
Ran 3 tests in 20.343s

OK (skipped=6, expected failures=1)

Warning -- test_dtrace leaked temporary files (2): stap8jlQ00, stapNGGnvV
Linked PRs
  • gh-156720

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with test.test_dtrace and the linked PR gh-156720, using the PPC64LE CentOS9 buildbot output to understand the two leaked temporary files. Run test_dtrace in a comparable environment and confirm that its temporary files are cleaned up after skipped or timed-out SystemTap checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing-qa
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.