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

Disable zip download for azure devops download task #34032

Merged
merged 2 commits into from
Mar 24, 2020

Conversation

safern
Copy link
Member

@safern safern commented Mar 24, 2020

Workaround suggested by azure devops for: #32805

Copy link
Member

@trylek trylek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you!

eng/pipelines/common/xplat-setup.yml Outdated Show resolved Hide resolved
@ericstj
Copy link
Member

ericstj commented Mar 24, 2020

@safern
Copy link
Member Author

safern commented Mar 24, 2020

Thanks @ericstj -- should we name it as SYSTEM...? It might be case sensitive in non-windows, right?

@jaredpar
Copy link
Member

@safern

Seems easy enough to check. When not using zip download the following will be in the log file:

console.log(tl.loc("DownloadingContainerResource", artifact.resource.data));

@jaredpar
Copy link
Member

@safern

The pipelines code base uses the same variable name with different case in many places. Think it's safe to bet it's case insensitive.

@ericstj
Copy link
Member

ericstj commented Mar 24, 2020

🤷‍♂ Not sure. I don't have much experience with this codebase. https://github.com/Microsoft/azure-pipelines-task-lib/blob/master/node/docs/azure-pipelines-task-lib.md#taskgetvariable- doesn't mention case, but I found https://github.com/microsoft/azure-pipelines-task-lib/blob/554c7e64203dbd29da9403ec3a153bab74ea2386/node/internal.ts#L259 which appears to normalize to upper during this call.

@jaredpar
Copy link
Member

@safern
Copy link
Member Author

safern commented Mar 24, 2020

Seems safe then. I'll leave it as is.

Seems easy enough to check. When not using zip download the following will be in the log file:
console.log(tl.loc("DownloadingContainerResource", artifact.resource.data));

Also it seems like it worked, the localized resource in en-us is:
"loc.messages.DownloadingContainerResource": "Downloading items from container resource %s",

I see that in the build logs.

@jaredpar
Copy link
Member

Windows_NT x86 release failure is #34010

@jaredpar
Copy link
Member

jaredpar commented Mar 24, 2020

OSX failure is #34045

@jaredpar
Copy link
Member

Mono tests aren't a know issue, nor does searching turn up any failures.

@trylek
Copy link
Member

trylek commented Mar 24, 2020

Well, it claims to be a long-running test, no surprise it timed out ;-).

@safern
Copy link
Member Author

safern commented Mar 24, 2020

I'll merge, we can open an issue with runfo ?

@safern safern merged commit 1c09961 into dotnet:master Mar 24, 2020
@safern safern deleted the DisableZipDownload branch March 24, 2020 22:49
@safern
Copy link
Member Author

safern commented Mar 24, 2020

@jaredpar
Copy link
Member

I'll merge, we can open an issue with runfo ?

I checked that before my comment. Only one other failure in last 100 runs and it was another PR. Keeping an eye on that test now though.

@davidsh
Copy link
Contributor

davidsh commented Mar 26, 2020

@davidsh @scalablecory maybe the timeout for the test was a network related thing?

Not sure if we have seen this particular test hang before. @wfurt ?

Discovering: System.Net.NetworkInformation.Functional.Tests (method display = ClassAndMethod, method display options = None)
Discovered: System.Net.NetworkInformation.Functional.Tests (found 75 of 92 test cases)
Starting: System.Net.NetworkInformation.Functional.Tests (parallel test collections = on, max threads = 2)
System.Net.NetworkInformation.Functional.Tests: [Long Running Test] 'System.Net.NetworkInformation.Tests.IPInterfacePropertiesTest_Linux.IPInfoTest_IPv4Loopback_ProperAddress', Elapsed: 00:02:08
System.Net.NetworkInformation.Functional.Tests: [Long Running Test] 'System.Net.NetworkInformation.Tests.IPInterfacePropertiesTest_Linux.IPInfoTest_IPv4Loopback_ProperAddress', Elapsed: 00:04:08
System.Net.NetworkInformation.Functional.Tests: [Long Running Test] 'System.Net.NetworkInformation.Tests.IPInterfacePropertiesTest_Linux.IPInfoTest_IPv4Loopback_ProperAddress', Elapsed: 00:06:08
System.Net.NetworkInformation.Functional.Tests: [Long Running Test] 'System.Net.NetworkInformation.Tests.IPInterfacePropertiesTest_Linux.IPInfoTest_IPv4Loopback_ProperAddress', Elapsed: 00:08:08
System.Net.NetworkInformation.Functional.Tests: [Long Running Test] 'System.Net.NetworkInformation.Tests.IPInterfacePropertiesTest_Linux.IPInfoTest_IPv4Loopback_ProperAddress', Elapsed: 00:10:08
System.Net.NetworkInformation.Functional.Tests: [Long Running Test] 'System.Net.NetworkInformation.Tests.IPInterfacePropertiesTest_Linux.IPInfoTest_IPv4Loopback_ProperAddress', Elapsed: 00:12:08
System.Net.NetworkInformation.Functional.Tests: [Long Running Test] 'System.Net.NetworkInformation.Tests.IPInterfacePropertiesTest_Linux.IPInfoTest_IPv4Loopback_ProperAddress', Elapsed: 00:14:08

@wfurt
Copy link
Member

wfurt commented Mar 26, 2020

no, I have not seen this one @davidsh but the the failure was on Mono runtime. (and we do not have that much experience with it yet)
The test is pretty trivial (GetAllNetworkInterfaces) but online most other tests it does use LINQ.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants