Opened 3 years ago

Closed 3 years ago

#2222 closed help (worksforme)

libcif crayftn internal error

Reported by: markr Owned by: um_support
Component: UM Model Keywords: archer crayftn libcif
Cc: Platform: ARCHER
UM Version: 7.3


Hello CMS, (*Note this is a copy of 969 on*)

I am helping a PhD student (ee10hp) debug an issue but my copy of their case fails to build with the following message (3 occurrences):

in ~mricha/output/xnnkb000.xnnkb.d17191.t143436.comp.leave

LLVM ERROR: IO failure on output stream. ftn-2708 crayftn: INTERNAL

Converting message file; libcif returned error status: The file is not a CIF format file

fcm_internal compile failed (256)

and it looks like it applies to 3 files: grep "Error 1" xnnkb000.xnnkb.d17191.t143436.comp.leave

gmake: * [blkdata.o] Error 1

gmake: * [order.o] Error 1

gmake: * [duplic.o] Error 1

and looking at explain ftn-2708

Internal : Converting message file; libcif returned error status: %s

This message should never be generated. The compiler could not output the messages it has generated. Please notify your product support organization with this error message number and any supporting information. This message does not indicate a problem with your code.

Message ID: INTERNAL_1060

Change History (3)

comment:1 Changed 3 years ago by grenville

It just built OK for me — pl try again (maybe do a full build (and extract))

comment:2 Changed 3 years ago by markr

Hi Grenville,
I found a reference on tickets where the user said they cleaned up their /tmp or /work

I just spent 30 min doing that and now the case has run. Sorry to have had to raise a ticket but it looked extremely odd message. Is this really just a disk quota issue?

Now the case fails as expected durine runtime (entering UKCA) so I have something to debug.

Thank you for investigating.

comment:3 Changed 3 years ago by grenville

  • Resolution set to worksforme
  • Status changed from new to closed


I'd forward this to ARCHER if it hadn't worked for me - we see odd things like this occasionally, but they usually go away on retrying.


Note: See TracTickets for help on using tickets.