Reply To: Is there a built-in way in OSVVM to detect build failure without parsing logs?
Why OSVVM™? › Forums › OSVVM › Is there a built-in way in OSVVM to detect build failure without parsing logs? › Reply To: Is there a built-in way in OSVVM to detect build failure without parsing logs?
Jim LewisHi 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 reporter, if the build finished (independent of test case errors), I want the test case reporter to run, hence, I only stop if there was a build failure (and test JUnit report is either potentially corrupted or does not exist). You need this report to determine which test cases passed worked and which did not.
If instead your CI run displays the OSVVM build summary report (html), then when the build finishes, it has already run, and you can report any failure, including test case failures, as a failed build. Note this test case reporter is specific to OSVVM output and will detect things like the VHDL *.pro test case name – TestName Fred does not match the VHDL test case name – SetTestName( "Fred") ; – which indicates the wrong test architecture ran. This can happen if you are using multiple test architectures of TestCtrl and not using configurations.
Best Regards,
Jim