Thomas Kemmer
Thomas Kemmer
Thanks for your patches and suggestions! I'm not currently involved in the Travis part but I have merged your other commits as d1b6f27cd2e79e16662ddbe44c0277cf79927d94...b89f49f05595703ee66097e4ef6717b67659e052.
I have removed the *vastly* outdated build instructions (including all remaining outdated URLs) from the document (a9daa6f12ee748762d4ad3e9647a4d4b9d66d0f1). Build instructions will be kept up-to-date online. Still to be done: * Screenshots...
This issue will become obsolete with the new rendering plugins; scheduled for BALL 1.6.
~~(1) Does not seem to be a problem anymore.~~ We will consider (2) as a build system feature for BALL 2.0.
Reopening (1) as separate issue.
Python tests should work once again. I have migrated all existing code (i.e., very few tests) to the unittest module. The tests still have to be included into CTest.
I have just pushed a patch (d35573af281c0379c44cd5481464c6e3b3bb0006) to make XDR optional so that VIEW/BALLView can be compiled again while this issue is being fixed.
This slider has only been introduced for RTfact in 864a020a556b9a3f0f57e3fa2fc8e37befb39ec0. This should be considered a defect anyway.
It seems that BALLView actually freezes while trying to read the assembly into a System, i.e., after the download has been completed successfully and after the assembly has been decompressed...
I had the same problem yesterday under Gentoo (same numbers): ``` checking [EXTRA] Additivity of energies w/ selection... (line 511 TEST_REAL_EQUAL(r4_r1 - r4_i, r1_r4 - r1_i): got -145.471, expected -103.957)...