You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are test failures on main because the tests throw errors with the message "Access violation in generated code when writing ...". It seems to be only happening on Windows.
To Reproduce
Follow the steps defined by the haskell.yml Github Actions workflow. It is not clear whether the bugs can reproduced locally, since I (@jorisdral) don't have a Windows machine to try it out on.
Desktop (please complete the following information):
OS: Windows
OS version: Windows Server 2022
GHC: 8.10.7, 9.8.2
Additional context
These tests have started showing up after #539 was merged. Maybe there are some out-of-bounds byte array accesses introduced by that PR?
The text was updated successfully, but these errors were encountered:
Describe the bug
There are test failures on
main
because the tests throw errors with the message "Access violation in generated code when writing ...". It seems to be only happening on Windows.To Reproduce
Follow the steps defined by the
haskell.yml
Github Actions workflow. It is not clear whether the bugs can reproduced locally, since I (@jorisdral) don't have a Windows machine to try it out on.Expected behavior
Tests should pass
Output
https://github.com/IntersectMBO/lsm-tree/actions/runs/12958624976/job/36149389798
https://github.com/IntersectMBO/lsm-tree/actions/runs/12958624976/job/36149392812
https://github.com/IntersectMBO/lsm-tree/actions/runs/12958624976/job/36149392812
https://github.com/IntersectMBO/lsm-tree/actions/runs/12958624976/job/36149389798
The following might also be related, but does not produce the same error message:
https://github.com/IntersectMBO/lsm-tree/actions/runs/12951447199/job/36126516458
Desktop (please complete the following information):
Additional context
These tests have started showing up after #539 was merged. Maybe there are some out-of-bounds byte array accesses introduced by that PR?
The text was updated successfully, but these errors were encountered: