Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature request] sby writes its output to a main log file #79

Open
tudortimi opened this issue Apr 11, 2020 · 4 comments
Open

[feature request] sby writes its output to a main log file #79

tudortimi opened this issue Apr 11, 2020 · 4 comments

Comments

@tudortimi
Copy link

It would be helpful if sby would write its output to an sby.log file.

@tudortimi tudortimi changed the title sby doesn't write its output to a main log file [feature request] sby writes its output to a main log file Apr 11, 2020
@ZipCPU
Copy link
Contributor

ZipCPU commented Apr 15, 2020

SBY does create a log file every time you run it, several in fact. The primary log file is in the created task directory and named logfile.txt. There's also a log file in each engine_? directory for each proof that the solver runs for that given task. You'll also find a log file describing the processing of your design in the task directory /model/design*.log.

Dan

@tudortimi
Copy link
Author

But if I'm running multiple tasks, using sby <file> it would be useful to get an overview of all tasks that were run, etc. With a lot of tasks it can get pretty crowded.

@tudortimi
Copy link
Author

Plus, even for one task, it's easier to open one log file from a standard location, look at it, leave the editor open, run the next task, refresh the contents of the log file in the open editor, etc,

@ZipCPU
Copy link
Contributor

ZipCPU commented Apr 15, 2020

I typically use "make" to handle directories with multiple sby tasks in them. You can find an example Makefile here. make -n then gives me a beautiful view of what's not yet passed, and make -kj4 will run all outstanding proofs on 4 CPU cores. I also have a passcheck.sh that I use to see if anything has failed. I can then examine that to if anything has failed. There's also an sby-gui command you can use to get a GUI view of (mostly) the same thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants