-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
disable the MacOS tests in jenkins #5119
Conversation
They've never really been enabled but they: 1. Are causing the tests to fail for various reasons (e.g., out of space). 2. Take time. License: MIT Signed-off-by: Steven Allen <[email protected]>
cc @victorbjelkholm ? |
try { | ||
run "make -j12 test/sharness/test-results/sharness.xml CONTINUE_ON_S_FAILURE=1 TEST_NO_FUSE=1" | ||
} catch (err) { | ||
throw err |
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.
Seems just commenting this and line 167 would give the wanted effect, rather than commenting the entire thing. But since @magik6k initially developed it, I'll leave it up to him to decide.
Although, removing the builds fully feels wrong, as we want to make sure it at least runs somewhat on macOS
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.
It's better to comment out the whole blocks imo
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.
Makes sense for now, LGTM.
Will conflict a bit with #5071 but it's easy fix. (well, other than the fact that we then got some data about failing mac tests) |
They've never really been enabled but they: