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

Multiple schemes tests #1300

Draft
wants to merge 16 commits into
base: main
Choose a base branch
from
Draft

Multiple schemes tests #1300

wants to merge 16 commits into from

Conversation

ole-alb
Copy link
Contributor

@ole-alb ole-alb commented Nov 13, 2024

Describe your changes here:

Created an iterator to test the Eclasses of multiple schemes. Returns the tree scheme (ts) instead of the eclass,

All these boxes must be checked by the reviewers before merging the pull request:

As a reviewer please read through all the code lines and make sure that the code is fully understood, bug free, well-documented and well-structured.

General

  • The reviewer executed the new code features at least once and checked the results manually

  • The code follows the t8code coding guidelines

  • New source/header files are properly added to the Makefiles

  • The code is well documented

  • All function declarations, structs/classes and their members have a proper doxygen documentation

  • All new algorithms and data structures are sufficiently optimal in terms of memory and runtime (If this should be merged, but there is still potential for optimization, create a new issue)

Tests

  • The code is covered in an existing or new test case using Google Test

Github action

  • The code compiles without warning in debugging and release mode, with and without MPI (this should be executed automatically in a github action)

  • All tests pass (in various configurations, this should be executed automatically in a github action)

    If the Pull request introduces code that is not covered by the github action (for example coupling with a new library):

    • Should this use case be added to the github action?
    • If not, does the specific use case compile and all tests pass (check manually)

Scripts and Wiki

  • If a new directory with source-files is added, it must be covered by the script/find_all_source_files.scp to check the indentation of these files.
  • If this PR introduces a new feature, it must be covered in an example/tutorial and a Wiki article.

License

  • The author added a BSD statement to doc/ (or already has one)

test/t8_gtest_macros.hxx Outdated Show resolved Hide resolved
test/t8_schemes/t8_gtest_iterator.cxx Outdated Show resolved Hide resolved
@Davknapp Davknapp self-requested a review November 26, 2024 14:31
@Davknapp Davknapp removed their request for review December 13, 2024 11:39
@Davknapp Davknapp added enhancement Enhances already existing code shouldn't take long Can be resolved in under 30 mins tests priority: high Should be solved as soon as possible workload: low Would take half a day or less tag: patch Merging this needs a new patch tag labels Dec 13, 2024
@ole-alb
Copy link
Contributor Author

ole-alb commented Dec 20, 2024

We faced problems when adding a new scheme to the all-schemes builder, as differences arise between the eclass counter and the number of eclass schemes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Enhances already existing code priority: high Should be solved as soon as possible shouldn't take long Can be resolved in under 30 mins tag: patch Merging this needs a new patch tag tests workload: low Would take half a day or less
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants