Stats

  • Locked Locked
  • Replies 4
  • Subscribers 65
  • Views 15045
  • 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

Tracking regression results with an SQLITE database

andymont

Hi , 

I would like to keep track of the verification status of my project (verilog/systemverilog) coverage and pass/fail status of tests during the life of the project. Ideally I want to create an SQLITE database to keep track of this since SQLITE is stored in a file which can be archived with the project after tapeout.

I am already writing my own solution which involves parsing the output vsof from a regression and then storing the information I need, however this seems to me to be something which may already be possible and there does seem to be an option in the emanager configuration to use SQL but there is no information in any of the docs which explains its use.

Does anyone have any ideas ?

regards

Andy 

Parents

  • I sent Andy some example code, which I'm copying here in case it's of help to any other forum members.

    // Usage example:
// vmanager -batch -c "load dump_results_csv; analyze_runs -vsof my_session/my_session.vsof; dump_results_csv()"
<'
extend global {
  dump_results_csv ( result_file_name:string=NULL ) is {
    if result_file_name == NULL { result_file_name = "results.csv"; };

    // Get all loaded sessions (there can be more than one)
    var all_sessions := vm_manager.get_all_sessions();
    // Get an analysis "context"
    var ctx : vm_context = vm_manager.create_context(all_sessions.as_a(list of vm_attribute_container), "Default");
    // Get all the runs from that context
    var all_runs := ctx.get_runs();

    // Create the output file and header
    var result_file := files.open(result_file_name,"w","Text file");
    files.write(result_file,"Test, Seed, Status, First Failure");

    // Get a handle to the sv_seed attribute type
    var attr_seed  := vm_manager.get_attribute_by_name("sv_seed");
    // Get a handle to the test_name attribute type
    var attr_title := vm_manager.get_attribute_by_name("test_name");

    // Iterate through all the runs
    for each (run) in all_runs {
      var line :string;
      line = append(run.get_attribute_value_or_default(attr_title), ", ");
      line = append(line, run.get_attribute_value_or_default(attr_seed), ", ");
      line = append(line, run.get_status(), ", ");
      if (run.get_status_enum() == failed) {
        // var all_failures := run.get_failures(); // Alternative if you want all failures
        var first_failure := run.get_first_failure();
        line = append(line, first_failure.get_value("description"));
      } else {
        line = append(line, "n/a");
      };
      files.write(result_file,line);
    };
    files.close(result_file);
  };
}; 

    '> 

    dump_results_csv.e.html
Reply

  • I sent Andy some example code, which I'm copying here in case it's of help to any other forum members.

    // Usage example:
// vmanager -batch -c "load dump_results_csv; analyze_runs -vsof my_session/my_session.vsof; dump_results_csv()"
<'
extend global {
  dump_results_csv ( result_file_name:string=NULL ) is {
    if result_file_name == NULL { result_file_name = "results.csv"; };

    // Get all loaded sessions (there can be more than one)
    var all_sessions := vm_manager.get_all_sessions();
    // Get an analysis "context"
    var ctx : vm_context = vm_manager.create_context(all_sessions.as_a(list of vm_attribute_container), "Default");
    // Get all the runs from that context
    var all_runs := ctx.get_runs();

    // Create the output file and header
    var result_file := files.open(result_file_name,"w","Text file");
    files.write(result_file,"Test, Seed, Status, First Failure");

    // Get a handle to the sv_seed attribute type
    var attr_seed  := vm_manager.get_attribute_by_name("sv_seed");
    // Get a handle to the test_name attribute type
    var attr_title := vm_manager.get_attribute_by_name("test_name");

    // Iterate through all the runs
    for each (run) in all_runs {
      var line :string;
      line = append(run.get_attribute_value_or_default(attr_title), ", ");
      line = append(line, run.get_attribute_value_or_default(attr_seed), ", ");
      line = append(line, run.get_status(), ", ");
      if (run.get_status_enum() == failed) {
        // var all_failures := run.get_failures(); // Alternative if you want all failures
        var first_failure := run.get_first_failure();
        line = append(line, first_failure.get_value("description"));
      } else {
        line = append(line, "n/a");
      };
      files.write(result_file,line);
    };
    files.close(result_file);
  };
}; 

    '> 

    dump_results_csv.e.html
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.