Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 14915
  • 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

env variable reEvaluationWhenActiveAndHistroyTestsDiffer

venkmanbuster

Hi,

I am trying to evaluate an history in maestro on virtuoso and I get the following error because I deleted one of the old tests.

"These tests have been either renamed,removed or disabled.

Set the value of the 'reEvaluationWhenActiveAndHistoryTestsDiffer' env variable to 'removeDeletedTestsFromHistory' or 'persistDeletedTestsInHistory', as required, and re-evaluate the results.

Can you tell me the syntax? I tried something, doesn't work. 

Parents
  • Andrew Beckett

    A search in the documentation (e.g. via the help menu in Virtuoso) for reEvaluationWhenActiveAndHistoryTestsDiffer would have found you this:

    reEvaluationWhenActiveAndHistoryTestsDiffer

    Specifies the action to be taken when the tests that exist in the history for which you are re-evaluating the results are not found in the active ADE XL setup.

    In .cdsenv:

    		 

    adexl.gui reEvaluationWhenActiveAndHistoryTestsDiffer cyclic "Disallow"

    In .cdsinit or the CIW:

    		 

    envSetVal( "adexl.gui" "reEvaluationWhenActiveAndHistoryTestsDiffer" 'cyclic "Disallow" )

    Valid Values:

    		 

    "Disallow"

    If the tests in the active ADE XL setup and the history setup do not match, the results are not re-evaluated for the history.

    		 

    "removeDeletedTestsFromHistory"

    The results are re-evaluated for the history. The results for the tests not found in the active ADE XL setup are removed from the results database for the history. Only the new results are saved.

    		 

    "persistDeletedTestsInHistory"

    The results are re-evaluated for the history. If the tests in the history setup and the active ADE XL setup are same, new results are written back to the results database. If any test from the history setup is not found in the active setup, the previous results for those tests are retained in the results database for the history.

    Default Value:

    		 
    "Disallow"

    So simply change "Disallow" for the value you want, and it will work.

    Andrew

Reply
  • Andrew Beckett

    A search in the documentation (e.g. via the help menu in Virtuoso) for reEvaluationWhenActiveAndHistoryTestsDiffer would have found you this:

    reEvaluationWhenActiveAndHistoryTestsDiffer

    Specifies the action to be taken when the tests that exist in the history for which you are re-evaluating the results are not found in the active ADE XL setup.

    In .cdsenv:

    		 

    adexl.gui reEvaluationWhenActiveAndHistoryTestsDiffer cyclic "Disallow"

    In .cdsinit or the CIW:

    		 

    envSetVal( "adexl.gui" "reEvaluationWhenActiveAndHistoryTestsDiffer" 'cyclic "Disallow" )

    Valid Values:

    		 

    "Disallow"

    If the tests in the active ADE XL setup and the history setup do not match, the results are not re-evaluated for the history.

    		 

    "removeDeletedTestsFromHistory"

    The results are re-evaluated for the history. The results for the tests not found in the active ADE XL setup are removed from the results database for the history. Only the new results are saved.

    		 

    "persistDeletedTestsInHistory"

    The results are re-evaluated for the history. If the tests in the history setup and the active ADE XL setup are same, new results are written back to the results database. If any test from the history setup is not found in the active setup, the previous results for those tests are retained in the results database for the history.

    Default Value:

    		 
    "Disallow"

    So simply change "Disallow" for the value you want, and it will work.

    Andrew

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.