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

Sentiment Feedback: Reporting two issues instead of one / Detect unpredictably slow osx machine and report as infra issue #10794

Closed
net-helix bot opened this issue Sep 10, 2022 · 2 comments
Labels
Sentiment Feedback This issue is directly from user feedback from the sentiment tracking feature

Comments

@net-helix
Copy link

net-helix bot commented Sep 10, 2022

A negative sentiment was registered against feature: DeveloperWorkflowGitHubCheckTab

The PR hit one problem. The report makes it look like that there are two distinct problems. Can the reporting be update to report this as just one problem?

The problem is timeout on OSX due to macOS machines being slow in unpredictable way. I know that is that is an infrastructure issue that you are working on. Is it possible to detect that we have hit unpredictably slow osx machine and highlight it in the report as infrastructure issue?

Feedback submitted by a user that chose to remain anonymous.

Parameters

rb = 0
rt = 0
ki = 0
s = 2022-09-10T18-15-39
e = 0
ut = 0
r = dotnet/runtime
c = 4581a71ab99f
ub = 1

@net-helix net-helix bot added the Sentiment Feedback This issue is directly from user feedback from the sentiment tracking feature label Sep 10, 2022
@AlitzelMendez AlitzelMendez changed the title Sentiment Tracking #3420 Sentiment Feedback: Reporting two issues instead of one / Detect unpredictably slow osx machine and report as infra issue Sep 12, 2022
@AlitzelMendez
Copy link
Member

AlitzelMendez commented Sep 12, 2022

Unique Build Failures

dotnet-linker-tests 20220910.7 / Build OSX x64 release Runtime_Release

[:construction: Report infrastructure issue] [:page_facing_up: Report repository issue]

    [Log] The job running on agent Azure Pipelines 3 ran longer than the maximum time of 120 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134

dotnet-linker-tests 20220910.7 / Build OSX x64 release Runtime_Release / Run Trimming Tests

[:construction: Report infrastructure issue] [:page_facing_up: Report repository issue]

    [Log] The operation was canceled.

Those were the two errors; they are basically the same (there was a timeout on the job and because of this the stage failed), this is being handle in: #10614

@ChadNedzlek
Copy link
Member

This is exactly the same problem as #10614, so I'm going to close this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Sentiment Feedback This issue is directly from user feedback from the sentiment tracking feature
Projects
None yet
Development

No branches or pull requests

2 participants