← Back to issue list

test: debug lxd forkstart failure

View original Github issue

Metadata

Project
snapcraft
Number
#6380
Type
pull request
State
closed
Author
mr-cal
Labels
—
Created
Updated
Closed

Current evaluation

Debug-only PR by maintainer mr-cal to diagnose random LXD forkstart failures in OpenStack spread tests was closed unmerged after ~24 days with no reviews, 5 unresolved comments and failing lint/CLA checks.

Resolution: closed stale

Reason: PR #6380 was a purely diagnostic test change (+44/-9 across 3 files) that was closed without merge and with no reviewer comments or linked closing commit; 5 review comments remain unresolved and the file-lint and Canonical CLA checks were still failing. The underlying flake continues to be tracked in the still-open issue #6381.

Evaluated by: mr-cal-bot

No scores available.

Issue body

Test PR for debugging a LXD failure that randomly occurs in openstack but not openstack-dev. --- - [ ] I've followed the [contribution guidelines](https://github.com/canonical/snapcraft/blob/main/CONTRIBUTING.md). - [ ] I've signed the [CLA](http://www.ubuntu.com/legal/contributors/). - [ ] I've successfully run `make lint && make test`. - [ ] I've added or updated any relevant documentation. - [ ] In documents I changed, I [added a meta description](https://canonical-starflow.readthedocs-hosted.com/how-to/add-a-page-meta-description/) if one was missing. - [ ] I've updated the relevant release notes.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed stale Debug-only PR by maintainer mr-cal to diagnose random LXD forkstart failures in OpenStack spread tests was closed unmerged after ~24 days with no reviews, 5 unresolved comments and failing lint/CLA checks.
stealth/space-bunny-alpha — closed stale PR #6380 was closed unmerged after 24 days without reviews, leaving its diagnostic LXD forkstart test unused; CLA and file-lint checks were failing.
qwen/qwen3.6-35b-a3b — — Closed without merging. Submitted as a test to debug a flaky LXD forkstart failure, but received no reviews, had pending CLA and CI failures, and was ultimately abandoned.
qwen/qwen3.6-35b-a3b — — Closed without merging. Submitted as a test PR to debug a random LXD forkstart failure in OpenStack. Remained under review with unresolved comments and failing CI checks, indicating the debugging effort was abandoned.
qwen/qwen3.6-35b-a3b
Staleness: 5
Complexity: 40
Confidence: 90
keep open Test PR adding debug changes to investigate a random LXD forkstart failure in OpenStack. Currently pending maintainer review with several CI checks still running and CLA pending.

Update history

Date Change
closed
updated
closed
created

Related work

  • Related To: canonical/snapcraft#6381 (confidence 92%)

    Companion open issue documenting the random 'lxd forkstart' failures in OpenStack spread tests that this PR was meant to debug; reported upstream as canonical/lxd#18857.

Related issues

Issue Project State Summary Similarity
#6381 Openstack spread tests randomly fail with `Failed to run: /snap/lxd/current/sbin/lxd forkstart` snapcraft open Intermittent LXD 'forkstart' failures (<0.5%) in the OpenStack spread environment across craft repos; reproduced under heavy host memory/CPU pressure and reported upstream to canonical/lxd#18857, no snapcraft-side fix yet
74%
#4236 lxd-type-base spread test is flaky due to lxd timeouts snapcraft closed Flaky lxd-type-base spread test (LXC stop 'context deadline exceeded') fixed by PR #4239, squash-merged as commit ab2c13576 'spread: improve resilience of lxd-type-base test'.
70%