Daniel Markstedt
Daniel Markstedt
It is specifically the validation frequency that causes this failure. If you set it to anything >1 then the tests fail. This work fine for instance. ``` dircachesize = 131072...
What all the failing tests have in common is that you execute file system operations with user 1, then immediately does something with the newly created file or dir with...
Cheers, let me know how your investigations go. Fingers crossed that it's a straight-forward fix.
Also, apologies that I didn't think about running the spectest with dircache optimized settings earlier. It occurred to me as I was running tests in preparation for tagging the release!
@delan So if I understand this correctly, if you configure the SCCD with the correct sector size that your SPARCstation expects, you get past this issue?
Got it! So in this case, piscsi works as intended, and what you observed is akin to hooking up an incompatible consumer grade CD-ROM drive to your UNIX workstation. As...
Fair point. I read the report too quickly and thought the panic was in the host system.
Fails with clang: error: clang frontend command failed with exit code 139 (use -v to see invocation)
At a glance this looks like the same issue that was discussed at our Discord channel the other day. While it wasn't clear exactly what worked for that person, I...
Fails with clang: error: clang frontend command failed with exit code 139 (use -v to see invocation)
This is the compiler using up all of the memory on the RPi and crashing with OOM. It is better to cross compile for either of the Zero models.
The same problem happens in `cryptocb.h` here, which leads to compile errors with missing types defined in the AES headers. https://github.com/wolfSSL/wolfssl/blob/c3900470aaff38f46fca225aec7b572c5ecda02d/wolfssl/wolfcrypt/cryptocb.h#L290 ``` [205/255] Compiling C object etc/uams/uams_dhx_pam.so.p/uams_dhx_pam.c.o FAILED: etc/uams/uams_dhx_pam.so.p/uams_dhx_pam.c.o cc...