lowRISC / lowRISC/opentitan

[dvsim,website] Results with different simulators get mixed on reports website

Open
#24,002 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component:Site Tool:dvsim
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

We currently run few chip-level tests with Xcelium and all other chip-level tests with VCS. The results from both runs get reported on our website under `https://reports.opentitan.org/hw/top_earlgrey/dv//report.html`. As Xcelium simulations finish much more quickly (because only a few tests are run), the earlier datetime on each day is for Xcelium while the later is for VCS; example: [Xcelium](https://reports.opentitan.org/hw/top_earlgrey/dv/2024.07.11_02.01.02/report.html), [VCS](https://reports.opentitan.org/hw/top_earlgrey/dv/2024.07.11_11.01.00/report.html).

For people who don't know this, the reports on the website can be confusing.

We should look into reporting chip-level regression results separately for VCS and Xcelium.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the Xcelium and VCS report URLs in the issue and trace how chip-level regression results are published to the reports website. Determine where simulator identity can be separated, then confirm that the website presents distinct VCS and Xcelium reports without mixing their results.

Written by the indexing model from the issue text.

Assessment

Domain
testing, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.