Test case observing unexpected gameTicks value

[dagpunk]

In run https://github.com/viperior/rimhistory/runs/6662782380

The gameTicks value is off, but not by much. Not sure if this is because I forgot to update after changing the test data or if it's a sorting issue. Determine the root cause and fix so build workflow passes.

[dagpunk]

test_data_list = ['test_data/demosave 3.rws.gz', 'test_data/demosave 1.rws.gz', 'test_data/demosave 2.rws.gz']

    def test_game_time_ticks(test_data_list: list) -> None:
        """Test the Save class's game_time_ticks property
    
        Parameters:
        test_data_list (list): The list of paths to the test input data files (fixture)
    
        Returns:
        None
        """
        game_time_ticks = Save(test_data_list[0]).data.game_time_ticks
        logging.debug("game_time_ticks = %d", game_time_ticks)
        assert isinstance(game_time_ticks, int)
>       assert game_time_ticks == 41164371
E       assert 45197193 == 41164371

[dagpunk]

Looks like the sort method changed. Could be related to the recent update to 'wcmatch'. Can probably fix by sorting the file list (ascending) before running the test.

[dagpunk]

Update: I think this is caused by the arbitrary return order of glob list elements. Sorting the list in ascending order before returning the list in the test_data_list fixture should resolve this:
https://github.com/viperior/rimhistory/blob/7406f093496ba523162d20506aee659a9d8dff89/tests/conftest.py#L23