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.

Sign up for GitHub

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

Jump to bottom

max_key acting weird #4

Open

TulkasLaugh opened this issue Jun 14, 2016 · 0 comments

Member

TulkasLaugh commented Jun 14, 2016

In Run2 in the diagrams folder I input:

spawn_updates 300000000 1000000 10000000 30000000 4000 60000

but when it scans it keeps saying:

"Scanning for 2000 s in [0,100000000) -> 1000 keys/read"

when it should say

"Scanning for 2000 s in [0,300000000) -> 1000 keys/read"

I can't identify what's going wrong with max_key in jitd_tester.cpp to not print out the updated value correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment