← Back to issue list

unittests are not passing in armhf

View original Launchpad issue

Metadata

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

Current evaluation

Closed without resolution or comments, likely abandoned or superseded. The six failing armhf tests required architecture-agnostic updates to pass across all platforms.

Suggested action:

No scores available.

Issue body

There are 6 tests that assume they are not running in armhf. The unittests should be agnostic, and run the same on all architectures. ====================================================================== FAIL: test_build_is_dirty_from_project (snapcraft.tests.test_pluginhandler.IsDirtyTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python3.5/unittest/mock.py", line 1157, in patched return func(*args, **keywargs) File "/tmp/autopkgtest.sdXxxA/build.Jjd/snapcraft/snapcraft/tests/test_pluginhandler.py", line 1530, in test_build_is_dirty_from_project 'Expected build step to be dirty') AssertionError: False is not true : Expected build step to be dirty ====================================================================== FAIL: test_pull_is_dirty_from_project (snapcraft.tests.test_pluginhandler.IsDirtyTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python3.5/unittest/mock.py", line 1157, in patched return func(*args, **keywargs) File "/tmp/autopkgtest.sdXxxA/build.Jjd/snapcraft/snapcraft/tests/test_pluginhandler.py", line 1579, in test_pull_is_dirty_from_project 'Expected pull step to be dirty') AssertionError: False is not true : Expected pull step to be dirty ====================================================================== FAIL: test_push_a_snap (snapcraft.tests.test_commands_push.PushCommandTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/tmp/autopkgtest.sdXxxA/build.Jjd/snapcraft/snapcraft/tests/test_commands_push.py", line 82, in test_push_a_snap self.fake_logger.output) AssertionError: "Uploading my-snap-name_0.1_amd64.snap.\nRevision 9 of 'my-snap-name' created." not found in "Created snapcraft.yaml.\nEdit the file to your liking or run `snapcraft` to get started\nPreparing to pull my-part \nPulling my-part \nPreparing to build my-part \nBuilding my-part \nStaging my-part \nPriming my-part \nSnapped my-snap-name_0.1_armhf.snap\nUploading my-snap-name_0.1_armhf.snap.\nRevision 9 of 'my-snap-name' created.\n" ====================================================================== FAIL: test_push_and_release_a_snap (snapcraft.tests.test_commands_push.PushCommandTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/tmp/autopkgtest.sdXxxA/build.Jjd/snapcraft/snapcraft/tests/test_commands_push.py", line 196, in test_push_and_release_a_snap self.fake_logger.output) AssertionError: "Uploading my-snap-name_0.1_amd64.snap.\nRevision 9 of 'my-snap-name' created." not found in "Created snapcraft.yaml.\nEdit the file to your liking or run `snapcraft` to get started\nPreparing to pull my-part \nPulling my-part \nPreparing to build my-part \nBuilding my-part \nStaging my-part \nPriming my-part \nSnapped my-snap-name_0.1_armhf.snap\nUploading my-snap-name_0.1_armhf.snap.\nRevision 9 of 'my-snap-name' created.\nThe 'beta' channel is now open.\n" ====================================================================== FAIL: test_push_and_release_a_snap_to_N_channels (snapcraft.tests.test_commands_push.PushCommandTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/tmp/autopkgtest.sdXxxA/build.Jjd/snapcraft/snapcraft/tests/test_commands_push.py", line 245, in test_push_and_release_a_snap_to_N_channels self.fake_logger.output) AssertionError: "Uploading my-snap-name_0.1_amd64.snap.\nRevision 9 of 'my-snap-name' created." not found in "Created snapcraft.yaml.\nEdit the file to your liking or run `snapcraft` to get started\nPreparing to pull my-part \nPulling my-part \nPreparing to build my-part \nBuilding my-part \nStaging my-part \nPriming my-part \nSnapped my-snap-name_0.1_armhf.snap\nUploading my-snap-name_0.1_armhf.snap.\nRevision 9 of 'my-snap-name' created.\nThe 'beta,edge,candidate' channel is now open.\n" ====================================================================== FAIL: test_upload_raises_deprecation_warning (snapcraft.tests.test_commands_push.PushCommandTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/tmp/autopkgtest.sdXxxA/build.Jjd/snapcraft/snapcraft/tests/test_commands_push.py", line 150, in test_upload_raises_deprecation_warning self.fake_logger.output) AssertionError: "Uploading my-snap-name_0.1_amd64.snap.\nRevision 9 of 'my-snap-name' created." not found in "Created snapcraft.yaml.\nEdit the file to your liking or run `snapcraft` to get started\nPreparing to pull my-part \nPulling my-part \nPreparing to build my-part \nBuilding my-part \nStaging my-part \nPriming my-part \nSnapped my-snap-name_0.1_armhf.snap\nDEPRECATED: Use `push` instead of `upload`\nUploading my-snap-name_0.1_armhf.snap.\nRevision 9 of 'my-snap-name' created.\n" ----------------------------------------------------------------------

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Closed without resolution or comments, likely abandoned or superseded. The six failing armhf tests required architecture-agnostic updates to pass across all platforms.
qwen/qwen3.6-35b-a3b Closed without comments or resolution. The six armhf-specific test failures were likely fixed in a subsequent commit or the issue was abandoned due to inactivity.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1649899 integration tests fail in armhf snapcraft (launchpad) closed Integration tests for armhf remain disabled and require adjustments. The issue was closed without a fix, indicating the problem was abandoned pending future work.
75%