Opened 4 years ago

Closed 4 years ago

#1934 closed help (fixed)

Rose test job does not build on archer

Reported by: earhg Owned by: annette
Component: UM Model Keywords: example job fails to build
Cc: Platform: ARCHER
UM Version: 10.4

Description

hi
I copied job u-aa774 (which is UM10.5) following the instructions here http://cms.ncas.ac.uk/wiki/RoseCylc#IfyouarerunningonArcher
to job u-af399, and tried to run it on archer from PUMA with Rose. Out of the box, it failed to do fcm_make on archer because the hdf5 version 1.8.16 is not installed there(or it couldn't find it); I got a stderr from Rose that looks like:
[FAIL] cc -E -C -DC_LONG_INT=c_long_int -DC_LOW_U=c_low_u -DFRL8=frl8 -DLINUX=linux -DBUFRD_IO=bufrd_io -DCRAY_FORTRAN=8004001 -DGNU_LIBC=2011003 -DC84_1A=c84_1a -D
C95_2A=c95_2a -DC96_1C=c96_1c -DC97_3A=c97_3a -DC_DP_HLM=c_dp_hlm -DUM_JULES=um_jules -I./include /fs2/n02/n02/earhg/cylc-run/u-af392/share/fcm_make_um/extract/um/s
rc/control/c_code/c_address_routines.c # rc=1
[FAIL] pkg-config error:
[FAIL] Package 'netcdf' requires 'hdf5_hl ≥ 1.8.16' but version of hdf5_hl is 1.8.14
[FAIL] You may find new versions of hdf5_hl at http://crayport.cray.com/Pages/default.aspx
[FAIL] process 0.0 ! um/src/control/c_code/c_address_routines.c ← um/src/control/c_code/c_address_routines.c
[FAIL] cc -E -C -DC_LONG_INT=c_long_int -DC_LOW_U=c_low_u -DFRL8=frl8 -DLINUX=linux -DBUFRD_IO=bufrd_io -DCRAY_FORTRAN=8004001 -DGNU_LIBC=2011003 -DC84_1A=c84_1a -D
C95_2A=c95_2a -DC96_1C=c96_1c -DC97_3A=c97_3a -DC_DP_HLM=c_dp_hlm -DUM_JULES=um_jules -I./include /fs2/n02/n02/earhg/cylc-run/u-af392/share/fcm_make_um/extract/um/s
rc/control/c_code/c_affinity.c # rc=1
[FAIL] pkg-config error:
[FAIL] Package 'netcdf' requires 'hdf5_hl ≥ 1.8.16' but version of hdf5_hl is 1.8.14
[FAIL] You may find new versions of hdf5_hl at http://crayport.cray.com/Pages/default.aspx
[FAIL] process 0.0 ! um/src/control/c_code/c_affinity.c ← um/src/control/c_code/c_affinity.c
The full error trace is on archer at
/home/n02/n02/earhg/cylc-run/u-af399/log.20160804T103512Z/job/1/fcm_make2/01/job.err

I changed the netcdf and hdf5 versions set in suite.rc to netcdf 4.3.2 and hdf 1.8.14 in a copy of this, job u-af396, and this error went away and the job seemed to get further through the build, but it still failed to compile, with stderr that looks like:

[FAIL] ftn -oo/yearlen_mod.o -c -I./include -s default64 -e m -J ./include -I/work/y07/y07/umshared/gcom/cce8.4.1/gcom6.0/archer_xc30_cce_mpp/build/include -O2 -Ove
ctor1 -hfp0 -hflex_mp=strict -h omp /work/n02/n02/earhg/cylc-run/u-af396/share/fcm_make/preprocess-atmos/src/um/src/atmosphere/radiation_control/yearlen_mod.F90 # r
c=1
[FAIL] ifort: error #10236: File not found: 'default64'
[FAIL] ifort: command line warning #10157: ignoring option '-error_limit'; argument is of wrong type
[FAIL] ifort: error #10236: File not found: 'm'
[FAIL] ifort: command line warning #10006: ignoring unknown option '-J'
[FAIL] ifort: command line warning #10006: ignoring unknown option '-Ovector1'
[FAIL] compile 0.4 ! yearlen_mod.o ← um/src/atmosphere/radiation_control/yearlen_mod.F90

(and continues for many failed attempts to make .o files). The full build err is at /home/n02/n02/earhg/cylc-run/u-af396/log.20160804T091633Z/job/1/fcm_make2/01

Please can someone help me fix this? I have not made any changes to the job except to change the username and the budget code, and I *think* though I may be wrong that my environment is ok.
Thanks very much, Hamish

Change History (3)

comment:1 Changed 4 years ago by annette

Hi Hamish,

It looks like you are using the Intel compiler. Have you changed this in your ARCHER environment? We have set the UM up to use the Cray compiler on ARCHER so this won't work.

Annette

comment:2 Changed 4 years ago by annette

  • Owner changed from um_support to annette
  • Status changed from new to assigned

comment:3 Changed 4 years ago by earhg

  • Resolution set to fixed
  • Status changed from assigned to closed

Hi Annette,
Thank you very much for spotting this. When I did module list I did see the Intel compiler. Not sure where it came from, but when I swapped it to the cray compiler the build succeeded. Thanks very much, I closed the ticket.
Hamish

Note: See TracTickets for help on using tickets.