-
Notifications
You must be signed in to change notification settings - Fork 15
docs(known-issues): note recent CI hits for SymbolIndexStore race #74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -24,3 +24,4 @@ This document tracks known limitations and deferred improvements in MachOSwiftSe | |||||
| - **Why deferred:** Running individual sub-suites (for example `--filter SwiftInterfaceBuilderTestSuite.MachOFileTests`) passes reliably, and end-to-end tests (`SymbolTestsCoreE2ETests`, `MachOSymbolsTests`, `DemanglingTests`) also pass. Only the parallel-suite harness configuration exposes the race, so ordinary CLI workflows are unaffected. | ||||||
| - **Potential fix:** Either (a) guard `demangledNodeBySymbol` with the same `SharedCache` mutex that already wraps `Storage` access, (b) make `setDemangledNode`/`demangledNodeBySymbol` itself thread-safe with an internal lock, or (c) pre-populate `demangledNodeBySymbol` completely during `buildStorageImpl` so `demangledNode(for:in:)` becomes read-only at query time. | ||||||
| - **Tracking:** Observed during PR #61 review-follow-up testing. | ||||||
| - **Recent CI hits:** reproduced on `main` push runs under `.github/workflows/macOS.yml` — after merging `docs/readme-0.9.1` the debug-mode `swift test` step crashed with signal 11 (run 24628302034), and after merging `release/0.10.0` the release-mode step crashed the same way (run 24633097766). Both commits passed on their matching PR-branch runs (e.g. run 24633093885 for `release/0.10.0`), reinforcing the parallel-harness-only nature of the race. | ||||||
|
||||||
| - **Recent CI hits:** reproduced on `main` push runs under `.github/workflows/macOS.yml` — after merging `docs/readme-0.9.1` the debug-mode `swift test` step crashed with signal 11 (run 24628302034), and after merging `release/0.10.0` the release-mode step crashed the same way (run 24633097766). Both commits passed on their matching PR-branch runs (e.g. run 24633093885 for `release/0.10.0`), reinforcing the parallel-harness-only nature of the race. | |
| - **Recent CI hits:** Reproduced on `main` push runs under `.github/workflows/macOS.yml` — after merging `docs/readme-0.9.1` the debug-mode `swift test` step crashed with signal 11 (run 24628302034), and after merging `release/0.10.0` the release-mode step crashed the same way (run 24633097766). Both commits passed on their matching PR-branch runs (e.g. run 24633093885 for `release/0.10.0`), reinforcing the parallel-harness-only nature of the race. |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The description following the bold label should start with a capital letter to maintain consistency with the existing entries in this file (e.g., lines 22, 24, and 26).