Yocto Wayland / RaspberryPi4-64

Linux
1

Hello,

I’ve started working on a Wayland implementation. I have a first pass on the UnitTestRunner app building. Only a few errors; below, and some questions.

Questions:

  1. Do the test numbers match the code I have noted? I figured the were by order of occurrence.
  2. Does UnitTestRunner complete 100% on a RaspberryPi 32-bit image? Which distro/image?
  3. What’s the smallest code/ram size one can get a full-screen JUCE app? Presuming link-time optimization is used.
  4. The below SIMD test asserts, but completes. Is that expected?

Thanks,
Joel

-----------------------------------------------------------------
Starting test: Files / Writing...

!!! Test 43 failed
JUCE Assertion failure in juce_UnitTest.cpp:280

FAILED!!  1 test failed, out of a total of 53
-----------------------------------------------------------------

        tempFile.setReadOnly (true);
43.        expect (! tempFile.hasWriteAccess());
-----------------------------------------------------------------
Starting test: Sockets / StreamingSocket...

!!! Test 6 failed
!!! Test 7 failed
!!! Test 9 failed
!!! Test 10 failed

FAILED!!  4 tests failed, out of a total of 14
-----------------------------------------------------------------

6.	expect (socket.connect (localHost.toString(), portNum));
7.	expect (socket.isConnected() == true);
9.	expect (socket.getBoundPort() != -1);
10.	expect (socket.getRawSocketHandle() != invalidSocket);
-----------------------------------------------------------------

Starting test: SIMDRegister UnitTests / CheckTruncate...
JUCE Assertion failure in juce_fallback_SIMDNativeOps.h:129
All tests completed successfully
-----------------------------------------------------------------
1 Like
2

If you run the UnitTestRunner in a debugger then the program will break on an assertion failure. That’ll show you exactly what’s failing in the unit tests.

1 Like