Opened 10 months ago

Closed 9 months ago

#2299 closed help (answered)

Compiler clashes

Reported by: simon.tett Owned by: ros
Priority: high Component: UM Model
Keywords: Cc:
Platform: UM Version: 8.5

Description

Hi,

I am getting the following error message when I try I compile some code.


* stett2 Job: 4863073.sdb started: 20/10/17 16:37:01 host: esPP001 *
* stett2 Job: 4863073.sdb started: 20/10/17 16:37:01 host: esPP001 *
* stett2 Job: 4863073.sdb started: 20/10/17 16:37:01 host: esPP001 *
* stett2 Job: 4863073.sdb started: 20/10/17 16:37:01 host: esPP001 *


/home/n02/n02/stett2/.profile[297]: .[681]: .[1059]: .: line 1254: PROMPT_COMMAND: is read only
/home/n02/n02/stett2/.profile[1294]: .[1664]: .: line 1859: PROMPT_COMMAND: is read only
Cray PrgEnv? already loaded
cce/8.3.7
craype-network-aries
cray-libsci/13.0.1
PrgEnv?-cray/5.2.82
craype-ivybridge
cray-mpich/7.1.1
cray-mpich/7.5.5(34):ERROR:150: Module 'cray-mpich/7.5.5' conflicts with the currently loaded module(s) 'cray-mpich/7.1.1'
cray-mpich/7.5.5(34):ERROR:102: Tcl command execution failed: conflict cray-mpich

/home/n02/n02/stett2/umui_runs/xnsta-293163154/umuisubmit_compile[38]: .[384]: .[370]: .: line 76: HISTSIZE: is read only
cray-mpich/7.5.5(34):ERROR:150: Module 'cray-mpich/7.5.5' conflicts with the currently loaded module(s) 'cray-mpich/7.1.1'
cray-mpich/7.5.5(34):ERROR:102: Tcl command execution failed: conflict cray-mpich

/home/n02/n02/stett2/umui_runs/xnsta-293163154/umuisubmit_compile[39]: .[370]: .: line 72: PROMPT_COMMAND: is read only
Cray PrgEnv? already loaded
cce/8.3.7
craype-network-aries
cray-libsci/13.0.1
PrgEnv?-cray/5.2.82
craype-ivybridge
cray-mpich/7.1.1
Currently Loaded Modulefiles:

1) modules/3.2.10.6
2) eswrap/1.3.3-1.020200.1278.0
3) switch/1.0-1.0502.60522.1.61.ari
4) cce/8.3.7
5) craype-network-aries
6) craype/2.5.10
7) cray-libsci/13.0.1
8) udreg/2.3.2-1.0502.10518.2.17.ari
9) ugni/6.0-1.0502.10863.8.29.ari

10) pmi/5.0.12
11) dmapp/7.0.1-1.0502.11080.8.76.ari
12) gni-headers/4.0-1.0502.10859.7.8.ari
13) xpmem/0.1-2.0502.64982.5.3.ari
14) dvs/2.5_0.9.0-1.0502.2188.1.116.ari
15) alps/5.2.4-2.0502.9774.31.11.ari
16) rca/1.0.0-2.0502.60530.1.62.ari
17) atp/2.1.0
18) PrgEnv?-cray/5.2.82
19) pbs/12.2.401.141761
20) craype-ivybridge
21) cray-mpich/7.1.1
22) packages-archer
23) bolt/0.6
24) nano/2.2.6
25) leave_time/1.3.0
26) quickstart/1.0
27) ack/2.14
28) epcc-tools/6.0
29) xalt/0.6.0
30) iobuf/2.0.8
31) craype-hugepages64M
32) cray-netcdf/4.3.2

cray-mpich/7.5.5(34):ERROR:150: Module 'cray-mpich/7.5.5' conflicts with the currently loaded module(s) 'cray-mpich/7.1.1'
cray-mpich/7.5.5(34):ERROR:102: Tcl command execution failed: conflict cray-mpich

FCM 2016.12.0 (/fs2/y07/y07/umshared/software/fcm-2016.12.0)
COMP_UMSCRIPTS is true - run build command
cray-mpich/7.5.5(34):ERROR:150: Module 'cray-mpich/7.5.5' conflicts with the currently loaded module(s) 'cray-mpich/7.1.1'
cray-mpich/7.5.5(34):ERROR:102: Tcl command execution failed: conflict cray-mpich


Resources requested: ncpus=1,place=free,walltime=04:00:00
Resources allocated: cpupercent=0,cput=00:00:02,mem=23404kb,ncpus=1,vmem=146092kb,walltime=00:00:03

* stett2 Job: 4863073.sdb ended: 20/10/17 16:37:05 queue: serial *
* stett2 Job: 4863073.sdb ended: 20/10/17 16:37:05 queue: serial *
* stett2 Job: 4863073.sdb ended: 20/10/17 16:37:05 queue: serial *
* stett2 Job: 4863073.sdb ended: 20/10/17 16:37:05 queue: serial *


Change History (5)

comment:1 Changed 10 months ago by ros

  • Owner changed from um_support to ros
  • Status changed from new to accepted

Hi Simon,

We get the module load conflict error as well in most our jobs, but it doesn't stop the compile continuing. I'll take a look.

Regards,
Ros.

comment:2 Changed 10 months ago by ros

Hi Simon,

Please try submitting the job to compile again. I've just taken a copy of your job xnsta and it has compiled OK (with those module load errors) and run the reconfiguration and model successfully.

Cheers,
Ros.

comment:3 Changed 10 months ago by simon.tett

Hi Ros,

thanks — that compiled but it no longer bit-compares with old code.. Has there been a compiler change since last August?

Simon

comment:4 Changed 10 months ago by simon.tett

Ignore the bit comparison remark. I was looking at the wrong reference job..
Simon

comment:5 Changed 9 months ago by ros

  • Resolution set to answered
  • Status changed from accepted to closed
Note: See TracTickets for help on using tickets.