Pipeline fails to complete and needed to be stopped manually

[#1]

Same scenarios worked ok previous days. Today, this was result for both runs. I see today that there is an update available, but haven't tried that yet. Just documenting current failure. I am pretty sure it is a web server started by the build/test that is holding a file lock in the build directory. The stack trace appeared after the pipeline was stopped manually.

Runner version:
    current: 1.252
    latest: 1.257

...
[2021-12-06 17:23:14,510] Shutting down log uploader.
[2021-12-06 17:23:14,541] Tearing down directories.
[2021-12-06 17:23:14,791] An error occurred whilst tearing down directories.
java.nio.file.FileSystemException: C:\Users\***\runners\atlassian-bitbucket-pipelines-runner\bin\..\temp\4e53e6b2-abce-53a0-b019-26fd6e1631ee\1638809652982\build\build\build.properties: The process cannot access the file because it is being used by another process.



at java.base/sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:92)
at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:103)
at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:108)
at java.base/sun.nio.fs.WindowsFileSystemProvider.implDelete(WindowsFileSystemProvider.java:274)
at java.base/sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:105)
at java.base/java.nio.file.Files.delete(Files.java:1142)
at com.atlassian.pipelines.runner.core.directory.windows.WindowsDirectory$1.visitFile(WindowsDirectory.java:81)
at com.atlassian.pipelines.runner.core.directory.windows.WindowsDirectory$1.visitFile(WindowsDirectory.java:73)
at java.base/java.nio.file.Files.walkFileTree(Files.java:2725)
at java.base/java.nio.file.Files.walkFileTree(Files.java:2797)
at com.atlassian.pipelines.runner.core.directory.windows.WindowsDirectory.delete(WindowsDirectory.java:73)
at com.atlassian.pipelines.runner.core.runtime.TemporaryDirectoryStepRuntimeImpl.teardownDirectories(TemporaryDirectoryStepRuntimeImpl.java:61)
at io.reactivex.internal.operators.completable.CompletableFromAction.subscribeActual(CompletableFromAction.java:35)
at io.reactivex.Completable.subscribe(Completable.java:2309)
at io.reactivex.internal.operators.completable.CompletablePeek.subscribeActual(CompletablePeek.java:51)
at io.reactivex.Completable.subscribe(Completable.java:2309)
at io.reactivex.internal.operators.completable.CompletablePeek.subscribeActual(CompletablePeek.java:51)
at io.reactivex.Completable.subscribe(Completable.java:2309)
at io.reactivex.internal.operators.completable.CompletableOnErrorComplete.subscribeActual(CompletableOnErrorComplete.java:35)
at io.reactivex.Completable.subscribe(Completable.java:2309)
at io.reactivex.internal.operators.completable.CompletableMerge$CompletableMergeSubscriber.onNext(CompletableMerge.java:99)
at io.reactivex.internal.operators.completable.CompletableMerge$CompletableMergeSubscriber.onNext(CompletableMerge.java:44)
at io.reactivex.internal.operators.flowable.FlowableFromIterable$IteratorSubscription.slowPath(FlowableFromIterable.java:236)
at io.reactivex.internal.operators.flowable.FlowableFromIterable$BaseRangeSubscription.request(FlowableFromIterable.java:124)
at io.reactivex.internal.operators.completable.CompletableMerge$CompletableMergeSubscriber.innerComplete(CompletableMerge.java:176)
at io.reactivex.internal.operators.completable.CompletableMerge$CompletableMergeSubscriber$MergeInnerObserver.onComplete(CompletableMerge.java:198)
at io.reactivex.internal.operators.completable.CompletableOnErrorComplete$OnError.onComplete(CompletableOnErrorComplete.java:48)
at io.reactivex.internal.operators.completable.CompletableAndThenCompletable$NextObserver.onComplete(CompletableAndThenCompletable.java:99)
at io.reactivex.internal.operators.completable.CompletableFromRunnable.subscribeActual(CompletableFromRunnable.java:47)
at io.reactivex.Completable.subscribe(Completable.java:2309)
at io.reactivex.internal.operators.completable.CompletableAndThenCompletable$SourceObserver.onComplete(CompletableAndThenCompletable.java:67)
at io.reactivex.internal.operators.completable.CompletableAndThenCompletable$NextObserver.onComplete(CompletableAndThenCompletable.java:99)
at io.reactivex.internal.operators.completable.CompletablePeek$CompletableObserverImplementation.onComplete(CompletablePeek.java:115)
at io.reactivex.internal.operators.completable.CompletablePeek$CompletableObserverImplementation.onComplete(CompletablePeek.java:115)
at io.reactivex.internal.operators.completable.CompletableMergeIterable$MergeCompletableObserver.onComplete(CompletableMergeIterable.java:132)
at io.reactivex.internal.operators.completable.CompletableMergeIterable.subscribeActual(CompletableMergeIterable.java:94)
at io.reactivex.Completable.subscribe(Completable.java:2309)
at io.reactivex.internal.operators.completable.CompletablePeek.subscribeActual(CompletablePeek.java:51)
at io.reactivex.Completable.subscribe(Completable.java:2309)
at io.reactivex.internal.operators.completable.CompletablePeek.subscribeActual(CompletablePeek.java:51)
at io.reactivex.Completable.subscribe(Completable.java:2309)
at io.reactivex.internal.operators.completable.CompletableAndThenCompletable$SourceObserver.onComplete(CompletableAndThenCompletable.java:67)
at io.reactivex.internal.operators.completable.CompletableOnErrorComplete$OnError.onError(CompletableOnErrorComplete.java:64)
at io.reactivex.internal.operators.completable.CompletablePeek$CompletableObserverImplementation.onError(CompletablePeek.java:95)
at io.reactivex.internal.operators.completable.CompletablePeek$CompletableObserverImplementation.onError(CompletablePeek.java:95)
at io.reactivex.internal.operators.completable.CompletableObserveOn$ObserveOnCompletableObserver.run(CompletableObserveOn.java:87)
at io.reactivex.Scheduler$DisposeTask.run(Scheduler.java:608)
at io.reactivex.internal.schedulers.ScheduledRunnable.run(ScheduledRunnable.java:66)
at io.reactivex.internal.schedulers.ScheduledRunnable.call(ScheduledRunnable.java:57)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
[2021-12-06 17:23:14,791] Cancelling timeout
[2021-12-06 17:23:14,791] Step was completed with result: Result{status=COMPLETED, error=None}.
[2021-12-06 17:23:14,791] Setting runner state to not executing step.
[2021-12-06 17:23:14,791] Waiting for next step.
[2021-12-06 17:23:33,807] Updating runner state to "ONLINE".

[2021-12-06 17:24:03,807] Updating runner state to "ONLINE".
[2021-12-06 17:24:25,417] [id: 0x4e08ce73, L:/10.0.0.4:49741 - R:auth.atlassian.com/104.192.142.7:443] The connection observed an error
java.io.IOException: An existing connection was forcibly closed by the remote host

I suppose this could be the same as your known issue on Orphaned child processes?

[lliang2]

Hey @Bob Swift _Appfire_ ,

You are right, that is exactly what happen for "orphaned child processes". We are working on it at the moment, and hopefully will get it fix in these two weeks.

Cheers

Leo Liang

[v8lust]

I have similar issue on the Windows runner. We have a docker-compose test suite, which runs selenium tests, which are fine if they succeed, however, is they fail, it clears the build directory successfully, but then fails.

So I'm thinking, is there a way to stop the post-build tear-down from executing.