Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CI] LoggedExecFuncTest failed tasks output logged to console when spooling true failing #119509

Open
elasticsearchmachine opened this issue Jan 3, 2025 · 2 comments
Labels
:Delivery/Build Build or test infrastructure needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

null

Applicable branches:
8.16

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

org.spockframework.runtime.ConditionNotSatisfiedError: Condition not satisfied:

normalized(givenOutput).contains(normalized(expected))
|          |            |        |          |
|          |            false    |          No such file or directory
|          |                     No such file or directory
|          Calculating task graph as no cached configuration is available for tasks: loggedExec
|          Could not read error output of command 'ls'.
|          java.io.IOException: Stream Closed
|          	at java.base/java.io.FileOutputStream.writeBytes(Native Method)
|          	at java.base/java.io.FileOutputStream.write(FileOutputStream.java:349)
|          	at org.elasticsearch.gradle.LazyFileOutputStream.write(LazyFileOutputStream.java:58)
|          	at org.gradle.process.internal.streams.ExecOutputHandleRunner.writeBuffer(ExecOutputHandleRunner.java:97)
|          	at org.gradle.process.internal.streams.ExecOutputHandleRunner.lambda$forwardContent$0(ExecOutputHandleRunner.java:81)
|          	at org.gradle.internal.operations.CurrentBuildOperationRef.with(CurrentBuildOperationRef.java:75)
|          	at org.gradle.process.internal.streams.ExecOutputHandleRunner.forwardContent(ExecOutputHandleRunner.java:80)
|          	at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:64)
|          	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
|          	at org.gradle.internal.concurrent.AbstractManagedExecutor$1.run(AbstractManagedExecutor.java:48)
|          	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
|          	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
|          	at java.base/java.lang.Thread.run(Thread.java:833)
|           
|          > Task :loggedExec FAILED
|          Output for ls:
|          ls: 
|           
|          FAILURE: Build failed with an exception.
|           
|          * What went wrong:
|          Execution failed for task ':loggedExec'.
|          > Process 'ls [wtf]' finished with non-zero exit value 2
|           
|          * Try:
|          > Run with --stacktrace option to get the stack trace.
|          > Run with --info or --debug option to get more log output.
|          > Run with --scan to get full insights.
|          > Get more help at https://help.gradle.org.
|           
|          BUILD FAILED in 489ms
|          1 actionable task: 1 executed
|          Configuration cache entry stored.
Calculating task graph as no cached configuration is available for tasks: loggedExec
Could not read error output of command 'ls'.
java.io.IOException: Stream Closed
	at java.base/java.io.FileOutputStream.writeBytes(Native Method)
	at java.base/java.io.FileOutputStream.write(FileOutputStream.java:349)
	at org.elasticsearch.gradle.LazyFileOutputStream.write(LazyFileOutputStream.java:58)
	at org.gradle.process.internal.streams.ExecOutputHandleRunner.writeBuffer(ExecOutputHandleRunner.java:97)
	at org.gradle.process.internal.streams.ExecOutputHandleRunner.lambda$forwardContent$0(ExecOutputHandleRunner.java:81)
	at org.gradle.internal.operations.CurrentBuildOperationRef.with(CurrentBuildOperationRef.java:75)
	at org.gradle.process.internal.streams.ExecOutputHandleRunner.forwardContent(ExecOutputHandleRunner.java:80)
	at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:64)
	at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
	at org.gradle.internal.concurrent.AbstractManagedExecutor$1.run(AbstractManagedExecutor.java:48)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:833)
 
> Task :loggedExec FAILED
Output for ls:
ls: 
 
FAILURE: Build failed with an exception.
 
* What went wrong:
Execution failed for task ':loggedExec'.
> Process 'ls [wtf]' finished with non-zero exit value 2
 
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.
 
BUILD FAILED in 489ms
1 actionable task: 1 executed
Configuration cache entry stored.

Issue Reasons:

  • [8.16] 2 failures in test failed tasks output logged to console when spooling true (6.9% fail rate in 29 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

@elasticsearchmachine elasticsearchmachine added :Delivery/Build Build or test infrastructure >test-failure Triaged test failures from CI labels Jan 3, 2025
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 8.16

Mute Reasons:

  • [8.16] 2 failures in test failed tasks output logged to console when spooling true (6.9% fail rate in 29 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Jan 3, 2025
@elasticsearchmachine elasticsearchmachine added Team:Delivery Meta label for Delivery team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Jan 3, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-delivery (Team:Delivery)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI
Projects
None yet
Development

No branches or pull requests

1 participant