-
Notifications
You must be signed in to change notification settings - Fork 11
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
Cleanup #52
Cleanup #52
Conversation
…isync into Cleanup # Conflicts: # doc/dataStructures/CuckooFilters.md
…isync into Cleanup # Conflicts: # doc/dataStructures/CuckooFilters.md
…g (i.e. avoid strtok)
…isync into Cleanup
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.
It looks good. Just a couple of questions.
@@ -50,7 +50,7 @@ void CommSocketTest::SocketSendAndReceiveTest() { | |||
//If socketSendReceiveTest() has finished successfully then kill child and break out of the loop | |||
if(result == 0) { | |||
CPPUNIT_FAIL("Sockets did not establish a connection in time"); | |||
kill(timer_pid, 0); | |||
// kill(timer_pid, 0); |
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.
We let the parent process to gracefully finish?
Can we delete this commented line?
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.
sure
@@ -57,5 +57,8 @@ void CuckooSyncTest::setReconcileTest() { | |||
// together because the execution trace picks up ZZ_p::init() call | |||
// before it reaches syncTest helper function. | |||
ZZ_p::init(randZZ()); | |||
CPPUNIT_ASSERT(syncTest(client, server, false, false, false, false, false)); | |||
|
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.
OK. I will look through it more thoroughly.
Just wondering, did this happen to you after I fixed Cuckoo::prng
?
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.
don't know ... but I don't think so
On May 28, 2020, at 5:56 PM, 5/28/20, Novak Boškov ***@***.***> wrote:
@novakboskov requested changes on this pull request.
It looks good. Just a couple of questions.
In tests/unit/CommSocketTest.cpp <#52 (comment)>:
> @@ -50,7 +50,7 @@ void CommSocketTest::SocketSendAndReceiveTest() {
//If socketSendReceiveTest() has finished successfully then kill child and break out of the loop
if(result == 0) {
CPPUNIT_FAIL("Sockets did not establish a connection in time");
- kill(timer_pid, 0);
+ // kill(timer_pid, 0);
We let the parent process to gracefully finish?
Can we delete this commented line?
I think that it's dead code right now, so I don't see why not delete it.
In tests/unit/CuckooSyncTest.cpp <#52 (comment)>:
> @@ -57,5 +57,8 @@ void CuckooSyncTest::setReconcileTest() {
// together because the execution trace picks up ZZ_p::init() call
// before it reaches syncTest helper function.
ZZ_p::init(randZZ());
- CPPUNIT_ASSERT(syncTest(client, server, false, false, false, false, false));
+
OK. I will look through it more thoroughly.
Just wondering, did this happen to you after I fixed Cuckoo::prng?
I think it was independent ...
… —
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#52 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACM5LU5UZISSMV3AH7M75PLRT3M2FANCNFSM4NGK3MWQ>.
---
Ari Trachtenberg, Boston University
http://people.bu.edu/trachten mailto:trachten@bu.edu
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Random quote of the day:
"A pious Jew is not one who worries about his fellow man's soul and his own stomach, but one who worries about his own soul and his fellow man's stomach." - Rabbi Israel Salanter
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
Some cleanup of code style and efficiency ... more to come later.