← Back to issue list

The cleanbuild integration test is skipped

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1593529
Type
issue
State
closed
Author
~elopio
Labels
cleanbuild tests
Created
Updated
Closed

Current evaluation

Cleanbuild integration testing was re-enabled by snapcore/snapcraft#1610, merged as commit e38921ab3.

Resolution: closed resolved

Reason: Commit e38921ab3, titled "tests: reenable the cleanbuild integration test," landed through PR #1610 and directly implemented the requested test enablement.

Evaluated by: mr-cal-bot

No scores available.

Issue body

The cleanbuild integration test was failing in travis when we ran those test in there, so we skipped it. We are no longer running those tests in travis, and autopkgtest should be able to get it working in most of the cases, so this should be enabled. Also because of bug #1577548, this integration test should verify that the container is deleted.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Cleanbuild integration testing was re-enabled by snapcore/snapcraft#1610, merged as commit e38921ab3.
stealth/space-bunny-alpha — closed resolved Re-enabled the cleanbuild integration test in snapcraft via merged PR #1610, commit e38921ab3; the earlier WIP PR #1387 was closed.
stealth/space-bunny-alpha — closed resolved Re-enabled the cleanbuild integration test in snapcraft PR #1610 (commit e38921ab3), allowing it to run under autopkgtest now that Travis no longer runs it.
qwen/qwen3.6-35b-a3b — — Re-enabled the skipped cleanbuild integration test after Travis CI deprecation, utilizing autopkgtest for execution. Updated to verify container deletion per bug #1577548. Closed as fixed.
qwen/qwen3.6-35b-a3b — — Abandoned. The request to re-enable the skipped cleanbuild integration test and verify container deletion was closed without implementation, likely superseded by updated test infrastructure.
qwen/qwen3.6-35b-a3b — — The cleanbuild integration test remains skipped. The request to re-enable it and verify container deletion was closed without implementation, indicating the issue was abandoned.

Update history

Date Change
created

Related work

  • Likely Fixed By: snapcore/snapcraft#1610 (confidence 100%)

    Merged as commit e38921ab3 to re-enable the cleanbuild integration test.

  • Related To: snapcraft (launchpad)#1577548 (confidence 90%)

    Container cleanup behavior that the re-enabled test was expected to verify.

Related issues

Issue Project State Summary Similarity
#1803193 improve cleanbuild backwards compatibilty snapcraft (launchpad) closed Fixed by adding hidden cleanbuild YAML validation in snapcore/snapcraft#2404 (commit 248fe265d).
72%
#1387 [WIP] tests: reenable the cleanbuild integration test snapcraft closed WIP PR to re-enable the cleanbuild integration test sat unreviewed with 5 unresolved comments and was closed by sergiusens as "stale" (Oct 2017); the work landed later via PR #1610, commit e38921ab3.
71%
#1541332 Missing build-packages in integration tests snapcraft (launchpad) closed Fixed by merged PR ubuntu-core/snapcraft#289, adding gcc to integration-test build-packages in commit 6e6fe11d7.
70%
#1610 tests: reenable the cleanbuild integration test snapcraft merged Merged PR #1610 as commit e38921ab3, re-enabling the cleanbuild integration test and updating seven files (+69/-15).
70%