-
Notifications
You must be signed in to change notification settings - Fork 220
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
Mark LoggingSpec pending on macOS to alleviate timeouts #2709
Conversation
c795177
to
5e271a5
Compare
bors try |
tryBuild succeeded: |
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 originally thought we should remove the entire spec as you have done, but then @piotr-iohk reminded me that there are some useful tests such as those checking that sensitive data is not logged.
If it's a problem only on macOS but not at all on Linux, then that's a possible concern, and we should investigate a little bit.
Otherwise, how about adding a pendingOnMacOS
function to Test.Utils
? And/or removing the worst-offending tests, if there are such tests?
fc2c57a
to
d2e8268
Compare
d2e8268
to
b5a55db
Compare
This might help reduce the unit test timeouts on macOS hydra builds. Investigating #2472 Jonathan found the following tests to fail with limited ulimit -v: 36% Match String: "Checkpoint" 44% Match String: "correct time measures" 100% Match String: "different request ids" 20% Match String: "Private Key" 32% Match String: "Tx History" 28% Match String: "Wallet Metadata" where entries 2 and 3 are from LogginsSpec. The timeouts in CI were in these following locations: 12 times (28%) 000000 // from "Not Allowed Methods" 9 times (21%) Checkpoint 8 times (19%) rollback 5 times (12%) 8601 // from e.g. "ISO 8601 extended format without timezones" 4 times (9%) JSON 4 times (9%) MVar 4 times (9%) readStakeDistribution // only in the past, so now fixed 1 times (2%) Coverage which either suggest there are an 10+ lines of output not shown in the output, or the LoggingSpec isn't to blame. So it would be very interesting to see whether this commit reduces timeouts or not.
b5a55db
to
127d785
Compare
bors try |
Done.
I think @jonathanknowles's investigation would suggest the properties are the worst-offending tests, but this is not at all clear from the CI logs. I marked the whole of LoggingSpec pending on macOS to be sure. (If we see that this reduces timeouts, we could try un-mark some of them later.) |
bors r+ |
2709: Mark LoggingSpec pending on macOS to alleviate timeouts r=Anviking a=Anviking # Issue Number <!-- Put here a reference to the issue that this PR relates to and which requirements it tackles. Jira issues of the form ADP- will be auto-linked. --> ADP-970 # Overview <!-- Detail in a few bullet points the work accomplished in this PR --> - [x] Mark LoggingSpec pending on macOS Co-authored-by: Johannes Lund <[email protected]>
https://hydra.iohk.io/build/6660598
|
Build failed:
#2472 (macOS) |
tryBuild failed: |
bors r+ |
2709: Mark LoggingSpec pending on macOS to alleviate timeouts r=Anviking a=Anviking # Issue Number <!-- Put here a reference to the issue that this PR relates to and which requirements it tackles. Jira issues of the form ADP- will be auto-linked. --> ADP-970 # Overview <!-- Detail in a few bullet points the work accomplished in this PR --> - [x] Mark LoggingSpec pending on macOS Co-authored-by: Johannes Lund <[email protected]>
Build failed:
|
bors r+ |
2709: Mark LoggingSpec pending on macOS to alleviate timeouts r=Anviking a=Anviking # Issue Number <!-- Put here a reference to the issue that this PR relates to and which requirements it tackles. Jira issues of the form ADP- will be auto-linked. --> ADP-970 # Overview <!-- Detail in a few bullet points the work accomplished in this PR --> - [x] Mark LoggingSpec pending on macOS Co-authored-by: Johannes Lund <[email protected]>
Build failed:
|
bors r+ |
Build succeeded: |
Issue Number
ADP-970
Overview