Open yuzibo opened 1 month ago
Finaly, I have pushed the 1.1.6 tag!
wow, thanks!
This time I ask for help how to run tests.:)
Here one document, but I tired to run it:
(sid-amd64-sbuild)root@dev:/home/vimer/build/rfs/gl4es/gl4es_ds/obj-x86_64-linux-gnu# xvfb-run ctest
Test project /home/vimer/build/rfs/gl4es/gl4es_ds/obj-x86_64-linux-gnu
Start 1: GLXgears
1/8 Test #1: GLXgears .........................***Failed 0.05 sec
Start 2: StuntCarRacer
2/8 Test #2: StuntCarRacer ....................***Failed 0.38 sec
Start 3: Neverball
3/8 Test #3: Neverball ........................***Failed 0.06 sec
Start 4: FoobillardPlus
4/8 Test #4: FoobillardPlus ...................***Failed 0.26 sec
Start 5: Descent3
5/8 Test #5: Descent3 .........................***Failed 0.20 sec
Start 6: PointSprite
6/8 Test #6: PointSprite ......................***Failed 0.12 sec
Start 7: OpenRA_GLES2
7/8 Test #7: OpenRA_GLES2 .....................***Failed 0.11 sec
Start 8: GLSL_lighting_GLES2
8/8 Test #8: GLSL_lighting_GLES2 ..............***Failed 0.07 sec
0% tests passed, 8 tests failed out of 8
Total Test time (real) = 1.26 sec
The following tests FAILED:
1 - GLXgears (Failed)
2 - StuntCarRacer (Failed)
3 - Neverball (Failed)
4 - FoobillardPlus (Failed)
5 - Descent3 (Failed)
6 - PointSprite (Failed)
7 - OpenRA_GLES2 (Failed)
8 - GLSL_lighting_GLES2 (Failed)
Errors while running CTest
Output from these tests are in: /home/vimer/build/rfs/gl4es/gl4es_ds/obj-x86_64-linux-gnu/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
if verbose:
Test project /home/vimer/build/rfs/gl4es/gl4es_ds/obj-x86_64-linux-gnu
Start 1: GLXgears
1/8 Test #1: GLXgears .........................***Failed 0.04 sec
-- Starting test in GLES 1...
-- Ran test.
Error: error: unavailable function glXChooseFBConfig
Output: Test returned a non-zero status 1 (segmentation fault?)
Failed to get snapshot
-- Starting test in GLES 2...
-- Ran test.
Error: error: unavailable function glXChooseFBConfig
Output: Test returned a non-zero status 1 (segmentation fault?)
Failed to get snapshot
CMake Error at /home/vimer/build/rfs/gl4es/gl4es_ds/test.cmake:59 (message):
Test(s) failed while using GLES 1;2
...
Or I can disable the tests during the build, then to run a sample hello,world
to link the lib that is okay also.
Thay will probably not work. They are fane-tuned and basicaly only work on the Pandora. I would suggest to isgnore the test for now.
Hi,
I am packaging the package on Debian. But I found the latest tag was almost 4 years ago. But the important is that we have to remove the
debian/
dir which was pushed here three years ago. In other words. in v1.1.4, there is nodebian/
dir in the upstream tarball. So I have to ask here, could we push a new tag includingdebian/
dir?In Debian policy, we will remove
debian/
dir from upstream. So, if I am working on v1.1.4 directly, we will upload the binary package into NEW queue twice to get approval from ftp-master. This is not necessnary.