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.

Sign up for GitHub

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

Jump to bottom

[REGRESSION]: #20632

Closed
4 of 7 tasks
Liabaemt opened this issue Nov 8, 2024 · 0 comments
Closed
4 of 7 tasks

[REGRESSION]: #20632

Liabaemt opened this issue Nov 8, 2024 · 0 comments
Labels
bug regression This used to work, but a change in the service/tasks broke it. triage

Comments

@Liabaemt
Copy link

Liabaemt commented Nov 8, 2024

New issue checklist

Task name

No response

Breaking task version

No response

Last working task version

No response

Regression Description

A regression happened!

Environment type (Please select at least one enviroment where you face this issue)

  • Self-Hosted
  • Microsoft Hosted
  • VMSS Pool
  • Container

Azure DevOps Server type

Azure DevOps Server (Please specify exact version in the textbox below)

Azure DevOps Server Version (if applicable)

No response

Operation system

Ios

Relevant log output

Fix

Full task logs with system.debug enabled

UNSUCCESSFUL RUN 
 [REPLACE THIS WITH YOUR INFORMATION]
SUCCESSFUL RUN 
 [REPLACE THIS WITH YOUR INFORMATION]

Repro steps

No response
@Liabaemt Liabaemt added bug regression This used to work, but a change in the service/tasks broke it. labels Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug regression This used to work, but a change in the service/tasks broke it. triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@v-schhabra @Liabaemt