[erlang-questions] Desperately looking for official Erlang tests results

REIX, Tony tony.reix@REDACTED
Thu Mar 2 17:33:45 CET 2017

Hi Björn

Thanks for studying.

I had already looked at these error messages. Here is below what I got about test.emulator_test .

This is due to : ts_install_cth failed! exit:{{make_failed,make},[{ts_make,make,1,

I have this issue both on AIX and on FC25/x86_64.
I guess that this issue should NOT appear on FC25/x86_64. However, I have it 48 times.

On AIX, there are probably MANY reasons why this ts_install_cth failed.
However, on FC25./x86_64, I am VERY surprised that this fails.
However, the guy who ported Erlang on FC25/x86_64 said to me that he did not run the Erlang tests...
Since I found that their RPM .spec file was missing a Request: instruction for the C++ compiler (leading to errors at build), I guess that their .spec file may contain other issues.

However, I have NO idea about how I can find the root cause of this ts_install_cth failulre. I have already tried.


=== Config function: ct_framework:init_per_suite/1 (click for source code)

=== Group properties: [{suite,a_SUITE}]

=== Config value:


=== Current directory is "/root/rpmbuild/BUILD/otp-OTP-19.2.3/release/tests/test_server/ct_run.test_server@REDACTED"

=== Started at 2017-03-01 16:58:31

Making "/root/rpmbuild/BUILD/otp-OTP-19.2.3/release/tests/emulator_test/a_SUITE_data/Makefile"
gcc -c -fPIC -D_THREAD_SAFE -D_REENTRANT -g -O2 -D_THREAD_SAFE -D_REENTRANT  -I/root/rpmbuild/BUILD/otp-OTP-19.2.3/erts/emulator/beam -I/root/rpmbuild/BUILD/otp-OTP-19.2.3/erts/emulator -I/root/rpmbuild/BUILD/otp-OTP-19.2.3/erts/emulator/sys/unix -I/root/rpmbuild/BUILD/otp-OTP-19.2.3/erts/include -I/root/rpmbuild/BUILD/otp-OTP-19.2.3/erts/include/x86_64-unknown-linux-gnu -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DHAVE_LIBM=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_LINUX_TCP_H=1 -DHAVE_SANE_LINUX_TCP_H=1 -DHAVE_POLL_H=1 -DHAVE_STRERROR=1 -DHAVE_VSNPRINTF=1 -DHAVE_USLEEP=1 -DHAVE_LIBRESOLV=1 -DHAVE_RES_GETHOSTBYNAME=1 -DHAVE_FINITE=1 timer_driver.c

In file included from /root/rpmbuild/BUILD/otp-OTP-19.2.3/erts/emulator/beam/erl_driver.h:40:0,

                 from timer_driver.c:6:

/root/rpmbuild/BUILD/otp-OTP-19.2.3/erts/emulator/beam/erl_drv_nif.h:76:34: erreur fatale : erl_int_sizes_config.h : No such file or directory

 #include "erl_int_sizes_config.h"


compilation terminée.

Makefile:13 : la recette pour la cible « timer_driver.so » a échouée

make: *** [timer_driver.so] Erreur 1

*** User 2017-03-01 16:58:31.290 ***
ts_install_cth failed! exit:{{make_failed,make},[{ts_make,make,1,

*** CT Error Notification 2017-03-01 16:58:31.291 ***
Error detected: ts_install_cth

Full error description and stacktrace

=== Ended at 2017-03-01 16:58:31
=== Location: {ct_framework,init_per_suite}
=== Reason: {ts_install_cth,
*** init_per_suite failed.
    Skipping all cases.


Tony Reix

Bull - ATOS
IBM Coop Architect & Technical Leader
Office : +33 (0) 4 76 29 72 67
1 rue de Provence - 38432 Échirolles - France

De : bgustavsson@REDACTED [bgustavsson@REDACTED] de la part de Björn Gustavsson [bjorn@REDACTED]
Envoyé : jeudi 2 mars 2017 17:05
À : REIX, Tony
Cc : erlang-questions@REDACTED; GIRARDET, JEAN
Objet : Re: [erlang-questions] Desperately looking for official Erlang tests results

On Thu, Mar 2, 2017 at 4:26 PM, REIX, Tony <tony.reix@REDACTED> wrote:
> Resending this email WITHOUT the attachment since it is too big to be sent
> without some approval.

It seems to have been approved now. I have received the other email.

I have taken a quick look at the log.

The major problem is that many test cases that call init_per_SUITE fail
when they attempt to compile C code during the running of the test suite,
especially when running emulator_tests. You should be able to
find more information from the generated html files. Starting
with index.html, you could click on test.emulator_test. On that page,
you could click on the links for the failed test cases. On the
page for a failed init_per_SUITE test case, you should be able
to see why the compilation failed. (Those failed test cases cause
all test in the same module to be skipped.)

On other thing so far: erl_boot_server_SUITE is not a good test
suite. It has some hard-coded assumptions about our
testing environment. It will fail outside our lab.


Björn Gustavsson, Erlang/OTP, Ericsson AB

More information about the erlang-questions mailing list