Bassam (Sam) Khouri comments

Results 63 comments of


                                            Bassam (Sam) Khouri

Tests: enable Swift PM tests in Windows toolchain build

Converted this PR back to draft as I want to trigger CI-builds once https://github.com/swiftlang/swift-package-manager/pull/8759 is merged to gain more confidence with this change. The cross-repository testing was successful when tested...

Tests: enable Swift PM tests in Windows toolchain build

@swift-ci smoke test

Tests: enable Swift PM tests in Windows toolchain build

@swift-ci test linux

Tests: enable Swift PM tests in Windows toolchain build

@swift-ci smoke test linux

[Windows] regression: `swift --version`, `swift build` does not output anything to console and returns immediately

cc @compnerd

[Windows] regression: `swift --version`, `swift build` does not output anything to console and returns immediately

once the issue is fixed, we will need to revert https://github.com/swiftlang/swift-docker/pull/453 to ensure the Windows docker image are no longer pinned to an "older" toolchain version

[Windows] regression: `swift --version`, `swift build` does not output anything to console and returns immediately

> I think that [#80157](https://github.com/swiftlang/swift/pull/80157) might fix the issue. Longer term, we need to figure out how to do some smoke testing for Windows with the toolchain itself. @compnerd :...

[Windows] regression: `swift --version`, `swift build` does not output anything to console and returns immediately

Just tried re-installing and it's working now.

[Windows] regression: `swift --version`, `swift build` does not output anything to console and returns immediately

Re-opening to track merging of https://github.com/swiftlang/swift-docker/pull/477

Add lock to ensure only one Swiftly process is running at any point

I encountered this also while running `swiftly update` simultaneously in two different terminal sessions. The command was installing the same toolchain version in both instances.