-
Notifications
You must be signed in to change notification settings - Fork 1.4k
ci: missing patch workflow #3119
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
base: develop
Are you sure you want to change the base?
Conversation
@ruchamahabal review please! Will do for the older versions if this is approved. |
2bb28b8
to
0f8a268
Compare
wget https://erpnext.com/files/v13-erpnext.sql.gz | ||
bench --site test_site --force restore ~/frappe-bench/v13-erpnext.sql.gz |
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.
This isn't sufficient IMO. Both of the current patch test backups have some Frappe/ERPNext specific test data. They're woefully inadequate, but at least it's there. Empty tables will ignore a lot possible failure modes that can happen during schema migrations.
Maybe create a new v14 site with some dummy data and store it somewhere?
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.
I thought of that initially but then it leaves out sites updating from v13?
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.
v13 is EOL since ~1.5 years now. So IMO it's better to expand "coverage" of code that gets tested vs. coverage of tested versions.
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.
v14 it is!
This should catch migration failures before they end up in the release
to-do
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/