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

recreate CI - Status/Health - issue in runtime #701

Closed
sandreenko opened this issue Dec 9, 2019 · 5 comments
Closed

recreate CI - Status/Health - issue in runtime #701

sandreenko opened this issue Dec 9, 2019 · 5 comments

Comments

@sandreenko
Copy link
Contributor

@dotnet/runtime-infrastructure will we have something like https:/dotnet/coreclr/issues/27231 for the new repo?
Jobs are red again (PR testing and outerloop) and it would be nice to have an issue where you could find known failures fast.

@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label Dec 9, 2019
@trylek
Copy link
Member

trylek commented Dec 9, 2019

We definitely should; the only problem is that due to a miscommunication with GitHub the issues haven't yet been transferred to the new repo. I guess that in this particular case it's probably worth creating a new item right away as there's not yet an established date for the issue transfer and real issues are trickling in. What about just renaming this item to CI status / health and copying over the old content (you have already included the link to the old CoreCLR item)? I can easily do that, I just want to make sure we're in agreement on that.

@jaredpar
Copy link
Member

jaredpar commented Dec 9, 2019

@trylek

I will just transfer that issue individually to this repository.

@jaredpar
Copy link
Member

jaredpar commented Dec 9, 2019

Issue transfered as #702.

@sandreenko
Copy link
Contributor Author

I think that is fixed then.

@sandreenko sandreenko removed the untriaged New issue has not been triaged by the area owner label Dec 9, 2019
@sandreenko
Copy link
Contributor Author

Thanks, @trylek, @jaredpar.

@ghost ghost locked as resolved and limited conversation to collaborators Dec 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants