[Bug]: Internal hashtable error: illegal key supplied! #7830
Comments
Hey @the-snork !Looks like it's your first time interacting with Armbian here on GitHub. Welcome and thank you for taking the time to report an issue ❤️. Don't forget to star ⭐ the repo. |
|
Jira ticket: AR-2611 |
|
Duplicate of #7744 -- not our bug -- go upgrade rsync |
actually it is, i would say in this case, this is through armbian's docker image |
Oh, then it warrants some investigation -- sorry for the early closure |
|
but anyway, let me recheck with an updated rsync in my host |
Seems the cache is being hit "too much" and we're shipping a broken version of `rsync` -- See armbian/build#7830 I will send a bigger change later making use of the new arm64 runners (so arm64 builds are not so slow - the main reason the cache was added in the first place)
|
There's indeed too much caching happening in the Docker build - armbian/docker-armbian-build#5 - @igorpecovnik could you either merge or give me permissions there? I've more changes later. |
|
added permissions. |
Seems the cache is being hit "too much" and we're shipping a broken version of `rsync` -- See armbian/build#7830 I will send a bigger change later making use of the new arm64 runners (so arm64 builds are not so slow - the main reason the cache was added in the first place)
|
Heh. Un-cached builds are failing due to arm64-on-amd64 qemu throwing segmentation faults. My guess? GH doesnt want people doing crossbuilds -- I had planned to rewrite those jobs to split over arm64 and amd64 GH runners and then join the resulting Docker images in a separate step "later", but I guess it will have to be "sooner". I'll try to make time ASAP |
|
I've had to split the Docker build matrix across arch'es (and join images later per-release), but finally we have updated Docker builds for both arches and all releases: @the-snork can you pull the latest image ( |
|
ps: |
No, known problem, I solved by using native arm64 runners. |
|
pps: by using native arm64 our docker builds are now 39 minutes -> 6 minutes faster. |
|
@rpardini - works for me; thanks. |
|
forgot close it.... sorry. |
What happened?
See https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2095004
[🐳|🌿] Copying files via rsync to [ / (MOUNT root) ]
[🐳|🔨]
[🐳|🔨] sent 1.68G bytes received 721.86K bytes 197.30M bytes/sec
[🐳|🔨] total size is 1.68G speedup is 1.00
[🐳|🌿] Copying files to [ /boot (MOUNT /boot) ]
[🐳|🔨] Internal hashtable error: illegal key supplied!
[🐳|🔨] rsync error: errors with program diagnostics (code 13) at hashtable.c(88) [generator=3.2.7]
[🐳|🔨] rsync error: received SIGUSR1 (code 19) at main.c(1613) [Receiver=3.2.7]
[🐳|💥] Error 13 occurred in main shell [ at /armbian/lib/functions/logging/runners.sh:211
run_host_command_logged_raw() --> lib/functions/logging/runners.sh:211
run_host_command_logged() --> lib/functions/logging/runners.sh:193
create_image_from_sdcard_rootfs() --> lib/functions/image/rootfs-to-image.sh:80
do_with_logging() --> lib/functions/logging/section-logging.sh:81
build_rootfs_and_image() --> lib/functions/main/rootfs-image.sh:104
full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:36
do_with_default_build() --> lib/functions/main/default-build.sh:42
cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25
armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136
cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176
main() --> compile.sh:50
]
[🐳|💥] Cleaning up [ please wait for cleanups to finish ]
How to reproduce?
Build on MacOS using compile.sh which in turn uses docker.
Tested with 1f69720; v24.11 works just fine.
Branch
main (main development branch)
On which host OS are you running the build script and observing this problem?
Other
Are you building on Windows WSL2?
Relevant log URL
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: