Integration Tests for the SOM language #128

rhys-h-walker · 2025-07-09T09:36:11Z

This pull request adds integration tests to the SOM standard library. These integration tests require two python libraries to be installed Pytest and PyYaml.

Integration tests are based on the lang_tests of yksom.

Tests can be configured through using environment variables:
EXECUTABLE= Location of the SOM executable
CLASSPATH= Classpath required for running
TEST_EXCEPTIONS= Exceptions yaml file for tests not expected to pass
DEBUG= Boolean for detailed run information on the go
GENERATE_REPORT= File location for a report to be generated at the end of the run

.github/workflows/ci.yml

IntegrationTests/conftest.py

IntegrationTests/test_runner.py

.github/workflows/ci.yml

IntegrationTests/conftest.py

IntegrationTests/test_runner.py

smarr · 2025-07-11T19:28:40Z

Another small issue:

I have test that passes, but was expected to fail. Reporting this should be minimal, and does not need to show the whole stuff.

Currently, it shows this:

E           AssertionError: Test core-lib/IntegrationTests/Tests/integer_asdouble.som is in failing_as_unspecified but passed
E
E             Expected stdout:
E             1|    0.0
E             2|    1.0
E             3|    -1.0
E             4|    1.8446744073709552e19
E             5|    -1.8446744073709552e19
E             Given stdout   :
E             1|    0.0
E             2|    1.0
E             3|    -1.0
E             4|    1.8446744073709552e19
E             5|    -1.8446744073709552e19
E             6|
E             Expected stderr:
E
E             Given stderr   :
E             1|
E             Command used   : ./som.sh -cp Smalltalk core-lib/IntegrationTests/Tests/integer_asdouble.som
E             Case sensitive : False
E             Stdout diff    :
E               0.0
E               1.0
E               -1.0
E               1.8446744073709552e19
E             - -1.8446744073709552e19+ -1.8446744073709552e19
E             ?                       +
E
E             Stderr diff    :
E
E
E           assert False

But all that's needed is:
E AssertionError: Test core-lib/IntegrationTests/Tests/integer_asdouble.som is in failing_as_unspecified but passed

Also, it looks like there's something odd with the diff:

E - -1.8446744073709552e19+ -1.8446744073709552e19

IntegrationTests/Tests/case_insensitive.som

IntegrationTests/test_runner.py

rhys-h-walker · 2025-07-14T11:17:18Z

Another small issue:

I have test that passes, but was expected to fail. Reporting this should be minimal, and does not need to show the whole stuff.

Currently, it shows this:

E           AssertionError: Test core-lib/IntegrationTests/Tests/integer_asdouble.som is in failing_as_unspecified but passed
E
E             Expected stdout:
E             1|    0.0
E             2|    1.0
E             3|    -1.0
E             4|    1.8446744073709552e19
E             5|    -1.8446744073709552e19
E             Given stdout   :
E             1|    0.0
E             2|    1.0
E             3|    -1.0
E             4|    1.8446744073709552e19
E             5|    -1.8446744073709552e19
E             6|
E             Expected stderr:
E
E             Given stderr   :
E             1|
E             Command used   : ./som.sh -cp Smalltalk core-lib/IntegrationTests/Tests/integer_asdouble.som
E             Case sensitive : False
E             Stdout diff    :
E               0.0
E               1.0
E               -1.0
E               1.8446744073709552e19
E             - -1.8446744073709552e19+ -1.8446744073709552e19
E             ?                       +
E
E             Stderr diff    :
E
E
E           assert False

But all that's needed is: E AssertionError: Test core-lib/IntegrationTests/Tests/integer_asdouble.som is in failing_as_unspecified but passed

Also, it looks like there's something odd with the diff:

E - -1.8446744073709552e19+ -1.8446744073709552e19

Assertions that fail only by being in unspecified/known/unuspported now just show that they passed and are located inside of the tags file.

smarr · 2025-07-15T15:48:53Z

IntegrationTests/test_runner.py

+
+# ###############################################
+#  TEST BELOW THIS ARE TESTING THE RUNNER ITSELF
+# ###############################################


It would be good if all this goes into a separate file.
Would be good if there's an easy way to run the integration tests on a SOM VM, without getting distracted by the tests of the test runner.

smarr · 2025-07-15T15:50:07Z

IntegrationTests/test_runner.py

+    tests = sorted(tests)
+
+    expected_tests = [
+        "core-lib/IntegrationTests/test_runner_tests/soms_for_testing/som_test_1.som",


you're already using __file__ above. I am not really sure what the test here is doing, but the hard coded paths here means this fails when pytest is ran in another than the expected directory, which is not great.

Yep I agree, hadn't spotted that. This should fix that using a filepath which is generated at runtime.

expected_tests = [ f"{str(test_runner_tests_location)}/soms_for_testing/som_test_1.som", f"{str(test_runner_tests_location)}/soms_for_testing/som_test_2.som", f"{str(test_runner_tests_location)}/soms_for_testing/som_test_3.som", ]

IntegrationTests/test_runner.py

smarr · 2025-07-15T16:09:31Z

IntegrationTests/test_runner.py

+def assign_environment_variables(classpath, vm, test_exceptions, generate_report):
+    """
+    Assign the environment variables needed for execution based on the name
+    classpath: String being the name of the variable CLASSPATH
+    vm: String being the name of the variable VM
+    test_exceptions: String being the name of the variable TEST_EXCEPTIONS
+    generate_report: String being the name of the variable GENERATE_REPORT
+    """
+    # Work out settings for the application (They are labelled REQUIRED or OPTIONAL)
+    if classpath not in os.environ:  # REQUIRED
+        sys.exit("Please set the CLASSPATH environment variable")
+
+    if vm not in os.environ:  # REQUIRED
+        sys.exit("Please set the VM environment variable")
+
+    if test_exceptions in os.environ:  # OPTIONAL
+        external_vars.TEST_EXCEPTIONS = os.environ[test_exceptions]
+
+    if generate_report in os.environ:  # OPTIONAL
+        # Value is the location
+        # Its prescense in env variables signifies intent to save
+        external_vars.GENERATE_REPORT = os.environ[generate_report]
+
+    external_vars.CLASSPATH = os.environ[classpath]
+    external_vars.VM = os.environ[vm]


Hm, I am not sure I see the benefit of having this a function.
Also, passing in the constants on call seems to make this just harder to figure out.

My initial idea was to convert this to a method call to be able to test the logic, however I've not thought of a good way of doing such so it will probably revert back to the old implementation.

smarr · 2025-07-15T22:18:22Z

Hm, there's some problem with the current output.

Looks like everything is turned lower case:

E     stdout diff with stdout expected
E
E       0
E     - 1
E     - true
E     - false
E     - false
E     - false
E     - true
E     - false
E     - false
E     - false
E     stderr diff with stderr expected
E
E     + warning: a terminally deprecated method in sun.misc.unsafe has been called
E     + warning: sun.misc.unsafe::objectfieldoffset has been called by com.oracle.truffle.api.nodes.nodeclassimpl$nodefielddata (file:/users/smarr/projects/som/trufflesom/../graal/truffle/mxbuild/dists/truffle-api.jar)
E     + warning: please consider reporting this to the maintainers of class com.oracle.truffle.api.nodes.nodeclassimpl$nodefielddata
E     + warning: sun.misc.unsafe::objectfieldoffset will be removed in a future release
E     + exception in thread "main" org.graalvm.polyglot.polyglotexception: com.oracle.truffle.api.dsl.unsupportedspecializationexception: unexpected values provided for booleaninlinedliteralnode.andinlinedliteralnode@51549490: [1], [long]
E     + 	at trufflesom/trufflesom.interpreter.nodes.specialized.booleaninlinedliteralnode.evaluateargument(booleaninlinedliteralnode.java:48)
E     + 	at trufflesom/trufflesom.interpreter.nodes.specialized.booleaninlinedliteralnode$andinlinedliteralnode.executeboolean(booleaninlinedliteralnode.java:69)
E     + 	at trufflesom/trufflesom.interpreter.nodes.specialized.booleaninlinedliteralnode$andinlinedliteralnode.executegeneric(booleaninlinedliteralnode.java:63)
E     + 	at trufflesom/trufflesom.interpreter.nodes.sequencenode.executegeneric(sequencenode.java:48)
E     + 	at trufflesom/trufflesom.interpreter.method.execute(method.java:62)
E     + 	at <som> bool4>>#run(unknown)
E     + 	at <som> system>>#initialize:(smalltalk/system.som:48:1961-1963)
E     + 	at <som> (unknown)
E     + 	at org.graalvm.polyglot/org.graalvm.polyglot.context.eval(context.java:418)
E     + 	at trufflesom/trufflesom.launcher.eval(launcher.java:32)
E     + 	at trufflesom/trufflesom.launcher.main(launcher.java:13)
E     + original internal error:
E     + com.oracle.truffle.api.dsl.unsupportedspecializationexception: unexpected values provided for booleaninlinedliteralnode.andinlinedliteralnode@51549490: [1], [long]

rhys-h-walker · 2025-07-15T22:57:05Z

Hm, there's some problem with the current output.

Looks like everything is turned lower case:

E     stdout diff with stdout expected
E
E       0
E     - 1
E     - true
E     - false
E     - false
E     - false
E     - true
E     - false
E     - false
E     - false
E     stderr diff with stderr expected
E
E     + warning: a terminally deprecated method in sun.misc.unsafe has been called
E     + warning: sun.misc.unsafe::objectfieldoffset has been called by com.oracle.truffle.api.nodes.nodeclassimpl$nodefielddata (file:/users/smarr/projects/som/trufflesom/../graal/truffle/mxbuild/dists/truffle-api.jar)
E     + warning: please consider reporting this to the maintainers of class com.oracle.truffle.api.nodes.nodeclassimpl$nodefielddata
E     + warning: sun.misc.unsafe::objectfieldoffset will be removed in a future release
E     + exception in thread "main" org.graalvm.polyglot.polyglotexception: com.oracle.truffle.api.dsl.unsupportedspecializationexception: unexpected values provided for booleaninlinedliteralnode.andinlinedliteralnode@51549490: [1], [long]
E     + 	at trufflesom/trufflesom.interpreter.nodes.specialized.booleaninlinedliteralnode.evaluateargument(booleaninlinedliteralnode.java:48)
E     + 	at trufflesom/trufflesom.interpreter.nodes.specialized.booleaninlinedliteralnode$andinlinedliteralnode.executeboolean(booleaninlinedliteralnode.java:69)
E     + 	at trufflesom/trufflesom.interpreter.nodes.specialized.booleaninlinedliteralnode$andinlinedliteralnode.executegeneric(booleaninlinedliteralnode.java:63)
E     + 	at trufflesom/trufflesom.interpreter.nodes.sequencenode.executegeneric(sequencenode.java:48)
E     + 	at trufflesom/trufflesom.interpreter.method.execute(method.java:62)
E     + 	at <som> bool4>>#run(unknown)
E     + 	at <som> system>>#initialize:(smalltalk/system.som:48:1961-1963)
E     + 	at <som> (unknown)
E     + 	at org.graalvm.polyglot/org.graalvm.polyglot.context.eval(context.java:418)
E     + 	at trufflesom/trufflesom.launcher.eval(launcher.java:32)
E     + 	at trufflesom/trufflesom.launcher.main(launcher.java:13)
E     + original internal error:
E     + com.oracle.truffle.api.dsl.unsupportedspecializationexception: unexpected values provided for booleaninlinedliteralnode.andinlinedliteralnode@51549490: [1], [long]

Output will be converted to lower case if case_sensitive is not set to be true in the test file. If case sensitivity is imperative for a test then it needs to be specified in the test file. The diff just reflects that, unless I am missing something in the output.

smarr · 2025-07-16T09:49:38Z

Output will be converted to lower case if case_sensitive is not set to be true in the test file. If case sensitivity is imperative for a test then it needs to be specified in the test file. The diff just reflects that, unless I am missing something in the output.

Hm, right. True, it's the diff.
I found it confusing seeing it like this. Hmmm...

rhys-h-walker · 2025-07-16T11:44:51Z

Output will be converted to lower case if case_sensitive is not set to be true in the test file. If case sensitivity is imperative for a test then it needs to be specified in the test file. The diff just reflects that, unless I am missing something in the output.

Hm, right. True, it's the diff. I found it confusing seeing it like this. Hmmm...

I could show the output in upper case and then show the diff, but I think the diff showing what is actually compared makes more sense otherwise it would point out case differences.

This is a PyTest-based runner for the integration tests of SOM. - Test expectations can be set through a tagging system. Uses a yaml file which can be specified through TEST_EXCEPTIONS envvar

- The report generated is now in yaml format. It can function as a TEST_EXCEPTIONS file with failing tests and passing tests, added and removed as needed. It should not be blindly followed but makes the generation of a tags file very easy. - It comes with additional information like number passed/skipped and which ones exactly have been changed. - Test runner is now case insensitive unless instructed not to be through case_sensitive: True in the tests. - It is also possible to now in the test level expect a test to fail. This allows for testing of test_runner features. Not ideal but makes sure case_sensitivity works correctly. - adjusted the reading of filepaths to require only 1 str() call - Tests now sorted / Name of check_out changed. Comments updated to reflect variable naming - Diff is now shown in error message

… string. - skip test on Unicode Failure

- Removed Print statements leftover - Updated error handling to just show diff unless no diff is available - EXECUTABLE changed to be VM - Added some basic test_runner tests - Make a diff reverted to just be a diff and not have line numbers - be strict on inclusion in stdout/stderr - Removed the lang_tests and adjusted the test_runner logic to now print a proper error on /Tests folder not found - Fix conftest to output a string rather than an object for exitstatus - Fixed error with missing or empty tag file, addded test to assert that the yaml files are working correctly - Added an additional test to check the robustness of read_test_exceptions - Fixed an error where specifying case_sensitive: False would not register as False but True instead - Added a new tests to test the discovery of lang_tester valid tests inside a directory - Pathname for TEST_EXCEPTIONS now just takes a filename if it is located within IntegrationTests. - Adjusted test_test_diccovery to use relative path names rather than hard coded - There are now two options for running pytest, normally and execute just the som tests and with the argument -m tester which will run the test_runner tests located in test_tester - Added deselect message when tests are deselected due to runner choice - Filepaths must now be given from IntegrationTests onwards so: Tests/test.som - Updated to now use relative paths rather than hardcoded for TEST_EXCEPTIONS

Signed-off-by: Stefan Marr <[email protected]>

…ests() It’s only needed when the tests are prepared. Signed-off-by: Stefan Marr <[email protected]>

smarr · 2025-07-16T23:21:02Z

@rhys-h-walker I squashed lots of commits, to have a better overview. I also rebased on the new master, that contains the merge with integration tests.

Please have a look at the commits I added, there were various bits that I pointed out earlier, and that simplify the code a bit.

Please also have a look at the test_tester stuff.
At the moment it depends on the directory pytest is executed in whether the tests pass or not.

This passes: core-lib/IntegrationTests$ pytest -s -v test_tester.py -m tester

But from one level up, it doesn't work: core-lib$ pytest -s -v IntegrationTests/test_tester.py -m tester

>       assert external_vars.known_failures == test_list
E       AssertionError: assert ['Integration...hod/test.som'] == ['./Tests/mut...hod/test.som']
E         
E         At index 0 diff: 'IntegrationTests/Tests/mutate_superclass_method/test.som' != './Tests/mutate_superclass_method/test.som'
E         
E         Full diff:
E           [
E         -     './Tests/mutate_superclass_method/test.som',
E         ?      ^...

rhys-h-walker · 2025-07-17T08:48:09Z

@rhys-h-walker I squashed lots of commits, to have a better overview. I also rebased on the new master, that contains the merge with integration tests.

Please have a look at the commits I added, there were various bits that I pointed out earlier, and that simplify the code a bit.

Please also have a look at the test_tester stuff. At the moment it depends on the directory pytest is executed in whether the tests pass or not.

This passes: core-lib/IntegrationTests$ pytest -s -v test_tester.py -m tester

But from one level up, it doesn't work: core-lib$ pytest -s -v IntegrationTests/test_tester.py -m tester
>       assert external_vars.known_failures == test_list
E       AssertionError: assert ['Integration...hod/test.som'] == ['./Tests/mut...hod/test.som']
E         
E         At index 0 diff: 'IntegrationTests/Tests/mutate_superclass_method/test.som' != './Tests/mutate_superclass_method/test.som'
E         
E         Full diff:
E           [
E         -     './Tests/mutate_superclass_method/test.som',
E         ?      ^...

Yep, that's an easy enough fix I think one of the testers is missing a relative path.

I have also noticed that the GENERATE_REPORT function no longer works correctly. The names it outputs for test include the whole core-lib/IntegrationTests so it no longer works directly as a TEST_EXCEPTIONS file. I'll fix that too

rhys-h-walker · 2025-07-17T09:24:06Z

Also, Tests/vector_awfy_capacity.som may need updating, it features a fixed classpath that is passed to the SOM++ interpreter.

VM:
    status: success
    custom_classpath: ./core-lib/Examples/AreWeFastYet/Core:./core-lib/Smalltalk
    stdout:
        50
        100
        10

It'll need some kind of relative path location added to it

…o that passing.yaml can be recognised

smarr · 2025-07-17T09:30:46Z

It'll need some kind of relative path location added to it

hm, yeah, I suppose that's a little different to the load_file case where it's inside the SOM program. Not sure whether we can find a consistent way of deal with both.

…remove anything in the path from before Tests/

…variable by that name. Useful for custom classpath loading

rhys-h-walker · 2025-07-17T13:45:23Z

It'll need some kind of relative path location added to it

hm, yeah, I suppose that's a little different to the load_file case where it's inside the SOM program. Not sure whether we can find a consistent way of deal with both.

This issue is resolved, specify through @tag an environment variable which can be used in place for a custom_classpath.


AWFY=./core-lib/Examples/AreWeFastYet/Core
CLASSPATH=./Smalltalk

"
VM:
    status: success
    custom_classpath: @AWFY:@CLASSPATH
    stdout:
        nil

"

custom_classpath= ./core-lib/Examples/AreWeFastYet/Core:./Smalltalk

…w match what is expected

… Tests/ So all tests will be Tests/test.som

IntegrationTests/test_runner.py

Signed-off-by: Stefan Marr <[email protected]>

…pdated parse_test_file to feature methods rather than one large method, Allows for more fine grained testing

… file

smarr reviewed Jul 10, 2025

View reviewed changes

smarr reviewed Jul 11, 2025

View reviewed changes

IntegrationTests/conftest.py Outdated Show resolved Hide resolved

smarr reviewed Jul 11, 2025

View reviewed changes

IntegrationTests/test_runner.py Outdated Show resolved Hide resolved

smarr reviewed Jul 11, 2025

View reviewed changes

IntegrationTests/test_runner.py Outdated Show resolved Hide resolved

smarr reviewed Jul 11, 2025

View reviewed changes

IntegrationTests/test_runner.py Outdated Show resolved Hide resolved

smarr reviewed Jul 11, 2025

View reviewed changes

IntegrationTests/Tests/case_insensitive.som Outdated Show resolved Hide resolved

smarr reviewed Jul 11, 2025

View reviewed changes

IntegrationTests/test_runner.py Show resolved Hide resolved

smarr reviewed Jul 11, 2025

View reviewed changes

IntegrationTests/test_runner.py Outdated Show resolved Hide resolved

smarr reviewed Jul 11, 2025

View reviewed changes

IntegrationTests/test_runner.py Outdated Show resolved Hide resolved

rhys-h-walker mentioned this pull request Jul 14, 2025

Adding yksom's lang_tests #129

Merged

smarr force-pushed the rhys-integration-tests branch from c830358 to 493648b Compare July 14, 2025 22:24

smarr reviewed Jul 15, 2025

View reviewed changes

IntegrationTests/test_runner.py Outdated Show resolved Hide resolved

smarr reviewed Jul 15, 2025

View reviewed changes

smarr force-pushed the rhys-integration-tests branch from 1b2c0f4 to 6d13aa9 Compare July 16, 2025 22:01

rhys-h-walker added 3 commits July 16, 2025 23:07

Implement test_runner.py, being mostly lang_tester compatible

b3aeffa

This is a PyTest-based runner for the integration tests of SOM. - Test expectations can be set through a tagging system. Uses a yaml file which can be specified through TEST_EXCEPTIONS envvar

Updated CI to run Black and PyLint, and integration tests

a4df605

Added README

fe5fd3d

smarr force-pushed the rhys-integration-tests branch from 6d13aa9 to c07858e Compare July 16, 2025 22:22

rhys-h-walker added 3 commits July 16, 2025 23:29

SOM UnicodeDecodeError: now more robust against a failure in decode a…

4883d65

… string. - skip test on Unicode Failure

smarr added 2 commits July 16, 2025 23:36

Fix PyLint issues and apply Black formatting

4546e22

Signed-off-by: Stefan Marr <[email protected]>

Update GHA to use VM and integration-tests.yml

79a727c

Signed-off-by: Stefan Marr <[email protected]>

smarr force-pushed the rhys-integration-tests branch from c07858e to 79a727c Compare July 16, 2025 22:37

smarr added 5 commits July 16, 2025 23:56

Fix typos

f0cdac4

Signed-off-by: Stefan Marr <[email protected]>

Run PyTest tests for the tester

f870963

Signed-off-by: Stefan Marr <[email protected]>

Simplify code

92d9a0e

Signed-off-by: Stefan Marr <[email protected]>

Simplify assertions, pytest already shows that info

f25126f

Signed-off-by: Stefan Marr <[email protected]>

Make failures pytest.fail, and move reading of envvars into prepare_t…

59e82e4

…ests() It’s only needed when the tests are prepared. Signed-off-by: Stefan Marr <[email protected]>

Updated to now feature relative paths from CWD for testing

1c9f4bc

Path now checks for current directory and removes "." from its name s…

8759095

…o that passing.yaml can be recognised

rhys-h-walker added 3 commits July 17, 2025 10:34

GENERATE_REPORT is now compatible with multiple directories. It will …

1f17fc3

…remove anything in the path from before Tests/

Text exceptions no longer alters path to yaml file

d3c2472

Can now specify @tag_name in custom_classpath to load an environment …

400dbb5

…variable by that name. Useful for custom classpath loading

rhys-h-walker added 2 commits July 17, 2025 14:56

Updated pytest parameterize to not run prepare_tests twice and IDs no…

81e3455

…w match what is expected

Updated GENERATE_REPORT to have all tests with a consistent name from…

bc2d1ce

… Tests/ So all tests will be Tests/test.som

smarr reviewed Jul 17, 2025

View reviewed changes

IntegrationTests/test_runner.py Outdated Show resolved Hide resolved

smarr reviewed Jul 17, 2025

View reviewed changes

IntegrationTests/test_runner.py Outdated Show resolved Hide resolved

smarr and others added 8 commits July 17, 2025 22:57

Apply black

5c34d6f

Signed-off-by: Stefan Marr <[email protected]>

Remove redundant assert messages

d068996

Signed-off-by: Stefan Marr <[email protected]>

Updated test_runner to feature more robust @tag classpath swapping. U…

7a024e7

…pdated parse_test_file to feature methods rather than one large method, Allows for more fine grained testing

Updated test_tester to feature more rigorous tests for parsing a test…

a760cf2

… file

Updated README to better represent the project

d33082f

Added a new test for check_partial_word

25ba5d3

Ran black

98b1d9c

Added new tests and updated formatting and style checks accordingly

4a46a6e

Integration Tests for the SOM language #128

Are you sure you want to change the base?

Integration Tests for the SOM language #128

Uh oh!

Conversation

rhys-h-walker commented Jul 9, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

smarr commented Jul 11, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

rhys-h-walker commented Jul 14, 2025

Uh oh!

smarr Jul 15, 2025

Choose a reason for hiding this comment

Uh oh!

smarr Jul 15, 2025

Choose a reason for hiding this comment

Uh oh!

rhys-h-walker Jul 15, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

smarr Jul 15, 2025

Choose a reason for hiding this comment

Uh oh!

rhys-h-walker Jul 15, 2025

Choose a reason for hiding this comment

Uh oh!

smarr commented Jul 15, 2025

Uh oh!

rhys-h-walker commented Jul 15, 2025

Uh oh!

smarr commented Jul 16, 2025

Uh oh!

rhys-h-walker commented Jul 16, 2025

Uh oh!

smarr commented Jul 16, 2025

Uh oh!

rhys-h-walker commented Jul 17, 2025

Uh oh!

rhys-h-walker commented Jul 17, 2025

Uh oh!

smarr commented Jul 17, 2025

Uh oh!

rhys-h-walker commented Jul 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

rhys-h-walker commented Jul 17, 2025 •

edited

Loading