Disable custom Copilot setup for support diagnosis#1159
Merged
Conversation
Contributor
JUnit Test Overview ReportGenerated on: 28125814204 Overall Statistics
Test Summary by Plugin
Disabled Tests Detailssandbox_common_test (2 disabled)
sandbox_functional_converter_test (26 disabled)
sandbox_int_to_enum_test (1 disabled)
sandbox_jface_cleanup_test (1 disabled)
sandbox_junit_cleanup_test (36 disabled)
sandbox_platform_helper_test (1 disabled)
This report is automatically generated by the Test Report workflow |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR disables the repository’s custom Copilot cloud agent setup steps to help GitHub Support diagnose Copilot agent sessions hanging (Support ticket 4157159), while preserving the prior setup workflow content for later comparison.
Changes:
- Added
.github/workflows/copilot-setup-steps.yml.disabledcontaining the previous Copilot setup workflow content. - Replaced
.github/workflows/copilot-setup-steps.ymlwith a minimal no-op workflow that only logs diagnostic messages.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/workflows/copilot-setup-steps.yml.disabled | Preserves the prior custom Copilot setup workflow (Java/Maven/cache/Xvfb) in a non-active file for reference. |
| .github/workflows/copilot-setup-steps.yml | Disables all custom setup actions by replacing them with a minimal no-op workflow for support diagnosis. |
Contributor
Test Results 225 files 225 suites 4m 9s ⏱️ Results for commit 3a6e28a. |
Contributor
✅ All Tests PassedNo test failures detected. This comment is automatically updated with test failure details for each commit. |
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
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.
This PR follows GitHub Support's request from ticket 4157159 to rule out the custom Copilot cloud agent environment setup.
What changed:
.github/workflows/copilot-setup-steps.ymlcontent in.github/workflows/copilot-setup-steps.yml.disabled..github/workflows/copilot-setup-steps.ymlwith a minimal no-op workflow.Why:
GitHub Support asked to remove or rename the custom setup file and then start a fresh Copilot agent session. The previous setup installed Java/Maven tooling, restored Maven caches, installed GUI libraries, and started Xvfb. Any of these steps could affect Copilot cloud agent initialization or make sessions appear stuck.
Note:
The direct delete/rename operation was not available via the connector, so this PR disables all custom setup commands while preserving the old file for comparison. If GitHub Support requires the filename itself to disappear completely, the active
.github/workflows/copilot-setup-steps.ymlfile can be deleted manually after this PR is reviewed.