Fix Copilot parser to find session logs after artifact flattening #8963
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.
The Copilot parser couldn't locate session log files after artifact flattening. The issue was that artifact download structures vary depending on how GitHub Actions handles uploaded paths, and the parser only checked specific expected locations.
Changes
logs_parsing.go: Enhanced
findAgentLogFile()with robust search strategyagent_output/directory (pre-flattening, backward compatibility)/tmp/gh-aw/prefix and checks expected flattened location:sandbox/agent/logs/session*.logfiles to handle any artifact structurelogs_test.go: Added test cases for Copilot engine
logs_copilot_flattening_integration_test.go: Added comprehensive integration tests
Example
The parser now correctly discovers session logs regardless of artifact structure, handling:
agent_output/)sandbox/agent/logs/)session*.logfilesOriginal prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.