RemoteExecutor FailureTest - NOT_FOR_MERGING #43211
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
antonfirsov
added
NO-MERGE
|
I can't tell here whether there are any failing tests on supported Windows environments. |
|
I created a standalone CI build just testing the executor. Fails on Windows put Passes on Linux |
|
@JimBobSquarePants, from dotnet/arcade#6371 it seems like the issue is now understood. Do you still need this PR open, or can it be closed? Thanks. |
|
Ah sorry @stephentoub yes this should be closed. |
|
Cool, thanks. |
JimBobSquarePants
deleted the
JimBobSquarePants-RemoteExecutor-NoMerge
branch
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Exists purely to test a potentially major issue I am seeing in
RemoteExecutorfrom the dotnet/arcade repository where actions are not being invoked.dotnet/arcade#6371
Didn't know of any other way to test this so sorry for hogging build infrastructure.