-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you!
Thanks @ericstj -- should we name it as |
Seems easy enough to check. When not using zip download the following will be in the log file:
|
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. |
🤷♂ 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. |
Seems safe then. I'll leave it as is.
Also it seems like it worked, the localized resource in en-us is: I see that in the build logs. |
Windows_NT x86 release failure is #34010 |
OSX failure is #34045 |
Mono tests aren't a know issue, nor does searching turn up any failures. |
Well, it claims to be a long-running test, no surprise it timed out ;-). |
I'll merge, we can open an issue with runfo ? |
@davidsh @scalablecory maybe the timeout for the test was a network related thing? |
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. |
Not sure if we have seen this particular test hang before. @wfurt ?
|
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) |
Workaround suggested by azure devops for: #32805