Skip to content

Issue 33#35

Merged
PkHutch merged 11 commits intodevelopmentfrom
issue-33
Jan 29, 2026
Merged

Issue 33#35
PkHutch merged 11 commits intodevelopmentfrom
issue-33

Conversation

@sudonym-i
Copy link
Collaborator

@sudonym-i sudonym-i commented Jan 23, 2026

REVIEW before merging

This branch has some experimental changes:

  • I added valgrind (memory leak detection) to the testing suite
  • changed the test output. The results are no longer in the same place. Rather than being in the log, they are now in a markdown artifact below everything.
  • Made some structural changes. The github actions scripting is now written in "automations.sh" rather than directly inside the .yml file.
  • Made 2 small changes to the the Makefile, adding valgrind build and changing one of the output file names.

closes #33

@sudonym-i
Copy link
Collaborator Author

Stressed the "review before merging" just to prevent any potential yolo merges.

Brought the readme up to date with my changes, adding new images and
instructions where appropriate.
@rileygramlich rileygramlich requested review from PkHutch and rileygramlich and removed request for rileygramlich January 27, 2026 19:32
There is further refactoring to be done that this point, namely
something like generate-coverage, test, and valgrind, all are very
similar commands.
Update from the makefile changed the output to geo_dash, this removes
it from being tracked.
The addition of the depenency does not include Valgrind in the
instructions, this updates the README.md to include it.
PkHutch
PkHutch previously approved these changes Jan 28, 2026
Copy link
Collaborator

@PkHutch PkHutch left a comment

Choose a reason for hiding this comment

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

https://github.com/RIPE-COMP2659/comp2659/pull/35/commits

I will let you take a look at these changes before we merge, importantly, I threw a low-priority issue here: #38

changes:
- added disclaimer to the readme that valgrind first and foremost ought
  to be run with the full game on local machines- not offloaded to
  automated starting

Sidenote: valgrind currently just runs on the testing executable for
now, to avoid timing out when we begin developing the game
@sudonym-i
Copy link
Collaborator Author

Note:

I'm not sure- but I think this may close issue 38.

@PkHutch may have to talk with @sudonym-i to see whether this is the case

@PkHutch
Copy link
Collaborator

PkHutch commented Jan 29, 2026

Note:

I'm not sure- but I think this may close issue 38.

@PkHutch may have to talk with @sudonym-i to see whether this is the case

I agree, closes #38 for the time being. We might want a Makefile refactor as we get further along, but it's inconsequential for the time being.

Copy link
Collaborator

@PkHutch PkHutch left a comment

Choose a reason for hiding this comment

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

LGTM via previous review

@PkHutch PkHutch merged commit 720ffd4 into development Jan 29, 2026
1 check passed
@PkHutch PkHutch deleted the issue-33 branch January 29, 2026 03:35
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.

Determine and implement memory leak checker

2 participants

Comments