Skip to content

Adding a new ubuntu CI leg - #2516

Merged
Anipik merged 5 commits into
dotnet:masterfrom
Anipik:UbuntuCi
Feb 19, 2019
Merged

Anipik merged 5 commits into
dotnet:masterfrom
Anipik:UbuntuCi

Conversation

@Anipik

@Anipik Anipik commented Feb 12, 2019 •

Copy link
Copy Markdown
Contributor

Related To #2381

Currently we are just running the tests on centos linux. A couple of libraries dont run on centos distro but run on ubuntu so we are adding a new ci leg to increase coverafe and run these tests on ubuntu

@codecov

codecov Bot commented Feb 12, 2019 •

Copy link
Copy Markdown

Codecov Report

❗ No coverage uploaded for pull request base (master@b2587fa). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master    #2516   +/-   ##
=========================================
  Coverage          ?   71.53%           
=========================================
  Files             ?      801           
  Lines             ?   141876           
  Branches          ?    16122           
=========================================
  Hits              ?   101493           
  Misses            ?    35928           
  Partials          ?     4455
Flag Coverage Δ
#Debug 71.53% <0%> (?)
#production 67.82% <ø> (?)
#test 85.73% <0%> (?)

@Anipik Anipik changed the title [Donot review] Adding a new ubuntu CI leg Adding a new ubuntu CI leg Feb 12, 2019
Comment thread .vsts-dotnet-ci.yml Resolved
Comment thread .vsts-dotnet-ci.yml Resolved
Comment thread .vsts-dotnet-ci.yml Resolved
Comment thread src/Native/CpuMathNative/CMakeLists.txt Resolved
Comment thread .vsts-dotnet-ci.yml Resolved
Comment thread .vsts-dotnet-ci.yml Outdated
buildScript: ./build.sh
customMatrixes:
Build_Debug_Intrinsics:
_configuration: Debug-Intrinsics

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought we were going to switch to the Release to use 3.0/Intrinsics. That way we get Debug and Release coverage across both versions:

CentOS|Debug|3.0
CentOS|Release|2.1
Ubuntu|Debug|2.1
Ubuntu|Release|3.0

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry I didn't saw it correctly, I will correct it

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moving back the CI to netcoreap2.1 untill the cli people resolves the https://github.com/dotnet/cli/issues/10802

Comment thread init-tools.sh Resolved
Comment thread test/Directory.Build.props Resolved
@Anipik

Anipik commented Feb 15, 2019

Copy link
Copy Markdown
Contributor Author

@eerhardt @jignparm can you please review this one. I have addressed the feedback.

@eerhardt currently i moved back the ubuntu ci to the netcoreapp2.1.
Most probably we will have to make some changes in the build tools script in order to make the netcoreapp3.0 non-windows ci work. I will change the ci leg to netcoreapp3.0 when the buildtools changes have been done

@jignparm jignparm mentioned this pull request Feb 15, 2019
@TomFinley

Copy link
Copy Markdown
Contributor

Hi @Anipik thank you for working on this. Can't we narrow it down a little, to specific components of interest? As far as I understood there were only a few things that would be potentially problematic. It's just a little irritating to think of this 99% C# codebase getting yet another fully realized leg just to run what is really only one test of interest.

{
internal static bool CheckLibcVersionGreaterThanMinimum(double minVersion)
{
#if !NETFRAMEWORK

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why the #if here? The if (RuntimeInformation.IsOSPlatform(OSPlatform.Windows)) will catch anytime we are running on Windows, and return false.

@Anipik Anipik Feb 19, 2019 •

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason behind this is Marshal.PtrToStringUTF8 api is not available for netframework which leads to compile error

@eerhardt

Copy link
Copy Markdown
Member

Hi @Anipik thank you for working on this. Can't we narrow it down a little, to specific components of interest? As far as I understood there were only a few things that would be potentially problematic. It's just a little irritating to think of this 99% C# codebase getting yet another fully realized leg just to run what is really only one test of interest.

@TomFinley - See #2381 for the reasoning.

@eerhardt eerhardt left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@ghost ghost locked as resolved and limited conversation to collaborators Mar 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants