-
Notifications
You must be signed in to change notification settings - Fork 182
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
Run some checks on windows #2730
base: master
Are you sure you want to change the base?
Conversation
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.
Should we also update the scheduled workflow? Perhaps it's worth considering running tests on Windows only there instead of on every CI.
"No such file or directory [..]" | ||
"[..] file [..]" |
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.
Could we make this failure message dependent on platform (applies to other places)?
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.
Actually, I'd do the opposite. We should wrap these errors so we don't output OS errors directly to the user. And specifically, we shouldn't assert specific os errors in tests.
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.
But until we do so, maybe I can assert the os specific error here
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.
Changed all of them to be OS dependent except for one assert that asserted the path scripts/
.
crates/forge/tests/e2e/running.rs
Outdated
#[should_panic(expected: "No such file or directory (os error 2)")] | ||
#[should_panic(expected: "file")] |
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.
Same as above
.github/workflows/ci.yml
Outdated
env: | ||
DEVNET_TAG: "v0.2.2" | ||
|
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.
We should use commit hash because it is immutable, unlike a tag which is mutable therefore could theoretically pose some risk.
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 still needs to be changed 😅
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.
Updated here as well
.github/workflows/ci.yml
Outdated
env: | ||
DEVNET_TAG: "v0.2.2" | ||
|
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 still needs to be changed 😅
scripts/install_devnet.ps1
Outdated
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.
Do we really need all these comments?
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.
Removed
Co-authored-by: Franciszek Job <[email protected]>
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 still think it would be better to test Windows only in the scheduled workflow. Testing it with every single change isn’t crucial and overall it will slow down our CI and make it harder to maintain.
Can we create an issue to investigate whether the cache action functions correctly, considering that the first CI run on a branch takes significantly longer than subsequent runs, and on Windows it is much longer than on Linux? Example: |
@ddoktorski I'd just merge this and we'll see if te build times are problematic. And if so, we can disable these checks at any time. |
# Conflicts: # CHANGELOG.md # Cargo.toml
#[cfg(not(target_os = "windows"))] | ||
mod fork_warning; | ||
#[cfg(not(target_os = "windows"))] |
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.
Is there any issue that addresses the removal of these?
Closes #2716
Introduced changes
Checklist
CHANGELOG.md