Actually, no need to force-push, just restart the job.
> On Aug 31, 2023, at 2:41 PM, Julian Hyde <jhyde.apa...@gmail.com> wrote:
>
> I searched for the error message and it’s maybe a corrupted Gradle cache.
> That sounds plausible, because the message doesn’t look specific to Windows
> or your change. Just one container gone bad. I’d force-push and see whether I
> get a healthier container next run.
>
> Julian
>
> [1]
> https://stackoverflow.com/questions/65645510/cannot-access-script-base-class-org-gradle-kotlin-dsl-kotlinbuildscript
>
>
>> On Aug 31, 2023, at 9:13 AM, Tanner Clary <tannercl...@google.com.INVALID>
>> wrote:
>>
>> Hi Calcite Developers,
>>
>> I have a PR [1] that is failing the CI checks for Windows [2]. I am not
>> familiar with these errors and am wondering if anyone has any suggestions
>> on how I could fix them. Thanks so much.
>>
>> Best,
>> Tanner Clary
>>
>> [1] https://github.com/apache/calcite/pull/3391
>> [2]
>> https://github.com/apache/calcite/actions/runs/6039592258/job/16388593881
>
