Open
Conversation
Collaborator
Generated by 🚫 Danger |
Contributor
|
| App Name | Jetpack | |
| Configuration | Release-Alpha | |
| Build Number | 31211 | |
| Version | PR #25310 | |
| Bundle ID | com.jetpack.alpha | |
| Commit | eb00410 | |
| Installation URL | 3ajhu4c7cdr3g |
Contributor
|
| App Name | WordPress | |
| Configuration | Release-Alpha | |
| Build Number | 31211 | |
| Version | PR #25310 | |
| Bundle ID | org.wordpress.alpha | |
| Commit | eb00410 | |
| Installation URL | 2nuhn32k9jrf8 |
Contributor
🤖 Build Failure AnalysisThis build has failures. Claude has analyzed them - check the build annotations for details. |
CI handles builds and tests via Fastlane; the `xcodebuild`-wrapping Rake tasks were unused. --- Generated with the help of Claude Code, https://claude.ai/code Co-Authored-By: Claude Code Opus 4.6 <noreply@anthropic.com>
Skips CI prerequisites (env files, signing, toolkit checks) and reuses DerivedData for incremental builds. Supports only_testing, scheme, device, and clean options. --- Generate with the help of Claude Code, https://code.claude.com Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
--- Generate with the help of Claude Code, https://code.claude.com Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The file was in a `WordPressUITests` directory with no matching SPM target, so it was never compiled or run. Updated its import from `WordPress` to `WordPressUI`. --- Generate with the help of Claude Code, https://code.claude.com Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Applies the same test-bundle workaround already used elsewhere in WordPressUI so the storyboard loads in SPM test context. --- Generate with the help of Claude Code, https://code.claude.com Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The test calendar used `.eastern` but the service used `.current`, so date interval keys never aligned. --- Generate with the help of Claude Code, https://code.claude.com Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The test crashes when DesignSystem is built as a dynamic library, which happens because WordPressAuthenticator (also in the plan) depends on it transitively. --- Generate with the help of Claude Code, https://code.claude.com Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Use `Bundle.designSystemBundle` instead of `.module` so resources resolve when Xcode builds the module as a dynamic library (same workaround as WordPressUI). --- Generate with the help of Claude Code, https://code.claude.com Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Prefer Xcode MCP when available, fall back to Fastlane. --- Generated with the help of Claude Code, https://claude.ai/code Co-Authored-By: Claude Code Opus 4.6 <noreply@anthropic.com>
When `clean:false` (the default), packages are already resolved from a previous build. Passing `-skipPackageResolving` via `skip_package_dependencies_resolution` avoids redundant resolution on incremental test runs. --- Generated with the help of Claude Code, https://claude.ai/code Co-Authored-By: Claude Code Opus 4.6 <noreply@anthropic.com>
mokagio
force-pushed
the
ainfra-1963-refine-claudemd-in-wordpress-ios-with-build-test-loop-2
branch
from
5e7bd4f to
918c849
Compare
This way, we can properly configure it and SwiftPM won't clobber it from the .swiftpm folder at its own discretion.
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
Supersedes #25242 to address @kean 's experience trying to run tests.
The core difference is that
AGENTS.mdinstructs to prioritize Xcode's MCP.Testing instructions
I retried all of Alex's experiments.
Test WordPressData
Run into an issue. The MCP couldn't find the target/scheme to run
Successfully fell back to Fastlane, but no luck there either. Claude then discovered the scheme and used
xcodebuild:Action Item:
xctestplanfor WordPressDataTest WordPressShared
Again, the first MCP call failed
Claude then opted for
xcodebuildgiven it worked before. It deprioritized the instruction inAGENTS.md. I let it run to see how it worked. Unfortunately, it kept running into linker issues.Retried with explicit instruction to exhaust all MCP options first. Got stuck on this:
Cancelled and looked at Xcode on my own. Test run fine. I did a few more iterations of this test and figured out the issue is with how SwiftPM autogenerates the schemes Xcode uses for packages.
I worked around this by creating a new scheme for WordPressShared in the project container so that it won't be accidentally modified:
However, despited having the scheme in place Claude did something funky here running the tests one at a time, but at least it worked and it was relatively fast.
Make a small change to WordPressShared that would result in an error
I changed a test so that it would fail. MCP test failed to detect it
Only picked up the failure when instructed
Run all tests (without reverting the failing test)
I haven't investigated the expected failure or not run tests.
Run all tests (after reverting the intentional failure)