Windows CI still flaky (again)

[dabrahams]

https://github.com/val-lang/val/actions/runs/3990232735/attempts/1

[compnerd]

I was unable to reproduce this locally over 25 runs. I wonder if there is some sort of parallelism issue here.

[C-BJ]

I think this Issue may be closed

[C-BJ]

@kyouko-taiga

[kyouko-taiga]

Fingers crossed

[kyouko-taiga]

Seems Windows CI is still flaky :(

[C-BJ]

Can you give me a link? @kyouko-taiga

[kyouko-taiga]

Seems I can't get a link to the failed CI jobs I re-ran. I'll post a link here next time there's a Windows failure.

[C-BJ]

@kyouko-taiga

[kyouko-taiga]

I've been looking at that history but couldn't find the failure. I don't remember exactly which branch it was, I commit a lot of stuff these days.

The failure was about 3 days ago, feel free to look for yourself.

[C-BJ]

https://github.com/val-lang/val/actions/runs/4242066814/jobs/7373093947
Got it @kyouko-taiga
But anyway, things are much better now than they were before, and within acceptable limits

[kyouko-taiga]

Here's another one: https://github.com/val-lang/val/actions/runs/4272221910/attempts/1

[C-BJ]

https://github.com/val-lang/val/actions/runs/4318715802/jobs/7537341725

[C-BJ]

https://github.com/val-lang/val/actions/runs/4335819972/jobs/7570671734

https://github.com/val-lang/val/actions/runs/4335676491/jobs/7570429339

[kyouko-taiga]

Sadly, the flakiness is getting worse and starts seriously impeding development. So I decided to disable Windows CI until we can figure out a solution (see #495).

[C-BJ]

I noticed that the things happens when using Swift locally same as CI.
Swift also crashes locally.
@kyouko-taiga

[C-BJ]

I'm thinking this isn't a problem we can solve either, so what should we do?

[C-BJ]

I have an idea

[C-BJ]

Assign this issue to me?
@kyouko-taiga

[compnerd]

@C-BJ would you be able to get a stack trace or minidump from the failure? That would help understand what is going on (hitting an assert/invalid memory access).

[C-BJ]

@compnerd how? I just run a Swift command and it doesn't respond, and then it exits

[C-BJ]

#517 Need to be solved first

[compnerd]

@compnerd how? I just run a Swift command and it doesn't respond, and then it exits

If it crashes, you should be able to enable user mode dumps and collect a minidump. There are details on how to configure that at https://learn.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps.

[kyouko-taiga]

Is this thread relevant to our issue: https://github.com/orgs/community/discussions/26933

[C-BJ]

At this stage we have temporarily solved this problem by retrying. #521

[dabrahams]

I've recently reworked the CI quite substantially and uncovered/suppressed one possible cause of this problem so I'm going to close this issue until such a time as we see problems again. At that point we should file a new issue.

[dabrahams]

Well no, that wasn't the problem. Reopening until I implement the "try again" workaround.
This isn't a Hylo problem.

[dabrahams]

I implemented a lot of workarounds, and now we're all green again… for now. I only pray this is an SPM problem that will be fixed by using cmake.