Repository navigation
Convert remaining UnitTest++ test files to GTest #566
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
Merged
highperformancecoder
merged 14 commits into
master
from
copilot/fix-1f30b62a-9f87-49f2-b020-afe651656e7e
Oct 4, 2025
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
74d07b0
Initial plan
Copilot 9717a18
Convert 6 simple test files to GTest
Copilot be96c98
Convert 4 more test files to GTest (testUserFunction, testVariablePan…
Copilot 3884b82
Convert testGrid, testXVector, and ticket-1461 to GTest
Copilot 0404f22
Convert testPubTab and testExpressionWalker to GTest
Copilot 6c8cff8
Convert testDerivative to GTest
Copilot 807605e
Convert testUnits to GTest
Copilot 68693e7
Convert testTensorOps, testModel, testMinsky to GTest and update Make…
Copilot 92e3f27
Fix syntax errors in CHECK_ARRAY conversions
Copilot 33e25b9
Fix regression failures.
highperformancecoder bc6043b
Fixed build errors. Still have failing unit tests.
highperformancecoder 88c10b5
All tests passing, except for TensorOpSuite.TensorVarValAssignment.
highperformancecoder e03e34f
Fix problematic unit test by moving it into a separate test suite.
highperformancecoder 47c71ca
Address code review comments.
highperformancecoder File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
Move macro undefs inside the header guard.
The
#undefdirectives forTrue,Bool, andNoneare placed after the closing#endifof the header guard (line 166). This means they will be processed every time this header is included, even on subsequent includes when the header guard prevents the main content from being processed. This could lead to unintended macro removal if these macros are defined by headers included after this one.Apply this diff to move the undefs inside the header guard:
Wait, let me reconsider. Looking at the line numbers again:
#endifThe undefs are currently AFTER the final
#endif. They should be BEFORE it. Let me provide the correct diff:🤖 Prompt for AI Agents
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.
That is what I want - these macros should never be defined in the first place!
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.
@highperformancecoder, thank you for the clarification! I understand now – you want these macros unconditionally undefined on every inclusion to prevent XLib macro pollution from interfering with gtest and other code. The placement after the header guard achieves exactly that. My apologies for the confusion!