-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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.
This has been generally frowned upon previously. Personally I actually don't mind it (better take the hit of random bugs up front than defer to the day it becomes inevitable) but let's hear from @niklasad1 and @ordian.
You executed
I agree. |
test failure on macOS is legit, seems like the test
needs to be updated I don't mind the update in general, what I don't like though, is that it mixes insubstantial updates with changes like librocksdb-sys 6.2.4 -> 6.6.4, which can have a huge impact. |
c4eda8d
to
805f418
Compare
So, we are only running the tests on macOS? This should fix it:
|
No, github actions automatically cancels other jobs in case of a failure. |
f5da49a
to
5b60f61
Compare
@@ -1105,9 +1061,12 @@ dependencies = [ | |||
|
|||
[[package]] | |||
name = "error-chain" |
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.
hrm, I thought we got rid of error-chain
completely. Seems to be related to ethabi
though (bumping to v11 should fix it I guess)
Ran into Cargo.lock conflicts while working on #11540, figured that instead of untangling it, might just update everything.