Skip to content

MLIR bazel build and test #3114

MLIR bazel build and test

MLIR bazel build and test #3114

Triggered via pull request January 21, 2024 18:19
@wsmoseswsmoses
synchronize #1618
mlirbazel
Status Failure
Total duration 22h 44m 40s
Artifacts

enzyme-mlir.yml

on: pull_request
Matrix: build-linux
Fit to window
Zoom out
Zoom in

Annotations

4 errors
MLIR Release openstack22
System.UnauthorizedAccessException: Access to the path '/home/ubuntu/actions-runner/_work/_tool' is denied. ---> System.IO.IOException: Permission denied --- End of inner exception stack trace --- at System.IO.FileSystem.CreateDirectory(String fullPath) at System.IO.Directory.CreateDirectory(String path) at GitHub.Runner.Worker.JobRunner.RunAsync(AgentJobRequestMessage message, CancellationToken jobRequestCancellationToken) at GitHub.Runner.Worker.JobRunner.RunAsync(AgentJobRequestMessage message, CancellationToken jobRequestCancellationToken) at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut) at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args)
MLIR Debug openstack22
The file '/home/ubuntu/actions-runner/_work' already exists.
MLIR Debug openstack22
System.NullReferenceException: Object reference not set to an instance of an object. at GitHub.Runner.Worker.JobRunner.CompleteJobAsync(IJobServer jobServer, IExecutionContext jobContext, AgentJobRequestMessage message, Nullable`1 taskResult) at GitHub.Runner.Worker.JobRunner.CompleteJobAsync(IRunnerService server, IExecutionContext jobContext, AgentJobRequestMessage message, Nullable`1 taskResult) at GitHub.Runner.Worker.JobRunner.RunAsync(AgentJobRequestMessage message, CancellationToken jobRequestCancellationToken) at GitHub.Runner.Worker.JobRunner.RunAsync(AgentJobRequestMessage message, CancellationToken jobRequestCancellationToken) at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut) at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args)
MLIR Debug openstack22
The self-hosted runner: github22-ci-2 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.