Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 13505
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Issue with multiple QRC runs

Suryansh Singh

Hello ,

I am trying to write a script to give multiple Quantus QRC runs.

So  I have done something like :

for file in <list_of_command_files>

   qrc -cmd file -log_file <file>.log &

Now the issue that I see is that QRC fails for some of the cases in the command file(which is also not very uniform, sometimes it does not even fail).

I see the following message in the qrc log :

[ERROR] Could not read temporary file: /tmp/<somefile>
ERROR (LBRCXM-609): Bad return status from RCX run. 0x200

INFO (LBRCXM-709): ***** Quantus terminated abnormally *****

I checked for the error code but this problem is not mentioned there.

I would also like to tell that I am using the option "-temporary_directory_name"  in my command files and its value is different for each run so I dont understand why is qrc using this /"tmp" directory. I also observed if I add bsub command for execution of qrc, qrc did not fail. 

Am I missing something over here ?

Regards

Suryansh Singh 

Parents
  • Andrew Beckett

    Hi Suryansh,

    You've not really given enough information. I do know there are some files that get written into /tmp regardless, but I'm not sure why it would fail (especially as the "<somefile>" bit is not very specific.

    Please contact customer support.

    Regards,

    Andrew.

  • Suryansh Singh
    in reply to Andrew Beckett

    Hello Andrew,

    Thanks for your response. I did not mention the files as it was some local netlist post-processing script. I figured out what was going wrong.

    The issue was that the Post-processing script created some files during its execution and later removed them. The file created had the same name across the multiple QRC runs and were created in /tmp directory. Now since the runs were all in parallel, they could use this file and the "faster" run would remove the file while the "slower" run was still using it.

    I could think of adding a time stamp to the names of these files as a solution. 

    Regards

    Suryansh Singh

Reply
  • Suryansh Singh
    in reply to Andrew Beckett

    Hello Andrew,

    Thanks for your response. I did not mention the files as it was some local netlist post-processing script. I figured out what was going wrong.

    The issue was that the Post-processing script created some files during its execution and later removed them. The file created had the same name across the multiple QRC runs and were created in /tmp directory. Now since the runs were all in parallel, they could use this file and the "faster" run would remove the file while the "slower" run was still using it.

    I could think of adding a time stamp to the names of these files as a solution. 

    Regards

    Suryansh Singh

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.