Custom Query (3332 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (37 - 39 of 3332)

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Ticket Resolution Summary Owner Reporter
#1214 fixed Compiling issues with code changes in UKCA luke yl238
Description

I have been trying to add a free tracer with a fixed e-folding time in the UKCA section of the UM. I copied the relevant section of code from Luke Abraham's job ximqc into my job xiloh, the source code of which is fcm:um_br/dev/yl238/vn8.2_treetracer/src, revision 14533.

The files changed are ukca_main1-ukca_main1.F90, ukca_cspecies.F90 and ukca_constants.F90.

However, upon compilation I get the following error:

gmake: *** No rule to make target `ereport.done', needed by `ukca_main1.done'. Stop. gmake: *** Waiting for unfinished jobs.... gmake -f /projects/ukca/yuliu/um/xiloh/umatmos/Makefile -j 3 -s all failed (2) at /projects/um1/fcm/bin/../lib/Fcm/Build.pm line 611 Build failed on Tue Feb 11 13:47:33 2014. ->Make: 0 second ->TOTAL: 191 seconds UMATMOS build failed

But there are no errors otherwise in the compilation of the individual source codes. I commented out the section related to EREPORT in the newly added code in ukca_main1-ukca_main1.F90 (as can be seen in my source code) but the problem persists even after erasing the work directory. However, when this (the commented section) wasn't added yet (earlier in the day) the program compiled just fine.

I would be most grateful for any help.

Regards, Sue

#3086 answered suite failing at the "coupled" stage um_support yb19052
Description

I have a suite (u-bo840) that I am trying to run. But, the suite has failed at the "coupled" stage and got the following message in "job.err":

Rank 1014 [Sun Nov 24 03:50:19 2019] [c9-2c1s14n1] application called MPI_Abort(MPI_COMM_WORLD, 0) - process 1014 Application 88555350 is crashing. ATP analysis proceeding… atpAppSigHandler timed out waiting for shutdown. Re-raising signal. _pmiu_daemon(SIGCHLD): [NID 07225] [c9-2c1s14n1] [Sun Nov 24 03:55:21 2019] PE RANK 1014 exit signal Aborted [NID 07225] 2019-11-24 03:55:21 Apid 88555350: initiated application termination [FAIL] run_model # return-code=137 2019-11-24T03:55:24Z CRITICAL - failed/EXIT

Although I checked the "ocean.output" file, it does not show any error messages.

I also checked some output from "coupled"(~/cylc-run/u-bo840/work/18500101T0000Z/coupled), and there are several wrong netCDF (e.g. ……error.nc).

Do you know how I fix this issue?

Thanks Kenji

#3157 answered a LGM suite failing at the "coupled" stage um_support yb19052
Description

I have a suite (u-bp881) that I am trying to run for one year. The suite works okay for the first seven months (Jan-Jul), but it has failed in August. Thus, I check the ‘job.err’ at ‘~/cylc-run/u-bp881/log/job/18500701T0000Z/coupled/NN’ There are several WARNING, but it does not show any specific messages,

Application 95495696 is crashing. ATP analysis proceeding… Rank 1025 [Fri Jan 24 04:06:58 2020] [c0-1c1s14n2] application called MPI_Abort(MPI_COMM_WORLD, 0) - process 1025 atpAppSigHandler timed out waiting for shutdown. Re-raising signal. _pmiu_daemon(SIGCHLD): [NID 02810] [c0-1c1s14n2] [Fri Jan 24 04:12:00 2020] PE RANK 1025 exit signal Aborted [NID 02810] 2020-01-24 04:12:00 Apid 95495696: initiated application termination [FAIL] run_model # return-code=137 2020-01-24T04:12:20Z CRITICAL - failed/EXIT

Next, I checked the ‘ocean.output’ file at ‘~/cylc-run/u-bp881/work/18500701T0000Z/coupled’ , but the file also does not show any errors.

How do I fix the issue?

Thanks Kenji

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Note: See TracQuery for help on using queries.