add basic logging for test failures

[sanjays-ms]

Context

GradleV3 Task Logging
The GradleV3 Task was printing code analysis failure messages when the pipeline was failing due to test case failures.

---

Task Name

GradleV3

---

Description

Changed output log messages to output gradle output as such.

Risk Assessment

Medium
Justification: Changing the existing logging message so customers using this task will see a change in logs in future pipeline runs in case of pipeline failures.

[sanjays-ms]

@microsoft-github-policy-service agree company="Microsoft"

[tarunramsinghani]

These checks will fail in case of localization i.e. if this is running on some machine with different language. we need a better way to identify what is failing.

[sanjays-ms]

/azp run

[sanjays-ms]

/azp run

[Copilot]

Pull Request Overview

This PR enhances the GradleV3 task by capturing and surfacing Gradle output when the task fails, so that test failures are logged more clearly.

• Bump task version (Minor: 247→257, Patch: 1→0)
• Add an optional error field to ITaskResult and update resolveTaskResult to include full Gradle output
• Capture Gradle’s stdout/stderr via custom streams and log the aggregated error output

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
Tasks/GradleV3/task.loc.json	Updated Minor/Patch version numbers
Tasks/GradleV3/task.json	Updated Minor/Patch version numbers
Tasks/GradleV3/interfaces.ts	Added error?: string to ITaskResult
Tasks/GradleV3/gradletask.ts	Created stdoutStream/stderrStream to collect output, passed to gradleRunner.exec, and log taskResult.error
Tasks/GradleV3/Modules/utils.ts	Extended resolveTaskResult signature to accept gradleOutput and populate the error field

Comments suppressed due to low confidence (3)

Tasks/GradleV3/Modules/utils.ts:10

• Update the JSDoc comment for resolveTaskResult to describe the new gradleOutput parameter and explain the purpose of the returned error field for clearer API docs.

export function resolveTaskResult(codeAnalysisResult: ICodeAnalysisResult, gradleOutput: string[]): ITaskResult {

Tasks/GradleV3/Modules/utils.ts:21

• There are no unit tests covering the new error aggregation in resolveTaskResult; consider adding tests for non-zero exit codes to verify both the message and error fields.

error = gradleOutput.join('');

Tasks/GradleV3/interfaces.ts:41

• [nitpick] Add a comment or JSDoc for the new error property in ITaskResult to describe when it will be populated and what it contains.

error?: string;

[Copilot]

[nitpick] Storing the entire Gradle output in memory may lead to high memory usage for large builds. Consider streaming to a temporary file or imposing a size limit on the buffer.

Suggested change

	const gradleOutput: string[] = [];
	const stdoutStream = new stream.Writable({
	write: (chunk, encoding, callback) => {
	const output = chunk.toString();
	gradleOutput.push(output);
	const fs = require('fs');
	const os = require('os');
	const path = require('path');
	const tempFilePath = path.join(os.tmpdir(), `gradle-output-${Date.now()}.log`);
	const outputStream = fs.createWriteStream(tempFilePath);
	const stdoutStream = new stream.Writable({
	write: (chunk, encoding, callback) => {
	const output = chunk.toString();
	outputStream.write(output);

[Copilot]

[nitpick] Use console.error instead of console.log when emitting error details, to ensure these messages are clearly marked as errors in the logs.

Suggested change

	console.log(taskResult.error);
	console.error(taskResult.error);

[sanjays-ms]

/azp run

[sanjays-ms]

/azp run

[tarunramsinghani]

Can you please add how the task output has changed after teh change ? both the cases i.e. a successful build and build with test failures.