You are not logged in.
Guys,
I am very new to Arch I installed it because it was the recommended linux distro for my T2 mac, and it's been wonderful so far.
However, now I need to install aws-workspaces-bin, a client for AWS Workspaces, from AUR.
This binary depends on hiredis0.14. Trying to run the `makepkg` on hiredis0.14, I see that the installer is running a series of tests, and this test is always failing:
I see these warnings prior to the test:
==> Starting check()...
cc -std=c99 -pedantic -c -O3 -fPIC -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer - mno-omit-leaf-frame-pointer -g -ffile-prefix-map=/home/jason/Setup/hiredis0.14/src=/usr/src/debug/hiredis0.14 -flto=auto -Wall -W -Wstrict-prototypes -Wwrite-strings -g -ggdb test.c
test.c: In function ‘test_blocking_connection_timeouts’:
test.c:544:17: warning: unused variable ‘cmd’ [-Wunused-variable]
544 | const char *cmd = "DEBUG SLEEP 3\r\n";
| ^~~
test.c:543:13: warning: unused variable ‘s’ [-Wunused-variable]
543 | ssize_t s;
| ^
cc -O3 -fPIC -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -g -ffile-prefix-map=/home/jason/Setup/hiredis0.14/src=/usr/src/debug/hiredis0.14 -flto=auto -Wall -W -Wstrict-prototypes -Wwrite-strings -g -ggdb -o hiredis-test -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -Wl,-z,pack-relative-relocs -flto=auto test.o libhiredis.a
170300:C 24 Mar 2025 09:13:03.090 * Reading config from stdin
170300:C 24 Mar 2025 09:13:03.090 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
./hiredis-test -h 127.0.0.1 -p 56379 -s /tmp/hiredis-test-redis.sock || \
( kill `cat /tmp/hiredis-test-redis.pid` && false )Then, test #39 always fails after about 5 minutes of churning:
#39 Returns error when host cannot be resolved: FAILEDI poked around and found this source code, defining the test:
static void test_blocking_connection_errors(void) {
redisContext *c;
test("Returns error when host cannot be resolved: ");
c = redisConnect((char*)"idontexist.test", 6379);
test_cond(c->err == REDIS_ERR_OTHER &&
(strcmp(c->errstr,"Name or service not known") == 0 ||
strcmp(c->errstr,"Can't resolve: idontexist.test") == 0 ||
strcmp(c->errstr,"nodename nor servname provided, or not known") == 0 ||
strcmp(c->errstr,"No address associated with hostname") == 0 ||
strcmp(c->errstr,"Temporary failure in name resolution") == 0 ||
strcmp(c->errstr,"hostname nor servname provided, or not known") == 0 ||
strcmp(c->errstr,"no address associated with name") == 0));
redisFree(c);I installed redis as a service and I can see the service running, and port 6379 listening.
I am stuck here. Can anyone suggest a solution, or some more troubleshooting?
Thanks in advance!
Last edited by chewmanfoo (2025-03-24 14:23:19)
Offline
Since testing functions are mostly for lib developer verification, the easiest here for you as an end user would be to bypass those for now. makepkg has the --nocheck flag to not run the check function.
Offline
Mod note: moving to AUR Issues
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
@V1del,
is this a safe recommendation, or will I end up wishing I had not fixed this issue now?
Offline
For clarity :
Aur doesn't have an aws-workplaces-bin pacakge , but there are 2 packages with a similar name :
amazon-workspaces-bin and amazon-workspaces-legacy-bin
Which of those packages is this about ?
Based on my experience tests failing on git versions is rather common and often solved with later commits.
Test failures with stable versions are a bad sign and should be reported upstream.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline