WHIZARD

Error in make check, installations in a HPC

Asked by Mohamed ouchemhou

Hello Dear all,
I am trying to install Whizard 3.1.4 on a server, but unfortunately, I encountered an error when running make check.

<./gmllongtest.1>]
make[5]: *** [Makefile:964: test-suite.log] Error 1
make[4]: *** [Makefile:1072: check-TESTS] Error 2
make[3]: *** [Makefile:2152: check-am] Error 2
make[2]: *** [Makefile:2154: check] Error 2
make[1]: *** [Makefile:663: check-recursive] Error 1
make: *** [Makefile:784: check-recursive] Error 1

PASS: api_c.run
PASS: api_cc.run
PASS: phs_wood_vis.run
PASS: prc_omega_diags.run
FAIL: integrations_history.run
SKIP: prc_recola.run
============================================================================
Testsuite summary for WHIZARD 3.1.4
============================================================================
# TOTAL: 145
# PASS: 130
# SKIP: 14
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
============================================================================
See tests/unit_tests/test-suite.log
============================================================================

Any help please?
Best Regards, MO

Question information

Language:
English Edit question
Status:
Solved
For:
WHIZARD Edit question
Assignee:
Juergen Reuter Edit question
Solved by:
Mohamed ouchemhou
Solved:
Last query:
Last reply:
Revision history for this message
Juergen Reuter (j.r.reuter) said : 		#1

Hi Mo,
this unit test just tests whether a LaTeX output of the integration history of the Monte Carlo integration is working or not. Normally the configure checks whether all ingredients are functional or not, but here it seemed to have failed. You should see in your integrations_history_1.r1.history.log file what went wrong. It could be that MetaPost is missing, or something related to your LaTeX installation (conTeXt is needed for this). But this is not really relevant for running Whizard.
Cheers,
    JRR (Juergen)

Revision history for this message
Mohamed ouchemhou (mouchemhou) said : 		#2

Dear JR,

Thank you for your response.

That was exactly the issue, and the problem is now resolved.

Best regards,
MO