← Back to issue list

Spread should run the doc tests with a nonroot user

View original Github issue

Metadata

Project
rockcraft
Number
#651
Type
issue
State
open
Author
cjdcordeiro
Labels
Type: Documentation
Created
Updated
Closed
—

Current evaluation

Open request to run documentation Spread suites as a non-root user so public examples catch permission failures such as #649; spread.yaml currently defines no non-root test user.

Suggested action: keep open

Reason: The requirement is clear and remains unimplemented: the documentation suites in spread.yaml have no non-root configuration, while the body cites #649 as a concrete permission-sensitive documentation failure. Implementation must reconcile non-root ownership of test workspaces with existing root setup and sudo-based commands.

Evaluated by: mr-cal-bot

Impact: 45 Quick Win: 13 Complexity: 62 Confidence: 90 Actionability: 76

Issue body

### What needs to get done By default, Spread will run the test suites with `sudo`. To be more comprehensive, and specifically for the doc tests (which are public-facing code blocks that must be reproducible), Spread should also run the tests as a nonroot user. ### Why it needs to get done If we only run the tests with `sudo`, then we'll fail to identify documentation bits that ignore how permissions might be set in the user's working environment. For example - #649 . In this case, testing that code block with a nonroot user would've helped identify the documentation issue in advance.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 45
Quick Win: 13
Complexity: 62
Confidence: 90
Actionability: 76
keep open Open request to run documentation Spread suites as a non-root user so public examples catch permission failures such as #649; spread.yaml currently defines no non-root test user.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 13
Complexity: 40
Confidence: 75
Actionability: 70
keep open Request to run Spread doc tests as a nonroot user to catch permission-related documentation issues like #649. Open 787 days, 0 comments, labeled Type: Documentation.
qwen/qwen3.8-27b
Impact: 40
Quick Win: 26
Staleness: 55
Complexity: 35
Confidence: 72
Support Request: 5
keep open Request to run Spread doc tests as a nonroot user to catch permission-related documentation issues (e.g. #649). Open 768 days, last activity 263 days ago, 0 comments, labeled Type: Documentation, authored by a maintainer. No evidence of implementation yet.
qwen/qwen3.6-35b-a3b
Staleness: 85
Complexity: 40
Confidence: 70
Support Request: 10
needs triage Request to configure Spread to run documentation tests as a non-root user to catch permission-related documentation errors. Currently unaddressed with no maintainer comments or activity for over 7 months.
qwen3.6-35b-a3b-mtp-q6
Staleness: 80
Complexity: 25
Confidence: 70
Support Request: 0
needs triage Request to configure Spread to run documentation tests as a non-root user to catch permission-related issues. Currently open with no maintainer comments or activity in 208 days.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 25
Confidence: 60
Support Request: 0
needs triage Request to configure Spread to run documentation tests as a non-root user to catch permission issues. Open for over two years with no maintainer comments, assignee, or triage status.

Update history

No update history recorded yet.

Related work

  • Related To: rockcraft#649 (confidence 100%)

    The issue explicitly cites this Docker permission failure as an example that non-root documentation testing would detect.

Related issues

No related issues found above the similarity threshold.