-
Notifications
You must be signed in to change notification settings - Fork 123
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
Refactor snapshot updating/checking scripts #172
Conversation
Should I create a mkconfig for current session variable storage? For example, when I changed to riscv, until next time I |
Feel free to consolidate! Check #44 |
2652237
to
53e2042
Compare
53e2042
to
8fc46c5
Compare
I would like to work on package prerequisites validation in another PR after the this one is merged. |
8fc46c5
to
b595e34
Compare
b595e34
to
1e02b7a
Compare
1e02b7a
to
7d9e2b2
Compare
7d9e2b2
to
a2cfa70
Compare
a2cfa70
to
ef7d273
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.
Rebase the latest master
branch.
- Adds .session.mk generation for consistent makefile execution behavior. - Refine document about snapshot test Co-authored-by: Meng-Hung Chen <[email protected]>
ef7d273
to
f2050f3
Compare
Thank @ChAoSUnItY for contributing! |
Previously in #171, I had encountered an snapshot checking issue, which is snapshot only contains arm32 backend but rv32. In order to resolve this, I have added few more rules to update/check snapshots:
make update-snapshots
/make check-snapshots
Updates/Checks all backends' snapshots.
make update-snapshot
/make check-snapshots
Updates/Checks current backend's snapshots.
Additionally I've separated arm and riscv backend CI into different matrix, to better observe which backend is running into failure.
Breaking changes for snapshots scripts
Now directly using snapshots scripts is unrecommended, instead, uses the above mentioned make rules to update/check snapshots.