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

InitializeToolset flakiness in correctness builds #58199

Closed
runfoapp bot opened this issue Dec 8, 2021 · 5 comments
Closed

InitializeToolset flakiness in correctness builds #58199

runfoapp bot opened this issue Dec 8, 2021 · 5 comments
Labels
Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead
Milestone
17.4

Comments

@runfoapp
Copy link

runfoapp bot commented Dec 8, 2021 •
edited
Loading

Runfo Tracking Issue: Correctness build InitializeToolset issues

Definition Build Kind Job Name
roslyn-CI 66363 Rolling Build_Windows_Release
roslyn-CI 64144 PR 65008 Build_Windows_Debug
roslyn-CI 64144 PR 65008 Build_Windows_Debug
roslyn-CI 64144 PR 65008 Correctness_Rebuild
roslyn-CI 64144 PR 65008 Correctness_Rebuild
roslyn-CI 64144 PR 65008 Build_Windows_Release
roslyn-CI 62903 PR 64957 Test_Windows_Desktop_Debug_64
roslyn-CI 56841 Rolling Test_Windows_CoreClr_IOperation_Debug
roslyn-CI 56841 Rolling Test_Windows_Desktop_Debug_64
roslyn-CI 56841 Rolling Test_Windows_Desktop_Debug_32
roslyn-CI 56841 Rolling Test_Windows_Desktop_Debug_32
roslyn-CI 56841 Rolling Test_Windows_Desktop_Debug_32
roslyn-CI 56841 Rolling Test_Windows_Desktop_Debug_32
roslyn-CI 56841 Rolling Test_Windows_CoreClr_Debug
roslyn-CI 56841 Rolling Test_Windows_CoreClr_Debug
roslyn-CI 56316 PR 64803 Test_Windows_Desktop_Release_32
roslyn-CI 56316 PR 64803 Test_Windows_CoreClr_Release
roslyn-CI 56269 Rolling Test_Windows_CoreClr_Debug_Single_Machine
roslyn-CI 51811 Rolling Test_Windows_CoreClr_Release
roslyn-CI 39111 Rolling Source-Build (Managed)
roslyn-CI 39111 Rolling Build_Windows_Release

Build Result Summary

Day Hit Count Week Hit Count Month Hit Count
0 1 8
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead labels Dec 8, 2021
@dibarbet dibarbet changed the title Tracking issue in roslyn-ci InitializeToolset flakiness in correctness builds Dec 8, 2021
@jinujoseph jinujoseph removed the untriaged Issues and PRs which have not yet been triaged by a lead label Dec 8, 2021
@jinujoseph jinujoseph added this to the 17.1 milestone Dec 8, 2021
@jcouv jcouv modified the milestones: 17.1, 17.2 Mar 17, 2022
@jaredpar
Copy link
Member

The actual error message I see here is the following:

##error The remote name could not be resolved: 'netcorenativeassets.blob.core.windows.net'

@MattGal is this a known issue?

@MattGal
Copy link
Member

MattGal commented Mar 22, 2022

There's, at least, three different network problems going on here:

@ilyas1974 and the rest of the FR crew have seen some network flakiness issues. FR standup is starting now, I'll stop by there and discuss.

@jinujoseph jinujoseph modified the milestones: 17.2, 17.3 May 5, 2022
@allisonchou allisonchou removed their assignment Sep 7, 2022
@allisonchou allisonchou modified the milestones: 17.3, 17.4 Sep 7, 2022
@jcouv jcouv added untriaged Issues and PRs which have not yet been triaged by a lead and removed Retriage labels Oct 14, 2022
@jasonmalinowski
Copy link
Member

@jaredpar @MattGal Looks like we have this very old (almost one year!) bug tracking what might have been temporary flakiness, but it looks like we're still seeing this every so often. Is there still something needing investigation here?

@MattGal
Copy link
Member

MattGal commented Nov 2, 2022

I don't think this issue is super useful to keep open. External dependencies are going to be occasionally flaky and there are bogus results coming up on this query anyways (the 2nd one is just Helix test failures?). Since we use the publicly available installation scripts, any hardening would need to be handled by that team not DncEng anyways... however given the false positives and infrequent hits I still think this isn't worth keeping open.

@jasonmalinowski
Copy link
Member

jasonmalinowski commented Nov 2, 2022 •
edited
Loading

Alright, just wanted to confirm. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Milestone
17.4
Development

No branches or pull requests
6 participants
@jaredpar @jasonmalinowski @MattGal @jinujoseph @jcouv @allisonchou