-
Notifications
You must be signed in to change notification settings - Fork 372
fix(spec-tests): Fix new fork tool test to use last fork dynamically #1741
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: forks/osaka
Are you sure you want to change the base?
fix(spec-tests): Fix new fork tool test to use last fork dynamically #1741
Conversation
|
Are we perhaps missing a label for |
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.
Might be worth having a test_end_to_end_latest and keeping test_end_to_end as is. That way we can tell if the new fork tool breaks for old forks.
a870452 to
e4bb577
Compare
|
@SamWilsn I split these to have both a hard-coded Osaka and the latest fork. I didn't see a strong reason to change the parameters for these but let me know if you think we should. |
|
Just sanity checked this by cherry-picking these commits over in Amsterdam bals branch and they pass 👌🏼 |
🗒️ Description
When we have two
Unscheduledforks, which will be more frequent moving forward, while Osaka isUnscheduledand Amsterdam is too, we cannot resolve the fork criteria for the e2e test for the fork tool (e.g. here).builder.pyif the fork isUnscheduledas well as if it'sforks[-1]and raise theorder_indexto come after it as we already do.I'm not tied to the last change. If we want to make hard-coding Osaka work, we can change some other things around as well but this change does get this test passing on Amsterdam as it uses
Amsterdamas the last fork.✅ Checklist
toxchecks to avoid unnecessary CI fails, see also Code Standards and Enabling Pre-commit Checks:uvx tox -e statictype(scope):.Cute Animal Picture