[erlang-questions] Port of Erlang (19.2) on AIX

REIX, Tony tony.reix@REDACTED
Tue Jan 17 14:18:06 CET 2017


Resending without the attachment.

Tony

Le 17/01/2017 à 11:52, Tony REIX a écrit :

Hi,

With :
      --disable-hipe --disable-threads --disable-smp-support --without-javac

I've been able to build Erlang and to launch the tests by:  ct_run -suite ../compiler_test/andor_SUITE -case t_orelse

However, it fails at beginning: "Failed to start CTH", and it talks about a file "see the CT Log for details"" that I have no idea where it is.

I've only found at: otp_src_19.2/release/tests/test_server :
   ./ct_run.ct@REDACTED/tests.compiler_test.andor_SUITE.t_orelse.logs/run.2017-01-17_11.14.50/suite.log
but it does not help a lot

Any idea which document/file I should have a look at in order to understand the root cause of the failing testing ?
Any idea about the root cause of the failure ?


I've also tried with : erl -s ts install -s ts run all_tests -s init stop .

But it crashes:  init terminating in do_boot

Crash dump

Looking at: erl_crash.dump , I see:  Current Process CP: 0x00000000 (invalid)

erl_crash.dump file is attached to this email. REMOVED


I guess that I have to learn a little bit ( ;) ) more about how Erlang works.

See below for details.


Thanks

Tony


1) Launch tests :

+ cd /opt/freeware/src/packages/BUILD/otp_src_19.2/release/tests//test_server
+ /opt/freeware/src/packages/BUILD/otp_src_19.2/bin/ct_run -suite ../compiler_test/andor_SUITE -case t_orelse

Common Test starting (cwd is /opt/freeware/src/packages/BUILD/otp_src_19.2/release/tests/test_server)

Eshell V8.2  (abort with ^G)
(ct@REDACTED)1>
Common Test: Running make in test directories...
(ct@REDACTED)1> Recompile: andor_SUITE
(ct@REDACTED)1> andor_SUITE.erl:83: Warning: this clause cannot match because of different types/sizes
(ct@REDACTED)1> andor_SUITE.erl:86: Warning: this clause cannot match because a previous clause always matches
(ct@REDACTED)1> andor_SUITE.erl:87: Warning: this clause cannot match because a previous clause always matches
(ct@REDACTED)1> andor_SUITE.erl:92: Warning: this clause cannot match because of different types/sizes
(ct@REDACTED)1> andor_SUITE.erl:169: Warning: the guard for this clause evaluates to 'false'
(ct@REDACTED)1> andor_SUITE.erl:170: Warning: the guard for this clause evaluates to 'false'
(ct@REDACTED)1> andor_SUITE.erl:170: Warning: the result of the expression is ignored (suppress the warning by assigning the expression to the _ variable)
(ct@REDACTED)1> andor_SUITE.erl:171: Warning: the guard for this clause evaluates to 'false'
(ct@REDACTED)1> andor_SUITE.erl:172: Warning: the guard for this clause evaluates to 'false'
(ct@REDACTED)1> andor_SUITE.erl:179: Warning: this expression will fail with a 'badarg' exception
(ct@REDACTED)1> andor_SUITE.erl:194: Warning: this clause cannot match because a previous clause at line 194 always matches
(ct@REDACTED)1> andor_SUITE.erl:195: Warning: the guard for this clause evaluates to 'false'
(ct@REDACTED)1> andor_SUITE.erl:196: Warning: the guard for this clause evaluates to 'false'
(ct@REDACTED)1> andor_SUITE.erl:197: Warning: the guard for this clause evaluates to 'false'
(ct@REDACTED)1> andor_SUITE.erl:227: Warning: this clause cannot match because a previous clause at line 227 always matches
(ct@REDACTED)1> andor_SUITE.erl:228: Warning: this clause cannot match because a previous clause at line 228 always matches
(ct@REDACTED)1> andor_SUITE.erl:229: Warning: this clause cannot match because a previous clause at line 229 always matches
(ct@REDACTED)1> andor_SUITE.erl:230: Warning: the guard for this clause evaluates to 'false'
(ct@REDACTED)1> Recompile: test_lib
(ct@REDACTED)1>
CWD set to: "/opt/freeware/src/packages/BUILD/otp_src_19.2/release/tests/test_server/ct_run.ct@REDACTED"<mailto:/opt/freeware/src/packages/BUILD/otp_src_19.2/release/tests/test_server/ct_run.ct@REDACTED>
(ct@REDACTED)1>
TEST INFO: 1 test(s), 1 case(s) in 1 suite(s)

(ct@REDACTED)1> Testing tests.compiler_test.andor_SUITE.t_orelse: Starting test, 1 test cases
(ct@REDACTED)1>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Error detected: "Failed to start CTH, see the CT Log for details"
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

(ct@REDACTED)1> Testing tests.compiler_test.andor_SUITE.t_orelse: *** FAILED {andor_SUITE,init_per_suite} ***
(ct@REDACTED)1> Testing tests.compiler_test.andor_SUITE.t_orelse: TEST COMPLETE, 0 ok, 0 failed, 1 skipped of 1 test cases


2) ./ct_run.ct@REDACTED/tests.compiler_test.andor_SUITE.t_orelse.logs/run.2017-01-17_11.14.50/suite.log

=== Suite started at 2017-01-17 11:14:50
=== Starting test, 1 test cases
=cases         1
=user          root
=host          hardy1
=hosts         hardy1
=emulator_vsn  8.2
=emulator      beam
=otp_release   19
=started       2017-01-17 11:14:50
=case          andor_SUITE:init_per_suite
=logfile       andor_suite.init_per_suite.html
=started       2017-01-17 11:14:50
=ended         2017-01-17 11:14:50
=result        failed: "Failed to start CTH, see the CT Log for details", [{andor_SUITE,
                                                                            init_per_suite}]
=== *** FAILED {andor_SUITE,init_per_suite} ***
===
=case          andor_SUITE:t_orelse
=started       2017-01-17 11:14:50
=result        auto_skipped: init_per_suite failed
=== *** Skipping test case #1 {andor_SUITE,t_orelse} ***
===
=case          andor_SUITE:end_per_suite
=started       2017-01-17 11:14:50
=result        auto_skipped: init_per_suite failed
=== *** Skipping {andor_SUITE,end_per_suite} ***
=== TEST COMPLETE, 0 ok, 0 failed, 1 skipped of 1 test cases

=finished      2017-01-17 11:14:50
=failed        0
=successful    0
=user_skipped  0
=auto_skipped  1


3) erl -s ts install -s ts run all_tests -s init stop

# erl -s ts install -s ts run all_tests -s init stop
 Erlang/OTP 19 [erts-8.2] [source]

 {"init terminating in do_boot",{undef,[{ts,install,[],[]},{init,start_em,1,[]},{init,do_boot,3,[]}]}}
 init terminating in do_boot ()

 Crash dump is being written to: erl_crash.dump...done


=erl_crash_dump:0.3
Tue Jan 17 11:41:15 2017
Slogan: init terminating in do_boot ()
System version: Erlang/OTP 19 [erts-8.2] [source]
Compiled: Tue Jan 17 11:04:33 2017
Taints: erl_tracer
Atoms: 6506
Calling Thread: scheduler:1
=scheduler:1
Scheduler Sleep Info Aux Work:
Current Port:
Run Queue Max Length: 0
Run Queue High Length: 0
Run Queue Normal Length: 1
Run Queue Low Length: 0
Run Queue Port Length: 0
Run Queue Flags: NONEMPTY_NORMAL | OUT_OF_WORK | HALFTIME_OUT_OF_WORK | NONEMPTY | UNKNOWN(134217728)
Current Process: <0.0.0>
Current Process State: Running
Current Process Internal State: ACT_PRIO_NORMAL | USR_PRIO_NORMAL | PRQ_PRIO_NORMAL | ACTIVE | RUNNING | TRAP_EXIT | ON_HEAP_MSGQ
Current Process Program counter: 0x202993d4 (init:boot_loop/2 + 28)
Current Process CP: 0x00000000 (invalid)
Current Process Limited Stack Trace:
0x20429544:SReturn addr 0x20088FDC (<terminate process normally>)
...

15000 lines


Le 16/01/2017 à 22:25, Kostis Sagonas a écrit :
On 01/16/2017 05:12 PM, REIX, Tony wrote:

After building with Hipe, I've tried without Hipe.
And I got the same result: an infinite loop, in read() from
signal_dispatcher_thread_func().
  In: ERLC   ../ebin/hipe_rtl.beam              with Hipe (--enable-hipe)
  In: ERLC   ../ebin/hipe_consttab.beam   without Hipe (--disable-hipe)
. No idea why "hipe" appears here also.
So, for now, I have a common issue, with or without hipe.

I can provide some info regarding the behavior you are experiencing:

 - Certain modules of the 'hipe' application, though not all. are compiled independently of whether HiPE is enabled or not because they are used by 'dialyzer'.

 - It just so happens that 'hipe' is the first application that is compiled in the bootstrapping process, so the infinite loop you are getting is not related to HiPE but shows some deeper problem in the system you have built.

Bottomline: what you are experiencing is not HiPE-related.  Your system is broken.

Kostis



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20170117/396d06f2/attachment.htm>


More information about the erlang-questions mailing list