l
image.png
j
Windows machine? it is annoying it only has 7gb…
Maybe if we don't have specific Windows code we can just trust external dependencies are working correctly in Windows and just test on macos and linux, what do you think @simon.vergauwen ?
s
We don’t have anything special in any platform
The only platform dependent code is AtomicRef, and expect/actual expceptions.
j
Should we just stop running windows in CI then? and just wait until GitHub add more ram?
s
Ye, that’s fine with me. Unstable CI is only causing more work. cc\\ @raulraja
r
sounds good to me as well
s
@Javier this wasn’t Windows. This is still the same issue with Gradle where it times out trying to configure itself 😞 This is a bug in the Kotlin Script Gradle code, the one I reported on Gradle Slack and Github tracker but still no response.
Disabling Windows will not make this less flaky.
j
That is annoying :/
s
Very 😞
This is the Gradle ticket that explains the issue we’re seeing @Lukasz Kalnik. https://github.com/gradle/gradle/issues/19446
👍 1
Afaik there is no workaround for this, and it’s making CI flaky 😭
j
it was triaged a few minutes ago
hope they add a workaround soon
🤞 3