[CI CONTROL — do not merge] no-op against protocol-next - #208
Closed
sisuresh wants to merge 1 commit into
Closed
Conversation
…integration failures Empty commit — no file changes, no XDR regen, no go-sdk pin. Purpose: confirm whether the P27 integration-test failures seen on the CAP-0085 PR (stellar#207) are pre-existing on protocol-next (unhealthy stellar-rpc container) rather than caused by that PR's changes. Draft; to be closed once CI reports.
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
1 participant
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.
Not a real change. Single empty commit, zero file diff against
protocol-next(no XDR regen, no go-stellar-sdk pin).Purpose: control experiment for #207. The CAP-0085 PR's P27 integration legs fail with an unhealthy
stellar-rpccontainer (data stores are not initialized: DB is empty, JSON-RPC -32603, connection resets); the P28 legs pass only because their RPC image is empty and RPC-dependent tests AMBER-skip. This PR carries none of #207's changes, so if its P27 legs fail the same way, the failure is pre-existing onprotocol-next/ infra, not caused by CAP-0085.Will be closed once CI reports.