Expected Behavior

Invoking a mockk should never cause a test to hang. If too many invocations lead to performance issues, it would be better to either:

• throw an exception once a reasonable cap is reached
• rotate away old data

Current Behavior

After invoking a mock around 130 000 times (on my machine, running JDK 15 on Windows) further invocations will hit a wall and take for

This requires just some small improvements, the error itself being harmless, but annoying.

$ immuadmin-090 login immudb
ERROR 2021/01/28 09:46:25 Couldn't discover absolute path
ERROR 2021/01/28 09:46:25 getwd: no such file or directory
Password:
logged in
$

immuadmin-090 is just a sym link:

$ which immuadmin-090
/home/{user}/apps/bin/immuadmin-090
$
$ ls 

This is very low prio, but it usually happens that when touching Prims or some other file high in the dependency graph, we get spurious diffs in many other files. Since we check-in the snapshot, and we need to have it up-to-date, we get very verbose commits when nothing relevant changed. Plus, when something did change, it's hard to spot.

Example: I removed a few lines in prims and get things

Several users have asked for an example of how to use the makefiles in projects that contain precompiled and/or encrypted IP cores or libraries. There should be a simple example. It will likely not work for them, but could act as a template.

Alternatively, documentation or an explicit API for these objects would also help.

Future documentation for this feature:

To delete pacts for a specific tag.

• Open the Pact Broker and click "show latest tags"

• Scroll to the row for the consumer/tag that you wish to delete.

• Click on the "..." icon for that row

• Select "Delete pacts for tag <tag>"

• You will see a prompt with the text

  This will delete the pacts for provider <provider> and all ver
  

Here is the problem:

$ make compile
Traceback (most recent call last):
File "C:\My_Designs\probe_fpga_design_1\run.py", line 336, in
main()
File "C:\My_Designs\probe_fpga_design_1\run.py", line 181, in main
vu.add_osvvm()
File "c:\my_designs\probe_fpga_design_1\deps\vunit\vunit\ui_init_.py", line 1030, in add_osvvm
self.builtins.add("osvvm")
File "c:\my

It would be useful to add new programs to the prusti-tests/ test suite, with the goal of increasing code coverage as some branches of Prusti are currently never reached by the tests.

See also the dev guide.