Michael Stuckey
Michael Stuckey
This issue has been migrated to Azure DevOps: https://dev.azure.com/dnceng/internal/_workitems/edit/8510
@mmitche What do you think should happen here?
It's not the first time we've had questions on how Arcade handles tests. Some scenario-based docs would provide clarity.
Since we're planning to close this queue in #5509 I'm going to go ahead and close this issue.
@steveharter Just checking, what's the status with this? It hasn't identified any builds.
The YAML explicitly disables `pr` and `trigger` and only has a `schedule` section filled-out. This should be enough to have it run only on the schedule and ignore all other...
I've created fresh pipeline `dotnet-helix-service-daily-2` pointing to the same yaml so that I may compare behavior.
> Is this related to yesterday's Helix rollout? Possibly... I'm not sure how to debug this. Do you have any pointers? What is this pipeline doing?
So you suspect there was a change dnceng made that was deployed in the last rollout that broke this? (Sorry for being pedantic, I'm not seeing anything familiar or anything...
Looking at the change history... I see no changes related to either the helix client or the version of Python we install on machines. Hmm...