-
Notifications
You must be signed in to change notification settings - Fork 847
Closed
Milestone
Description
MacOS CI run occasionally times out after 60 minutes.
Sometimes it looks like it didn't just run out of time, but got stuck in a specific moment, like this:
Test run for /Users/runner/work/1/s/artifacts/bin/FSharp.Compiler.UnitTests/Release/net8.0/FSharp.Compiler.UnitTests.dll (.NETCoreApp,Version=v8.0)
Microsoft (R) Test Execution Command Line Tool Version 17.8.0 (x64)
Copyright (c) Microsoft Corporation. All rights reserved.
Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
---------------------------------------------------------------
Executables
CSC = /Users/runner/work/1/s//.packages/Microsoft.Net.Compilers/4.3.0-1.22220.8/tools/csc.exe
BUILD_CONFIG = Release
csc_flags = /nologo
FSC = /Users/runner/work/1/s/tests/FSharp.Test.Utilities/../../artifacts/bin/fsc/Release/net8.0/fsc.dll
fsc_flags = -r:System.Core.dll --nowarn:20 --define:COMPILED --preferreduilang:en-US
FSCOREDLLPATH = /Users/runner/work/1/s/tests/FSharp.Test.Utilities/../../artifacts/bin/FSharp.Core/Release/netstandard2.0/FSharp.Core.dll
FSI = /Users/runner/work/1/s/tests/FSharp.Test.Utilities/../../artifacts/bin/fsi/Release/net8.0/fsi.dll
DotNetExe =dotnet
DOTNET_MULTILEVEL_LOOKUP = 0
DOTNET_ROOT = /Users/runner/.dotnet
FSI_FOR_SCRIPTS = /Users/runner/work/1/s/tests/FSharp.Test.Utilities/../../artifacts/bin/fsi/Release/net8.0/fsi.dll
fsi_flags = -r:System.Core.dll --nowarn:20 --define:INTERACTIVE --maxerrors:1 --abortonerror --preferreduilang:en-US
ILDASM = /Users/runner/work/1/s//.packages/runtime.osx-x64.Microsoft.NETCore.ILDAsm/5.0.0-preview.7.20364.11/runtimes/osx-x64/native/ildasm
PEVERIFY = dummy
---------------------------------------------------------------
[xUnit.net 00:00:03.01] FSharp.Compiler.UnitTests.AssemblySigning.AssemblyKeyNameAttribute DESKTOP [SKIP]
Skipped FSharp.Compiler.UnitTests.AssemblySigning.AssemblyKeyNameAttribute DESKTOP [1 ms]
[xUnit.net 00:00:10.58] FSharp.Compiler.UnitTests.AssemblySigning.--keycontainer:name DESKTOP [SKIP]
Skipped FSharp.Compiler.UnitTests.AssemblySigning.--keycontainer:name DESKTOP [1 ms]
value: "<null>"
value: "<null>"
##[error]The Operation will be canceled. The next steps may not contain expected logs.
##[error]The operation was canceled.
Finishing: Build / Test
The PR (#16877) doesn't touch any code, so most probably is not to blame here.
Maybe it's just a coincidence, or I'm not reading this right, but I've seen timeouts with logs like this in my draft here: (#16779) and they were related to a a deadlock and not just a simple timeout.
OK., you can toggle timestamps in the log above:

9 minutes apparently doing nothing before it times out.
Compare with normal MacOS timeout (happens quite often too, unfortunately):

Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Done