Moved various language tests from AppVeyor to GitHub Actions #6300
Conversation
aardappel
force-pushed
the
master
branch
2 times, most recently
from
f44225c to
de718a5
Compare
|
@krojew looks like JS/TS not happy in this new CI, any hints what I should fix? Also curious the TS one succeeds, but looks like it shouldn't. @dbaileychess the C# one also succeeds but looks like it shouldn't |
|
@rw can't get the Go test to work, without my changes it complains about a flag that was defined that was not passed, which appears to be caused by golang/go#31859 |
|
I think JS/TS problems can be related to the discussion here: #6145 We should move away for a monolithic lib in favor of modules and transpilation. |
|
Ok, I think what I'll do is disable the failing languages for now, and they can be addressed at some future date. There is already value in the current PR in having reduced the scope of our dependence on AppVeyor (and hopefully making it run faster), giving languages their own CI, and even adding CI for languages we didn't have before. For anyone that ends up enabling CI for a particular language: make sure to remove it from the AppVeyor script if we are covering it completely. My goal is eventually to get rid of AppVeyor CI entirely. |
No description provided.