Skip to content
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

HPCC-18936 Allow a timing unit test to be run individually #10762

Merged
merged 1 commit into from
Jan 15, 2018

Conversation

ghalliday
Copy link
Member

@ghalliday ghalliday commented Jan 5, 2018

Signed-off-by: Gavin Halliday gavin.halliday@lexisnexis.com

Type of change:

  • This change is a bug fix (non-breaking change which fixes an issue).
  • This change is a new feature (non-breaking change which adds functionality).
  • This change improves the code (refactor or other change that does not change the functionality)
  • This change fixes warnings (the fix does not alter the functionality or the generated code)
  • This change is a breaking change (fix or feature that will cause existing behavior to change).
  • This change alters the query API (existing queries will have to be recompiled)

Checklist:

  • My code follows the code style of this project.
    • My code does not create any new warnings from compiler, build system, or lint.
  • The commit message is properly formatted and free of typos.
    • The commit message title makes sense in a changelog, by itself.
    • The commit is signed.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly, or...
    • I have created a JIRA ticket to update the documentation.
    • Any new interfaces or exported functions are appropriately commented.
  • I have read the CONTRIBUTORS document.
  • The change has been fully tested:
    • I have added tests to cover my changes.
    • All new and existing tests passed.
    • I have checked that this change does not introduce memory leaks.
    • I have used Valgrind or similar tools to check for potential issues.
  • I have given due consideration to all of the following potential concerns:
    • Scalability
    • Performance
    • Security
    • Thread-safety
    • Premature optimization
    • Existing deployed queries will not be broken
    • This change fixes the problem, not just the symptom
    • The target branch of this pull request is appropriate for such a change.
  • There are no similar instances of the same problem that should be addressed
    • I have addressed them here
    • I have raised JIRA issues to address them separately
  • This is a user interface / front-end modification
    • I have tested my changes in multiple modern browsers
    • The component(s) render as expected

Testing:

@ghalliday
Copy link
Member Author

@richardkchapman please review

@AttilaVamos
Copy link
Contributor

@ghalliday
Copy link
Member Author

@richardkchapman I think the failure is unrelated. However it looks like it happened after the ifblock fix was merged, so may still be a problem.

@richardkchapman
Copy link
Member

I suspect it's a race condition - I think the ECL both creates and reads that file, and it may be that the codegen cannot spot the dependency. Should raise a Jira to fix it but as you say not related

@@ -8716,9 +8716,9 @@ static int compareTiming(const void * pLeft, const void * pRight)
}


class RoxieMemTimingTests2 : public CppUnit::TestFixture
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure I understand why this name change was made

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The name was changed because the filter for running a unit test matches using a substring. If the 2 is on the end of the test name it is impossible to only run the first test - since it will also run this test!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm. I would have gone for calling them tests1 and tests2 then...

@richardkchapman
Copy link
Member

@ghalliday One minor question

@ghalliday
Copy link
Member Author

@richardkchapman

@richardkchapman
Copy link
Member

@ghalliday

Signed-off-by: Gavin Halliday <gavin.halliday@lexisnexis.com>
@ghalliday
Copy link
Member Author

@richardkchapman repushed

@HPCCSmoketest
Copy link
Contributor

Automated Smoketest: ✅
Sha: d77a27b
Build: success
Install hpccsystems-platform-community_6.5.0-trunk0.el7.x86_64.rpm
HPCC Start: OK

Unit tests result:

Test total passed failed errors timeout
unittest 81 81 0 0 0
wutoolTest(Dali) 19 19 0 0 0
wutoolTest(Cassandra) 19 19 0 0 0

Regression test result:

phase total pass fail
setup (hthor) 11 11 0
setup (thor) 11 11 0
setup (roxie) 11 11 0
test (hthor) 737 737 0
test (thor) 648 648 0
test (roxie) 766 766 0

HPCC Stop: OK
HPCC Uninstall: OK
Time stats:

Prep time Build time Package time Install time Start time Test time Stop time Summary
36 sec (00:00:36) 166 sec (00:02:46) 59 sec (00:00:59) 8 sec (00:00:08) 54 sec (00:00:54) 1078 sec (00:17:58) 39 sec (00:00:39) 1440 sec (00:24:00)

@richardkchapman richardkchapman merged commit b43750d into hpcc-systems:master Jan 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants