-
Notifications
You must be signed in to change notification settings - Fork 19
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
Enable assertions in race builds #27
Conversation
LGTM |
We need to revert 0cc8a3d first, right? |
LGTM |
The parent of this commit is 4.8, so we don't need to revert. We can point the glockfile to this commit (pre-merge) for assertions-enabled 4.8, and the merge of this commit for assertions-enabled 4.9. |
Neat. On Sep 8, 2016 00:44, "Ben Darnell" notifications@github.com wrote:
|
In the transition to the new Make-based build system for C dependencies (4d72e12), RocksDB assertions were inadvertently enabled for all builds. Restore the old behavior, which only enabled assertions for race builds (cockroachdb/c-rocksdb#27). Fixes cockroachdb#15604.
In the transition to the new Make-based build system for C dependencies (4d72e12), RocksDB assertions were inadvertently enabled for all builds. Restore the old behavior, which only enabled assertions for race builds (cockroachdb/c-rocksdb#27). Fixes cockroachdb#15604.
In the transition to the new Make-based build system for C dependencies (4d72e12), RocksDB assertions were inadvertently enabled for all builds. Restore the old behavior, which only enabled assertions for race builds (cockroachdb/c-rocksdb#27). Fixes #15604.
See cockroachdb/cockroach#9168
@cockroachdb/stability