-
Notifications
You must be signed in to change notification settings - Fork 11
Add Earlgrey OpenTitan regression flow #163
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
Conversation
36e5b04
to
efd0fd4
Compare
@loiclefort and @rivos-eblot: This is Earlgrey only at the moment, but we can do the same with Darjeeling once we get proper support in the OpenTitan repo. Let me know what you think of this approach. I don't want to slow down your Darjeeling QEMU work with Earlgrey problems. It runs against the |
This approach seems ok to me and a great move toward a real CI, thanks. |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some suggestions
9b914b1
to
b73a43b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @jwnrt, this looks all good from my side! (apart from the CI failure from the unsorted tests)
b73a43b
to
da28311
Compare
Signed-off-by: James Wainwright <james.wainwright@lowrisc.org>
Signed-off-by: James Wainwright <james.wainwright@lowrisc.org>
da28311
to
e26c9fc
Compare
Adds a CI workflow which runs a pull request's QEMU against the latest OpenTitan
earlgrey_1.0.0
tests. This takes ~30 minutes at the moment.There is a list of tests in the script which it compares against. The workflow fails if:
It runs on pull requests or can be manually run on any OpenTitan branch from the Actions tab.