Output build times for each pip package built

Metadata

Project: charmcraft
Number: #1842
Type: issue
State: open
Author: sed-i
Labels: —
Created: 2024-08-24 02:59 AM UTC
Updated: 2025-08-15 03:17 PM UTC
Closed: —

Current evaluation

Feature request (untriaged, no labels/comments): print per-package pip build times when packing with --no-binary so charm authors can see which deps (e.g. pydantic_core) dominate build time.

Suggested action: needs triage

Reason: issue_detail confirms the issue is 'Untriaged, no maintainer response' with zero labels and zero comments, so it has not been assessed by a maintainer — the default for unlabelled new issues. Code inspection shows installs are a single opaque `pip install --no-binary=:all:` invocation (charmcraft/charm_builder.py:286,302 and charmcraft/utils/package.py:117) wrapped only in a coarse `instrum.Timer("Installing all dependencies")`; grep found no per-package timing, `--report`, or duration output anywhere, so the feature is not implemented. Implementation is non-trivial because pip exposes no built-in per-package build duration, so the choice (parse pip output vs. time each package individually) is an open design decision the issue itself leaves open ('tree format similar to pipdeptree, or a flat list like strace... Either works :)'). Impact is moderate DX benefit rather than a bug.

Evaluated by: mr-cal-bot

Impact: 30 Quick Win: 7 Complexity: 55 Confidence: 80 Actionability: 55

Issue body

### What needs to get done During/after packing, please output the time it took to build each package. ### Why it needs to get done Since charmcraft packs with `--no-binary`, build times can be very long. It would be very useful for charm authors to know which parts of their deps contribute to build time. For example, we had no idea that it's `pydantic_core` that is the lengthy one and not `pydantic` itself. Such knowledge could help us in deciding if we want to keep a dep or drop it. For example, httpx takes a long time to build, so one might prefer using urllib instead. This could be either in a tree format similar to pipdeptree, or a flat list like strace. Either works :) ``` $ pipdeptree cosl==0.0.23 ├── ops [required: Any, installed: 2.15.0] │ ├── PyYAML [required: ==6.*, installed: 6.0.2] │ └── websocket-client [required: ==1.*, installed: 1.8.0] ├── pydantic [required: Any, installed: 2.8.2] │ ├── annotated-types [required: >=0.4.0, installed: 0.7.0] │ ├── pydantic_core [required: ==2.20.1, installed: 2.20.1] │ │ └── typing_extensions [required: >=4.6.0,!=4.7.0, installed: 4.12.2] │ └── typing_extensions [required: >=4.6.1, installed: 4.12.2] ├── PyYAML [required: Any, installed: 6.0.2] ├── tenacity [required: Any, installed: 9.0.0] └── typing_extensions [required: Any, installed: 4.12.2] ``` ``` $ strace -wc sleep 3 % time seconds usecs/call calls errors syscall ------ ----------- ----------- --------- --------- ---------------- 99.93 3.000132 3000132 1 clock_nanosleep 0.02 0.000542 18 30 12 openat 0.01 0.000425 19 22 mmap 0.01 0.000321 16 20 close 0.01 0.000272 15 18 fstat 0.01 0.000241 240 1 execve 0.00 0.000054 17 3 mprotect 0.00 0.000042 13 3 brk 0.00 0.000041 13 3 read 0.00 0.000022 11 2 pread64 0.00 0.000021 20 1 munmap 0.00 0.000015 15 1 futex 0.00 0.000015 14 1 prlimit64 0.00 0.000015 14 1 arch_prctl 0.00 0.000014 14 1 getrandom 0.00 0.000014 14 1 set_tid_address 0.00 0.000014 14 1 rseq 0.00 0.000014 13 1 set_robust_list 0.00 0.000012 12 1 1 access ------ ----------- ----------- --------- --------- ---------------- 100.00 3.002227 26805 112 13 total ```

Evaluation history

Date	Model	Scores	Action	Summary
2026-10-02 03:25 PM UTC	stealth/space-bunny-alpha	Impact: 30 Quick Win: 7 Complexity: 55 Confidence: 80 Actionability: 55	needs triage	Feature request (untriaged, no labels/comments): print per-package pip build times when packing with --no-binary so charm authors can see which deps (e.g. pydantic_core) dominate build time.
2026-09-18 06:24 AM UTC	qwen/qwen3.6-35b-a3b	Impact: 35 Quick Win: 13 Complexity: 40 Confidence: 60 Actionability: 60	needs triage	Feature request to output per-package build times during charmcraft packing with --no-binary. Untriaged, no maintainer response.
2026-09-01 12:26 AM UTC	qwen/qwen3.8-27b	Impact: 35 Quick Win: 21 Staleness: 75 Complexity: 40 Confidence: 70 Support Request: 10	needs triage	Feature request to output per-package build times during charmcraft pack, since --no-binary builds can be very slow. Open 737 days with no labels, no comments, and no maintainer response. The --no-binary behavior is still active in the codebase.
2026-07-22 11:47 AM UTC	qwen/qwen3.6-35b-a3b	Staleness: 95 Complexity: 45 Confidence: 75 Support Request: 10	needs triage	Feature request to log build times per pip package during packing to identify slow dependencies. Unlabelled, no maintainer response, inactive for over a year.
2026-07-07 10:06 PM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 85 Complexity: 45 Confidence: 90 Support Request: 10	needs triage	Feature request to output per-package build times during charmcraft packing to identify slow dependencies. Unlabelled with no maintainer comments or activity in over 10 months.
2026-07-05 03:53 AM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 85 Complexity: 45 Confidence: 90 Support Request: 15	needs triage	Feature request to log per-package build times during charmcraft packing to identify slow dependencies. Currently unlabelled and awaiting maintainer review.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.