owner stringclasses 14
values | repo stringclasses 14
values | id int64 116k 4.61B | issue_number int32 1 181k | author stringlengths 1 39 | body stringlengths 1 262k | created_at timestamp[us]date 2000-06-06 02:40:44 2026-06-02 20:16:18 | updated_at timestamp[us]date 2000-06-06 02:40:44 2026-06-02 20:22:56 | reactions unknown | author_association stringclasses 5
values |
|---|---|---|---|---|---|---|---|---|---|
swiftlang | swift | 4,257,469,616 | 87,612 | ktoso | I have removed all the other workarounds to nonsending for now, to keep this PR clean. We will need to fix nonsending closures separately. | 2026-04-16T04:53:52 | 2026-04-16T04:53:52 | {} | CONTRIBUTOR |
swiftlang | swift | 4,261,076,699 | 88,465 | mattmassicotte | @swift-ci please smoke test | 2026-04-16T14:57:33 | 2026-04-16T14:57:33 | {} | CONTRIBUTOR |
swiftlang | swift | 4,261,458,568 | 88,285 | xedin | I saw this failure in other PRs as well i.e. https://ci.swift.org/job/swift-PR-macos-arm64/1315, so I think we should land this. | 2026-04-16T15:52:29 | 2026-04-16T15:52:29 | {
"+1": 1
} | CONTRIBUTOR |
swiftlang | swift | 4,253,685,162 | 88,483 | tshortli | @swift-ci please smoke test | 2026-04-15T16:19:24 | 2026-04-15T16:19:24 | {} | CONTRIBUTOR |
swiftlang | swift | 4,254,151,025 | 88,446 | tbkka | It would be nice for @aschwaighofer or @eeckstein to review this. | 2026-04-15T17:33:44 | 2026-04-15T17:33:44 | {} | CONTRIBUTOR |
swiftlang | swift | 4,254,449,320 | 88,465 | mattmassicotte | I've narrowed the crash down *slightly*. Just making the existing initializer `async` causes the crash... | 2026-04-15T18:22:56 | 2026-04-15T18:22:56 | {} | CONTRIBUTOR |
swiftlang | swift | 4,255,120,657 | 88,483 | tshortli | @swift-ci please smoke test | 2026-04-15T20:08:51 | 2026-04-15T20:08:51 | {} | CONTRIBUTOR |
swiftlang | swift | 4,255,541,140 | 88,490 | a-viv-a | @swift-ci Please test | 2026-04-15T21:16:40 | 2026-04-15T21:16:40 | {} | CONTRIBUTOR |
swiftlang | swift | 4,255,692,253 | 88,491 | DougGregor | @swift-ci please test | 2026-04-15T21:35:55 | 2026-04-15T21:35:55 | {} | MEMBER |
swiftlang | swift | 4,255,796,925 | 88,465 | ktoso | This may just be because this is in the core module which doesnt have any of the concurrency types -- move this extension into the concurrency module :) | 2026-04-15T21:45:28 | 2026-04-15T21:45:28 | {
"heart": 1
} | CONTRIBUTOR |
swiftlang | swift | 4,256,576,636 | 88,492 | jamieQ | @swift-ci please smoke test | 2026-04-16T00:35:09 | 2026-04-16T00:35:09 | {} | CONTRIBUTOR |
swiftlang | swift | 4,257,553,321 | 88,491 | DougGregor | @swift-ci please test apple silicon macOS | 2026-04-16T05:19:51 | 2026-04-16T05:19:51 | {} | MEMBER |
swiftlang | swift | 4,259,202,134 | 88,285 | jamieQ | Thank you for re-running @xedin. It seems it failed again in the same way. I can't locate the source of the failing tests to better understand what is being tested for and failing... is that accessible somehow, or is it an internal thing? I'll kick it off again, but do you think that failure could be caused by this cha... | 2026-04-16T10:11:31 | 2026-04-16T10:17:30 | {} | CONTRIBUTOR |
swiftlang | swift | 4,259,440,717 | 88,488 | al45tair | @swift-ci Please smoke test | 2026-04-16T10:52:26 | 2026-04-16T10:52:26 | {} | CONTRIBUTOR |
swiftlang | swift | 4,260,374,013 | 88,497 | allevato | @swift-ci please test | 2026-04-16T13:21:00 | 2026-04-16T13:21:00 | {} | MEMBER |
swiftlang | swift | 4,260,889,914 | 85,522 | finagolfin | Now that both trunk Android CI have been switched over to NDK 28, we can finally start putting this in. However, I notice that [the new Runtimes/ config on the Windows CI already seems to use versioned triples to build the Android stdlib](https://ci-external.swift.org/job/swift-main-windows-toolchain/2047/consoleText),... | 2026-04-16T14:33:08 | 2026-04-16T14:33:08 | {} | MEMBER |
swiftlang | swift | 4,253,673,492 | 88,470 | tshortli | > Very nice! Would this fixit also be picked up by the migrator?
Yes, see the changes to [member_import_visibility_migrate.swift](https://github.com/swiftlang/swift/pull/88470#diff-4e9429ba9eb8554fcb1c5ef25178d1434c9792290d6f46f535a8f064d34a677e). | 2026-04-15T16:17:45 | 2026-04-15T16:19:49 | {
"+1": 1
} | CONTRIBUTOR |
swiftlang | swift | 4,253,820,956 | 88,372 | j-hui | @swift-ci please smoke test windows platform | 2026-04-15T16:39:52 | 2026-04-15T16:39:52 | {} | CONTRIBUTOR |
swiftlang | swift | 4,254,074,694 | 88,341 | sepy97 | @swift-ci please smoke test macOS | 2026-04-15T17:21:38 | 2026-04-15T17:21:38 | {} | CONTRIBUTOR |
swiftlang | swift | 4,254,115,051 | 88,424 | finagolfin | OK, will do. 👍 | 2026-04-15T17:27:55 | 2026-04-15T17:27:55 | {} | MEMBER |
swiftlang | swift | 4,254,222,554 | 88,470 | tshortli | @swift-ci please test source compatibility | 2026-04-15T17:44:43 | 2026-04-15T17:44:43 | {} | CONTRIBUTOR |
swiftlang | swift | 4,255,457,782 | 88,467 | cachemeifyoucan | Remember to move this out of draft state. | 2026-04-15T21:03:40 | 2026-04-15T21:03:40 | {} | CONTRIBUTOR |
swiftlang | swift | 4,260,271,713 | 87,612 | ktoso | @swift-ci please smoke test Windows | 2026-04-16T13:04:57 | 2026-04-16T13:04:57 | {} | CONTRIBUTOR |
swiftlang | swift | 4,257,338,757 | 84,370 | ktoso | Actually still had a bug here if we were copying values from parent task the name would not be first. Fixed now | 2026-04-16T04:12:43 | 2026-04-16T04:12:43 | {} | CONTRIBUTOR |
swiftlang | swift | 4,259,242,677 | 88,285 | jamieQ | @swift-ci please test arm64 | 2026-04-16T10:18:09 | 2026-04-16T10:18:09 | {} | CONTRIBUTOR |
swiftlang | swift | 4,259,841,937 | 88,243 | carlpeto | Waiting on testing a built toolchain from this patch before closing this issue. Also we may need to cherry pick it over to release branch 6.3.x. | 2026-04-16T11:54:31 | 2026-04-16T11:54:31 | {
"heart": 1
} | CONTRIBUTOR |
swiftlang | swift | 4,260,435,654 | 88,499 | finagolfin | @swift-ci test android | 2026-04-16T13:30:32 | 2026-04-16T13:30:32 | {} | MEMBER |
swiftlang | swift | 4,260,741,682 | 88,500 | xedin | I don’t have a Windows machine but I will try to reproduce on macOS. This means that we got into a situation when isolation is set to `nonisolated(nonsending)` but the function doesn’t have the expected leading isolation parameter. | 2026-04-16T14:13:16 | 2026-04-16T14:13:16 | {} | CONTRIBUTOR |
swiftlang | swift | 4,261,500,657 | 88,503 | xedin | @swift-ci please smoke test | 2026-04-16T15:58:25 | 2026-04-16T15:58:25 | {} | CONTRIBUTOR |
swiftlang | swift | 4,254,133,078 | 88,392 | Bigcheese | https://github.com/swiftlang/llvm-project/pull/12740
@swift-ci smoke test | 2026-04-15T17:30:47 | 2026-04-15T17:30:47 | {} | CONTRIBUTOR |
swiftlang | swift | 4,254,789,432 | 88,488 | al45tair | @swift-ci Please smoke test | 2026-04-15T19:16:50 | 2026-04-15T19:16:50 | {} | CONTRIBUTOR |
swiftlang | swift | 4,255,767,403 | 88,465 | ktoso | I'll have a look | 2026-04-15T21:42:26 | 2026-04-15T21:42:26 | {} | CONTRIBUTOR |
swiftlang | swift | 4,256,615,540 | 88,495 | kavon | @swift-ci test | 2026-04-16T00:47:22 | 2026-04-16T00:47:22 | {} | MEMBER |
swiftlang | swift | 4,254,156,759 | 88,369 | mikeash | Gave the pure-IR approach another attempt and got it to a state which seems reasonably decent. Codegen is not quite as good, but probably good enough: https://github.com/swiftlang/swift/pull/88486 | 2026-04-15T17:34:38 | 2026-04-15T17:34:38 | {} | CONTRIBUTOR |
swiftlang | swift | 4,254,887,216 | 88,465 | mattmassicotte | Ok, this is now getting hard to believe. I have reduced this even further. Adding the following to the bottom of this same file produces the crash:
```
struct Wat {
init() async {
}
}
``` | 2026-04-15T19:32:46 | 2026-04-15T19:32:46 | {} | CONTRIBUTOR |
swiftlang | swift | 4,260,674,319 | 88,501 | jamieQ | @swift-ci please smoke test | 2026-04-16T14:03:19 | 2026-04-16T14:03:19 | {} | CONTRIBUTOR |
swiftlang | swift | 4,261,367,817 | 88,461 | artemcm | @swift-ci test | 2026-04-16T15:39:14 | 2026-04-16T15:39:14 | {} | CONTRIBUTOR |
swiftlang | swift | 4,254,740,584 | 88,487 | NotTheNHK | @phausler After some experimenting, this is what I’ve come up with so far. What do you think? | 2026-04-15T19:10:16 | 2026-04-15T19:10:16 | {} | CONTRIBUTOR |
swiftlang | swift | 4,256,705,622 | 88,495 | kavon | @swift-ci test | 2026-04-16T01:15:18 | 2026-04-16T01:15:18 | {} | MEMBER |
swiftlang | swift | 4,260,270,445 | 87,612 | ktoso | @swift-ci please smoke test macOS | 2026-04-16T13:04:45 | 2026-04-16T13:04:45 | {} | CONTRIBUTOR |
swiftlang | swift | 4,253,455,404 | 88,470 | nkcsgexi | Very nice! Would this fixit also be picked up by the migrator? | 2026-04-15T15:44:47 | 2026-04-15T15:44:47 | {} | CONTRIBUTOR |
swiftlang | swift | 4,253,530,215 | 87,238 | tkrajacic | @justice-adams-apple thx for your efforts! Much appreciated!
Now let's hope 6.3 also makes it 🤭 | 2026-04-15T15:55:21 | 2026-04-15T15:55:21 | {} | NONE |
swiftlang | swift | 4,254,689,276 | 88,467 | hjyamauchi | > Can you please add a test for that?
>
> The fix makes sense. How about `.pch` output from bridging header. Does that have the same problem?
Yes I think pch has the same problem. I applied it to pch as well and added a test. PTAL | 2026-04-15T19:02:02 | 2026-04-15T19:02:02 | {} | CONTRIBUTOR |
swiftlang | swift | 4,256,022,375 | 88,487 | phausler | @swift-ci please smoke test | 2026-04-15T22:23:34 | 2026-04-15T22:23:34 | {} | CONTRIBUTOR |
swiftlang | swift | 4,257,488,170 | 87,612 | ktoso | @swift-ci please smoke test linux | 2026-04-16T04:59:46 | 2026-04-16T04:59:46 | {} | CONTRIBUTOR |
swiftlang | swift | 4,257,529,857 | 88,466 | finagolfin | Since you admit we are already dumping this info on CI, I'm skeptical of the value add here: this is meant for devs who are developing locally and reporting problems, to give them a very easy way to dump all hashes from their local log?
Why can't we just tell them to run this command locally then, or `git log` in th... | 2026-04-16T05:12:35 | 2026-04-16T05:12:35 | {} | MEMBER |
swiftlang | swift | 4,254,433,059 | 88,405 | eeckstein | @swift-ci apple silicon benchmark | 2026-04-15T18:19:54 | 2026-04-15T18:19:54 | {} | CONTRIBUTOR |
swiftlang | swift | 4,254,533,000 | 85,365 | finagolfin | @enh-google's suggested fix passed the Swift compiler validation suite with no more redefinition errors, so I submitted it upstream, llvm/llvm-project#192307. | 2026-04-15T18:36:22 | 2026-04-15T18:36:22 | {} | MEMBER |
swiftlang | swift | 4,254,683,062 | 88,467 | hjyamauchi | Please test with following PR:
https://github.com/swiftlang/llvm-project/pull/12768
@swift-ci please smoke test | 2026-04-15T19:01:02 | 2026-04-15T19:01:02 | {} | CONTRIBUTOR |
swiftlang | swift | 4,254,874,528 | 87,867 | finagolfin | Another cross-repo testing check, again completely unrelated to this pull
swiftlang/swift-docker#536
@swift-ci test android | 2026-04-15T19:31:25 | 2026-04-15T19:31:25 | {} | MEMBER |
swiftlang | swift | 4,255,109,169 | 88,446 | DougGregor | @swift-ci apple silicon benchmark | 2026-04-15T20:06:49 | 2026-04-15T20:06:49 | {} | MEMBER |
swiftlang | swift | 4,255,114,742 | 88,308 | keith | @swift-ci Please smoke test | 2026-04-15T20:07:50 | 2026-04-15T20:07:50 | {} | MEMBER |
swiftlang | swift | 4,256,504,544 | 88,494 | gottesmm | @swift-ci smoke test | 2026-04-16T00:11:52 | 2026-04-16T00:11:52 | {} | CONTRIBUTOR |
swiftlang | swift | 4,259,417,623 | 88,442 | clintonpi | @swift-ci please test source compatibility | 2026-04-16T10:48:45 | 2026-04-16T10:48:45 | {} | CONTRIBUTOR |
swiftlang | swift | 4,259,836,998 | 88,243 | carlpeto | For anyone reading this later, a bit more root cause analysis. It looks like the issue is probably in `build.ps1` not in the installer build itself and it's a little more subtle than it first appears.
I built the toolchain and installer on arm64 Windows and it worked fine. My best guess is that when patching mimalloc ... | 2026-04-16T11:53:43 | 2026-04-16T11:53:43 | {} | CONTRIBUTOR |
swiftlang | swift | 4,260,515,340 | 88,469 | MaxDesiatov | macos arm64 lldb failure is unrelated and is not blocking | 2026-04-16T13:42:09 | 2026-04-16T13:42:24 | {} | CONTRIBUTOR |
swiftlang | swift | 4,253,607,696 | 88,419 | tbkka | @adrian-prantl -- Who can review this? | 2026-04-15T16:07:00 | 2026-04-15T16:07:00 | {} | CONTRIBUTOR |
swiftlang | swift | 4,255,127,014 | 87,869 | calda | Hey @rintaro, could you review the latest changes when you have a chance? Anyone else who should also review the PR? Thanks :) | 2026-04-15T20:09:57 | 2026-04-15T20:09:57 | {
"eyes": 1
} | CONTRIBUTOR |
swiftlang | swift | 4,261,348,359 | 88,205 | artemcm | https://github.com/swiftlang/swift-syntax/pull/3305
@swift-ci test macOS platform | 2026-04-16T15:36:34 | 2026-04-16T15:36:34 | {} | CONTRIBUTOR |
swiftlang | swift | 4,253,421,679 | 88,468 | compnerd | @swift-ci please test Windows platform | 2026-04-15T15:39:46 | 2026-04-15T15:39:46 | {} | MEMBER |
swiftlang | swift | 4,253,594,118 | 88,405 | tbkka | CC: @drexin for the missing IRGen capability that's driving this.
Could @eeckstein or @aidan-hall or @slavapestov give this a technical review? | 2026-04-15T16:04:55 | 2026-04-15T16:04:55 | {} | CONTRIBUTOR |
swiftlang | swift | 4,253,609,701 | 88,466 | xavgru12 | Tagging people that might be interested
@charles-zablit
@adrian-prantl
@justice-adams-apple | 2026-04-15T16:07:17 | 2026-04-15T16:07:17 | {} | CONTRIBUTOR |
swiftlang | swift | 4,255,470,751 | 85,365 | enh-google | > Do you think we can get that into the next NDK 30 beta, assuming it passes review by others too?
the ndk folks say "yes", so reopen the ndk bug and include the link to the fix, and i'll make sure it gets on their radar. | 2026-04-15T21:05:41 | 2026-04-15T21:05:41 | {
"+1": 1
} | NONE |
swiftlang | swift | 4,256,728,691 | 88,285 | jamieQ | macos arm64 tests failing on `lldb-api :: lang/swift/swiftui_formatters/TestSwiftUIFormatters.py`:
<details>
<summary>Info</summary>
16:14:11 ======================================================================
16:14:11 FAIL: test_after_dwarf_dwarfimporter (TestSwiftUIFormatters.TestCase)
16:14:11 -------... | 2026-04-16T01:23:10 | 2026-04-16T01:23:10 | {} | CONTRIBUTOR |
swiftlang | swift | 4,261,330,515 | 88,500 | Steelskin | I have a symbolized stack trace now:
```
Exception Code: 0x80000003
#0 0x00007ff632b83625 HandleAbort S:\SourceCache\llvm-project\llvm\lib\Support\Windows\Signals.inc:372:0
#1 0x00007ffc433019a9 (C:\WINDOWS\System32\ucrtbase.dll+0xc19a9)
#2 0x00007ffc432e4ad1 (C:\WINDOWS\System32\ucrtbase.dll+0xa4ad1)
#3 0x00007ffc... | 2026-04-16T15:34:21 | 2026-04-16T15:34:21 | {} | CONTRIBUTOR |
swiftlang | swift | 4,253,993,810 | 88,465 | mattmassicotte | Arg. The body of this new initializer implementation is currently crashing the compiler.
```
1. Swift version 6.4-dev (LLVM a63c015618d6123, Swift 339e8bc4595f8ce)
2. Compiling with effective version 5.10
3. While evaluating request ASTLoweringRequest(Lowering AST to SIL for module Swift)
4. While silgen visitDe... | 2026-04-15T17:08:17 | 2026-04-15T17:08:17 | {} | CONTRIBUTOR |
swiftlang | swift | 4,254,494,910 | 88,446 | eeckstein | @swift-ci apple silicon benchmark | 2026-04-15T18:30:19 | 2026-04-15T18:30:19 | {} | CONTRIBUTOR |
swiftlang | swift | 4,255,450,357 | 88,467 | hjyamauchi | Please test with following PR:
https://github.com/swiftlang/llvm-project/pull/12768
@swift-ci please smoke test | 2026-04-15T21:02:24 | 2026-04-15T21:02:24 | {} | CONTRIBUTOR |
swiftlang | swift | 4,255,175,370 | 88,433 | cachemeifyoucan | https://github.com/swiftlang/swift-driver/pull/2115
@swift-ci please smoke test | 2026-04-15T20:18:03 | 2026-04-15T20:18:03 | {} | CONTRIBUTOR |
swiftlang | swift | 4,255,768,284 | 88,465 | ktoso | @swift-ci please smoke test | 2026-04-15T21:42:31 | 2026-04-15T21:42:31 | {} | CONTRIBUTOR |
swiftlang | swift | 4,257,554,827 | 88,491 | DougGregor | @swift-ci please test arm64 macOS | 2026-04-16T05:20:17 | 2026-04-16T05:20:17 | {} | MEMBER |
swiftlang | swift | 4,258,417,246 | 88,360 | blindspotbounty | Thank you for looking and adding the test! | 2026-04-16T08:13:12 | 2026-04-16T08:13:12 | {
"+1": 1
} | NONE |
swiftlang | swift | 4,260,722,955 | 88,466 | charles-zablit | I like the idea of being able to easily reproduce a checkout.
By default, `update-checkout` prints the hashes of the commits of all repositories when it exits. The ci.swift.org bots and ci-external.swift.org bots all call update-checkout and therefore have the hash dump in their logs. I don't think adding an additio... | 2026-04-16T14:10:33 | 2026-04-16T14:11:36 | {} | CONTRIBUTOR |
swiftlang | swift | 4,261,370,233 | 88,464 | artemcm | @swift-ci test | 2026-04-16T15:39:35 | 2026-04-16T15:39:35 | {} | CONTRIBUTOR |
swiftlang | swift | 4,261,421,604 | 88,491 | DougGregor | arm64 macOS failure is an unrelated LLDB issue | 2026-04-16T15:46:53 | 2026-04-16T15:46:53 | {} | MEMBER |
swiftlang | swift | 4,339,487,356 | 88,721 | invalidname | @swift-ci please test | 2026-04-28T22:19:05 | 2026-04-28T22:19:05 | {} | CONTRIBUTOR |
swiftlang | swift | 4,340,300,782 | 86,082 | Bryce-MW | @swift-ci please smoke test | 2026-04-29T01:49:58 | 2026-04-29T01:49:58 | {} | CONTRIBUTOR |
swiftlang | swift | 4,346,058,002 | 88,632 | carlpeto | @swift-ci please smoke test linux platform | 2026-04-29T17:35:04 | 2026-04-29T17:35:04 | {} | CONTRIBUTOR |
swiftlang | swift | 4,346,880,540 | 88,621 | hnrklssn | @swift-ci please smoke test | 2026-04-29T19:29:59 | 2026-04-29T19:29:59 | {} | MEMBER |
swiftlang | swift | 4,346,999,409 | 88,731 | gottesmm | @Brett-Best I believe this is already fixed. Can you try with the newest swift snapshot? | 2026-04-29T19:48:18 | 2026-04-29T19:48:18 | {} | CONTRIBUTOR |
swiftlang | swift | 4,347,566,598 | 88,727 | j-hui | @nkcsgexi a couple of reasons: (1) some of these requests are specific to C++ interop features (many were added specifically for C++ interop), so they would not be used when C++ interop is disabled; (2) C++ interop causes many more types to be imported, so the chance of a memory address being reused for a Clang node is... | 2026-04-29T21:15:59 | 2026-04-29T21:15:59 | {
"+1": 1
} | CONTRIBUTOR |
swiftlang | swift | 4,347,606,441 | 88,730 | jamieQ | @swift-ci please smoke test | 2026-04-29T21:23:17 | 2026-04-29T21:23:17 | {} | CONTRIBUTOR |
swiftlang | swift | 4,347,644,728 | 88,725 | MaxDesiatov | Verified that the test crashes without the fix in https://ci.swift.org/job/swift-PR-Linux-smoke-test/27272:
```
18:27:32 # executed command: /home/build-user/swift/utils/wasm-run.py /home/build-user/build/buildbot_linux/wasistdlib-linux-x86_64/test-wasi-wasm32/stdlib/Output/KeyPath32Bit.swift.tmp/a.out
18:27:32 ... | 2026-04-29T21:30:31 | 2026-04-29T21:30:31 | {} | CONTRIBUTOR |
swiftlang | swift | 4,339,308,263 | 88,480 | slavapestov | https://github.com/swiftwasm/WasmKit/pull/341
@swift-ci Please smoke test | 2026-04-28T21:43:42 | 2026-04-28T21:43:42 | {} | CONTRIBUTOR |
swiftlang | swift | 4,341,964,614 | 88,480 | MaxDesiatov | I tagged a new release of WasmKit that includes the necessary change if you'd like to bump checkout JSON https://github.com/swiftwasm/WasmKit/releases/tag/0.2.2 | 2026-04-29T08:15:42 | 2026-04-29T08:15:42 | {} | CONTRIBUTOR |
swiftlang | swift | 4,342,673,351 | 88,724 | NotTheNHK | @xedin I’ve always wondered why we only dynamically infer global actor isolation for closures. I assume it’s to allow for better type compatibility?
Do you think we currently have the tools to make the second example (actor instance) work? I think that one would be tricky to solve. | 2026-04-29T09:58:41 | 2026-04-29T09:58:41 | {} | CONTRIBUTOR |
swiftlang | swift | 4,343,982,539 | 88,729 | meg-gupta | @swift-ci test macOS platform | 2026-04-29T13:15:05 | 2026-04-29T13:15:05 | {} | CONTRIBUTOR |
swiftlang | swift | 4,347,211,925 | 88,698 | DougGregor | For reference, floating point parsing was reimplemented in https://github.com/swiftlang/swift/pull/85797 | 2026-04-29T20:15:17 | 2026-04-29T20:15:17 | {} | MEMBER |
swiftlang | swift | 4,339,936,004 | 88,726 | jckarter | @swift-ci Please test | 2026-04-28T23:58:10 | 2026-04-28T23:58:10 | {} | CONTRIBUTOR |
swiftlang | swift | 4,340,265,034 | 75,354 | daveinglis | https://github.com/swiftlang/swift-build/pull/1251
@swift-ci test macos | 2026-04-29T01:37:38 | 2026-04-29T01:37:38 | {} | CONTRIBUTOR |
swiftlang | swift | 4,342,498,921 | 88,205 | artemcm | https://github.com/swiftlang/swift-syntax/pull/3305
@swift-ci smoke test | 2026-04-29T09:39:46 | 2026-04-29T09:39:46 | {} | CONTRIBUTOR |
swiftlang | swift | 4,347,294,566 | 88,722 | DougGregor | @swift-ci please smoke test Windows | 2026-04-29T20:29:06 | 2026-04-29T20:29:06 | {} | MEMBER |
swiftlang | swift | 4,339,838,484 | 88,725 | MaxDesiatov | @swift-ci smoke test | 2026-04-28T23:33:27 | 2026-04-28T23:33:27 | {} | CONTRIBUTOR |
swiftlang | swift | 4,340,240,204 | 88,722 | DougGregor | @swift-ci please test | 2026-04-29T01:29:03 | 2026-04-29T01:29:03 | {} | MEMBER |
swiftlang | swift | 4,345,897,139 | 88,715 | hjyamauchi | Done. | 2026-04-29T17:10:52 | 2026-04-29T17:10:52 | {} | CONTRIBUTOR |
swiftlang | swift | 4,340,262,737 | 75,354 | daveinglis | @swift-ci test macos | 2026-04-29T01:36:53 | 2026-04-29T01:36:53 | {} | CONTRIBUTOR |
swiftlang | swift | 4,343,778,296 | 88,724 | jamieQ | Hmm... yeah, it seems like this should probably work given that it does for non-function-type non-sendable values (and also does for nonisolated closures). It's not clear to me how `Sendable` inference is supposed to work for closures that are also inferred to be global-actor-isolated... should they also be inferred as... | 2026-04-29T12:46:13 | 2026-04-29T12:46:13 | {} | CONTRIBUTOR |
swiftlang | swift | 4,346,578,330 | 88,720 | meg-gupta | Failed due to a timed out lldb test, trying again | 2026-04-29T18:45:40 | 2026-04-29T18:45:40 | {} | CONTRIBUTOR |
swiftlang | swift | 4,347,567,078 | 88,727 | j-hui | @swift-ci please test | 2026-04-29T21:16:04 | 2026-04-29T21:16:04 | {} | CONTRIBUTOR |
swiftlang | swift | 4,339,335,355 | 88,718 | xedin | @swift-ci please test | 2026-04-28T21:48:43 | 2026-04-28T21:48:43 | {} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.