Run the gate and the manual checks on real macOS #2
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#18 Build a macOS package
ethan-hann/SavePoint
Reference
ethan-hann/SavePoint#2
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
macOS has never been built or run (D9). Its code stays on the shared POSIX paths and its tables are covered by data-driven tests, but nothing has checked them on hardware.
Steps are in docs/testing-on-mac-and-linux.md: clone, install the .NET 10 SDK, run
bash build/gate.sh, then the manual checks (Cmd+Q during a job, .app bundle games, APFS case handling, the denylist, VoiceOver, notifications through osascript, reduced motion).Done when the gate passes on macOS, or each failure has its own issue, and the manual results are recorded on this issue.
Add to the Mac pass: check the 7 Days to Die template's mods folder on a real Mac. The template resolves it to ~/Library/Application Support/7DaysToDie/Mods, beside the saves folder (pinned by ModsFolderTemplateTests with an injected macOS platform), but nothing confirms the game really reads mods from there (#221, D61).
Add to the Mac pass: run HostIdentityTests, PathSafetyPinTests and FolderRecheckTests on a real Mac (Intel and Apple Silicon if both are at hand). The folder identity is read with stat$INODE64, falling back to stat, using the documented 64-bit-inode layout (st_dev int32 at 0, st_ino uint64 at 8), but it has never run on a Mac (#167, D57). If the read fails it returns null and the path-plus-marker check still applies; a wrong read would instead refuse destructive steps with a folder-changed error.