Open dlambrig opened 6 hours ago
LGTM. Note that currently the two rangeLocking simulation test (tests/fast/RangeLockCycle.toml and tests/fast/RangeLocking.toml) disable PROXY_USE_RESOLVER_PRIVATE_MUTATIONS in the toml file. We can re-enable the feature in the two tests once the PR of removing duplicated functions in Resolver.actor.cpp has been merged.
N/A
N/A
N/A
N/A
N/A
N/A
Error while executing command: if python3 -m joshua.joshua list --stopped | grep ${ENSEMBLE_ID} | grep -q 'pass=10[0-9][0-9][0-9]'; then echo PASS; else echo FAIL && exit 1; fi. Reason: exit status 1
LGTM. Note that currently the two rangeLocking simulation test (tests/fast/RangeLockCycle.toml and tests/fast/RangeLocking.toml) disable PROXY_USE_RESOLVER_PRIVATE_MUTATIONS in the toml file. We can re-enable the feature in the two tests once the PR of removing duplicated functions in Resolver.actor.cpp has been merged.
There are only two functions and one data structure to deduplicate. Conceptually I do not think there is a good reason why your change would not work on the resolver, but if there is a problem I'll see if it can be fixed.
Joshua ran clean when I enabled both knobs after modifying the toml files. I'll test a bit more to be sure.
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Do not check for PROXY_USE_RESOLVER_PRIVATE_MUTATIONS in rangeLockEnabled
Joshua with
PROXY_USE_RESOLVER_PRIVATE_MUTATIONS
enabled andENABLE_READ_LOCK_ON_RANGE
disabled:20241104-211756-dlambrig-a5cb3b9fac7ed2ca
with
ENABLE_READ_LOCK_ON_RANGE
andPROXY_USE_RESOLVER_PRIVATE_MUTATIONS
enabled:20241104-231600-dlambrig-bfad63339bc07b5e
Code-Reviewer Section
The general pull request guidelines can be found here.
Please check each of the following things and check all boxes before accepting a PR.
For Release-Branches
If this PR is made against a release-branch, please also check the following:
release-branch
ormain
if this is the youngest branch)