lowRISC / lowRISC/ibex

[dv/formal]: With Yosys and rIC3 fails for python conductor.py prove.

Open
#2,373 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Type:Bug
Dominant language
SystemVerilog
Stars
2.1k
Forks
810
Avg merge
5d 23h
Merged PRs (30d)
9

Description

## Observed Behavior
I tried to re-run the dv/formal flow using the Opensource tools using the following instructions:
**Build instructions:**

- nix develop .#oss-dev
- make build/aig-manip builds the Rust aig-manip tool used by conductor.py
- make build/all.aig builds the core Aiger file
- python3 conductor.py prove

but the run crashed with Error code 127. I attached the log file also for the crash.

## Expected Behavior
In the link here https://semiiphub.com/industryexpertblogs/open-source-correctness-proof-for-ibex it was mentioned that dv/formal is part of the latest CI. Thus I was hoping it must pass.

## Steps to reproduce the issue
Commands I ran:
- git clone https://github.com/lowRISC/ibex.git
- cd dv/formal
- nix develop .#oss-dev
- make build/aig-manip builds the Rust aig-manip tool used by conductor.py
- make build/all.aig builds the core Aiger file
- python3 conductor.py

At pyhon3 conductor.py prove got lot of errors with Error code 127,

## My Environment

[log_file.txt](https://github.com/user-attachments/files/25871318/log_file.txt)

**Operating system:**
Distributor ID: Ubuntu
Description: Ubuntu 24.04.4 LTS
Release: 24.04

**Version of the Ibex source code:**
branch: master

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 in dv/formal/conductor.py and reproduce the failure with nix develop .#oss-dev, make build/aig-manip, make build/all.aig, and python3 conductor.py prove. Inspect the attached log for the command producing Error 127; done means the documented open-source formal flow completes successfully on the reported environment.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.