scriptcs-engines icon indicating copy to clipboard operation
scriptcs-engines copied to clipboard

Travis CI build

Open adamralph opened this issue 10 years ago • 5 comments
trafficstars

adamralph avatar Mar 17 '15 20:03 adamralph

I guess this has no value until Roslyn scripting is x-plat and we have some acceptance tests.

adamralph avatar Apr 05 '15 12:04 adamralph

this is valuable in a sense that we want the project to build successfully outside of windows - having the Travis CI builds will help catch issues with Path or other Mono-quirks

filipw avatar Apr 06 '15 20:04 filipw

Yep, agreed, but I've tried invoking the current roslyn scripting bits (nightly from 4th April) in Mono and it blows up immediately trying to make native calls:

[System.DllNotFoundException] clr at (wrapper managed-to-native) Microsoft.CodeAnalysis.GlobalAssemblyCache:GetCachePath (Microsoft.CodeAnalysis.GlobalAssemblyCache/ASM_CACHE,byte*,int&) at Microsoft.CodeAnalysis.GlobalAssemblyCache.GetLocation (ASM_CACHE gacId) [0x00000] in :0 at Microsoft.CodeAnalysis.GlobalAssemblyCache..cctor () [0x00000] in :0

If we set up a Travis CI build now it would probably succeed while there are no tests, but as soon as we add some it would fail. I guess there's no harm in putting it in place now. We can always switch it off later if it starts to fail and adds too much noise.

adamralph avatar Apr 06 '15 21:04 adamralph

https://github.com/dotnet/roslyn/issues/1542 On Apr 6, 2015 11:24 PM, "Adam Ralph" [email protected] wrote:

Yep, agreed, but I've tried invoking the current roslyn scripting bits (nightly from 4th April) in Mono and it blows up immediately trying to make native calls:

[System.DllNotFoundException] clr at (wrapper managed-to-native) Microsoft.CodeAnalysis.GlobalAssemblyCache:GetCachePath (Microsoft.CodeAnalysis.GlobalAssemblyCache/ASM_CACHE,byte*,int&) at Microsoft.CodeAnalysis.GlobalAssemblyCache.GetLocation (ASM_CACHE gacId) [0x00000] in :0 at Microsoft.CodeAnalysis.GlobalAssemblyCache..cctor () [0x00000] in :0

If we set up a Travis CI build now it would probably succeed while there are no tests, but as soon as we add some it would fail. I guess there's no harm in putting in place now. We can always switch it off later if it starts to fail and adds too much noise.

— Reply to this email directly or view it on GitHub https://github.com/scriptcs/scriptcs-engines/issues/7#issuecomment-90249973 .

filipw avatar Apr 07 '15 04:04 filipw

Milestone 1.1 :cry:

adamralph avatar Apr 07 '15 06:04 adamralph