Activity

I found the issue. The problem was that the reset was undefined right at the start which was causing some issues.

Hello Mikkie, sorry for not seeing your question.

To merge results:
vcover merge merged.ucdb run1.ucdb run2.ucdb run3.ucdb

Then the normal “report” to view the combined report:
vcover report merged.ucdb

Note, the VHDL has to be identical otherwise you’re trying to merge results that are not aligned, I think Questa gives an error.

OK, I just checked, this seems to be a regression in XSIM. It works in 2024.2.2 as well as 2025.1.

Using a test reporter is the intended method to get this information in CI

Hi Jim,

Thanks for the information!

I’ve actually switched to using the built-in JUnit GitHub Action for test reporting. In this setup, I simply specify the location of the XML report files, and the action handles the rest.

Here is the current method I’m using:


# Setup OSVVM and launch simulation
- name: Run Simulation
run: |
cd $GI…[Read more]

Hi Amine,
If you are still in Tcl, there are a number of variables you can check with the build status. Currently these are not documented, but they should be. Lets start here:

* ::osvvm::ReportBuildName – Name of Build
* ::osvvm::BuildStatus – PASSED / FAILED
* ::osvvm::TestCasesPassed
* ::osvvm::TestCasesFailed
*…[Read more]

There is also pyEDAA.OSVVM for reading OSVVM’s YAML files (or XML files). You get a data model where you can access fields and aggregated files as well as status properties.

See https://github.com/edaa-org/pyEDAA.OSVVM

Hi Amine,
CI will be running modelsim from the bash command line. And you can use:
vsim -c -do "exit -code [catch {source $OsvvmLibraries/Scripts/StartUp.tcl ; LinkLibraryDirectory ; build RunTest.pro}]

The “exit -code” is required to get the return status. What I return error on depends on what reporter I am using.

If I am using a JUnit…[Read more]