Skip to content

Conversation

@duskmoss
Copy link
Contributor

Hi, just making an update build for incus @dkwo

Removed umoci from the readme because 6.13 removed it as a dependency.

I will also make a PR to remove it from the void docs.

(if there is a consensus on whether we want this info in only one place, I can adjust this PR to remove the README or adjust void docs to not have the redundant information) @classabbyamp

Testing the changes

  • I tested the changes in this PR: YES

@duskmoss
Copy link
Contributor Author

void-linux/void-docs#852

@dkwo
Copy link
Contributor

dkwo commented Aug 20, 2025

Some incusd tests are failing on aarch64 with Initialize LXC: allocating the container failed, but they also fail on master branch.
(I am fine deleting readme if all info is now in the docs.)

@dkwo
Copy link
Contributor

dkwo commented Aug 20, 2025

it is failing TestContainerTestSuite/TestContainer_AddRoutedNicValidation and TestValidateConfig:

Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo
Failed to create lock for testFoo2
Failed to create lock for isol-2
Failed to create lock for isol-1
Failed to create lock for isol-5
Failed to create lock for isol-4
Failed to create lock for isol-3
Failed to create lock for isol-2
Failed to create lock for isol-1
Failed to create lock for isol-0
Failed to create lock for isol-2
Failed to create lock for isol-1
Failed to create lock for isol-1
--- FAIL: TestContainerTestSuite (2.87s)
    --- FAIL: TestContainerTestSuite/TestContainer_AddRoutedNicValidation (0.21s)
        instance_test.go:309: 
            	Error Trace:	/builddir/incus-6.12.0/cmd/incusd/instance_test.go:309
            	Error:      	Received unexpected error:
            	           	Initialize LXC: allocating the container failed
            	Test:       	TestContainerTestSuite/TestContainer_AddRoutedNicValidation
            	Messages:   	Adding multiple routed with gateway mode ['none'] should succeed. 
2025/08/20 20:43:27 Running test #0: Single port
2025/08/20 20:43:27 Running test #1: Multiple ports
2025/08/20 20:43:27 Running test #2: Port range
2025/08/20 20:43:27 Running test #3: Mixed ports and port ranges
2025/08/20 20:43:27 Running test #4: UDP
2025/08/20 20:43:27 Running test #5: Unix socket
2025/08/20 20:43:27 Running test #6: Abstract unix socket
2025/08/20 20:43:27 Running test #7: Unknown connection type
2025/08/20 20:43:27 Running test #8: Valid IPv6 address (1)
2025/08/20 20:43:27 Running test #9: Valid IPv6 address (2)
2025/08/20 20:43:27 Running test #10: Valid IPv6 address (3)
2025/08/20 20:43:27 Running test #11: Valid IPv6 address (4)
2025/08/20 20:43:27 Running test #12: Invalid IPv6 address (1)
2025/08/20 20:43:27 Running test #13: Invalid IPv6 address (2)
Failed to create lock for hal9000
FAIL
FAIL	github.com/lxc/incus/v6/cmd/incusd	4.460s
Failed to create lock for c1
--- FAIL: TestValidateConfig (0.00s)
    main_migrate_test.go:100: 
        	Error Trace:	/builddir/incus-6.12.0/cmd/lxc-to-incus/main_migrate_test.go:100
        	Error:      	Received unexpected error:
        	           	allocating the container failed
        	Test:       	TestValidateConfig
2025/08/20 20:43:23 Running test #0: invalid path
Processing storage configuration
2025/08/20 20:43:23 Running test #1: ignored default mounts
Processing storage configuration
2025/08/20 20:43:23 Running test #2: ignored mounts
Processing storage configuration
2025/08/20 20:43:23 Running test #3: valid mount configuration
Processing storage configuration
--- FAIL: TestConvertStorageConfig (0.00s)
    main_migrate_test.go:336: 
        	Error Trace:	/builddir/incus-6.12.0/cmd/lxc-to-incus/main_migrate_test.go:336
        	Error:      	Received unexpected error:
        	           	Invalid path: /home
        	Test:       	TestConvertStorageConfig
2025/08/20 20:43:23 Running test #0: missing lxc.rootfs key
2025/08/20 20:43:23 Running test #1: valid lxc.rootfs key (1)
2025/08/20 20:43:23 Running test #2: valid lxc.rootfs key (2)
FAIL
FAIL	github.com/lxc/incus/v6/cmd/lxc-to-incus	0.007s

@duskmoss
Copy link
Contributor Author

duskmoss commented Aug 20, 2025

I don't think I can run the tests with a cross build right? Do you have any ideas on whats wrong?

Edit, just saw they also fail on master, to confirm you mean void-packages master, so it's not added with this update?

@dkwo
Copy link
Contributor

dkwo commented Aug 21, 2025

Yes, it is void master. Can you rebase this pr on master? Perhaps even temporarily switch to native aarch64 ci, like first commit here #54013 ?
I wonder if these new failures are due to recent util-linux update, or my machine running newer coreutils, or else..

@duskmoss
Copy link
Contributor Author

I don't have any aarch64 machines.

@classabbyamp classabbyamp merged commit 0e7b251 into void-linux:master Aug 22, 2025
8 checks passed
@dkwo
Copy link
Contributor

dkwo commented Aug 23, 2025

I cannot reproduce on my other aarch64 machine, so perhaps this is related to newer coreutils (to be seen).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants