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,394,312,225 | 88,907 | natecook1000 | @swift-ci Please build toolchain macOS platform | 2026-05-07T05:14:35 | 2026-05-07T05:14:35 | {} | MEMBER |
swiftlang | swift | 4,396,490,602 | 88,871 | Snowy1803 | @swift-ci smoke test macOS platform | 2026-05-07T10:57:00 | 2026-05-07T10:57:00 | {} | MEMBER |
swiftlang | swift | 4,396,686,953 | 88,689 | jamieQ | @swift-ci please smoke test | 2026-05-07T11:26:49 | 2026-05-07T11:26:49 | {} | CONTRIBUTOR |
swiftlang | swift | 4,393,073,301 | 88,900 | grynspan | Swift Testing has an issue in place to automate the process. | 2026-05-07T00:01:42 | 2026-05-07T00:01:42 | {
"rocket": 1
} | CONTRIBUTOR |
swiftlang | swift | 4,393,334,725 | 88,873 | airspeedswift | > We should probably fix the representation of invalid conformances to store a type at some point (today the invalid conformance is a singleton, literally a null pointer), since this sort of workaround has come up in several places already.
Filed https://github.com/swiftlang/swift/issues/88902 | 2026-05-07T01:08:22 | 2026-05-07T01:08:22 | {} | MEMBER |
swiftlang | swift | 4,393,627,012 | 88,904 | airspeedswift | @swift-ci please smoke test | 2026-05-07T02:04:11 | 2026-05-07T02:04:11 | {} | MEMBER |
swiftlang | swift | 4,394,122,570 | 88,903 | hnrklssn | Do I understand correctly that the ones reenabled are fine to cache because they never run before modules are unloaded? Is there any way to access this information at runtime? Part of me kinda wants to subtype `SimpleRequest` with `ClangASTNodeRequest` and have it be conditionally cached: once we know module unloading ... | 2026-05-07T04:14:45 | 2026-05-07T04:14:45 | {} | MEMBER |
swiftlang | swift | 4,394,664,754 | 88,880 | hnrklssn | That's an interesting point. Passing a pointer to an InlineArray is nice in the sense that you can't get the size wrong, but can you easily get one if your backing storage turns out to be e.g. an Array, or are you now limited to actually using an InlineArray? The main reason however is that safe interop has mostly focu... | 2026-05-07T06:33:18 | 2026-05-07T06:33:18 | {} | MEMBER |
swiftlang | swift | 4,398,234,018 | 87,177 | airspeedswift | This appears to be fixed by https://github.com/swiftlang/swift/pull/84251 | 2026-05-07T14:56:04 | 2026-05-07T14:56:04 | {} | MEMBER |
swiftlang | swift | 4,392,996,145 | 88,901 | slavapestov | Perhaps we shouldn't allow marker protocols to inherit from AnyObject, but if we decide that is okay, then existentials for those marker protocols should not self-conform. Joe also mentions that BitwiseCopyable cannot self-conform because the existential is not bitwise copyable, so we should really reconsider the rules... | 2026-05-06T23:41:07 | 2026-05-06T23:41:07 | {} | CONTRIBUTOR |
swiftlang | swift | 4,393,405,437 | 88,880 | hnrklssn | I've done some debugging and there seems to be a couple of pieces missing for macro expansion in `swift-synthesize-interface`. I'll see if I can land a fix. For `swiftc`, depending on your version you may need to pass `-enable-experimental-feature SafeInteropWrappers`. Does that make a difference here? | 2026-05-07T01:26:52 | 2026-05-07T01:26:52 | {} | MEMBER |
swiftlang | swift | 4,393,632,338 | 88,905 | j-hui | @swift-ci please test | 2026-05-07T02:05:08 | 2026-05-07T02:05:08 | {} | CONTRIBUTOR |
swiftlang | swift | 4,394,446,201 | 88,777 | eeckstein | @azarovalex Should this go into 6.4? If yes, could you open a cherry-pick PR for release/6.4.x (using the template in the description)? | 2026-05-07T05:53:40 | 2026-05-07T05:53:40 | {} | CONTRIBUTOR |
swiftlang | swift | 4,394,469,485 | 88,775 | compnerd | @swift-ci please test Windows platform | 2026-05-07T06:00:05 | 2026-05-07T06:00:05 | {} | MEMBER |
swiftlang | swift | 4,395,213,469 | 88,825 | eeckstein | @swift-ci smoke test | 2026-05-07T07:52:42 | 2026-05-07T07:52:42 | {} | CONTRIBUTOR |
swiftlang | swift | 4,395,447,821 | 87,736 | lm | Here is small Swift package which causes compiler to crash with release config.
Just running `swift build -c release` ends up with crash. Seems to me that cause is:
- generic struct with nested class
- together with `.defaultIsolation(MainActor.self)` settings within Package.swift
[compiler-crash-87736.zip](https://g... | 2026-05-07T08:26:51 | 2026-05-07T08:26:51 | {} | NONE |
swiftlang | swift | 4,396,491,315 | 88,838 | Snowy1803 | @swift-ci smoke test macOS platform | 2026-05-07T10:57:07 | 2026-05-07T10:57:07 | {} | MEMBER |
swiftlang | swift | 4,397,016,000 | 88,813 | tshortli | https://github.com/swiftlang/llvm-project/pull/12912
@swift-ci please test macOS | 2026-05-07T12:17:05 | 2026-05-07T12:17:05 | {} | CONTRIBUTOR |
swiftlang | swift | 4,398,215,105 | 67,671 | marcomasser | This works fine using the Swift 6.3.2 compiler. | 2026-05-07T14:53:38 | 2026-05-07T14:53:38 | {} | NONE |
swiftlang | swift | 4,398,305,978 | 88,919 | kovdan01 | Tagging @asl @JaapWijnen | 2026-05-07T15:04:55 | 2026-05-07T15:04:55 | {} | CONTRIBUTOR |
swiftlang | swift | 4,398,308,619 | 88,921 | kovdan01 | Tagging @asl @JaapWijnen | 2026-05-07T15:05:15 | 2026-05-07T15:05:15 | {} | CONTRIBUTOR |
swiftlang | swift | 4,393,022,474 | 83,073 | Catfish-Man | @swift-ci please test | 2026-05-06T23:48:01 | 2026-05-06T23:48:01 | {} | CONTRIBUTOR |
swiftlang | swift | 4,393,387,913 | 88,864 | hnrklssn | Thank you for the bug report, @ptoffy! Are you able to install a main snapshot (https://www.swift.org/install/macos/) and reproduce it using the latest version also? | 2026-05-07T01:22:04 | 2026-05-07T01:22:04 | {} | MEMBER |
swiftlang | swift | 4,395,415,475 | 88,173 | marcomasser | Also note:
- ✅ This issue seems to be gone when using the [development snapshot from 2026-05-04](https://download.swift.org/development/xcode/swift-DEVELOPMENT-SNAPSHOT-2026-05-04-a/swift-DEVELOPMENT-SNAPSHOT-2026-05-04-a-osx.pkg):
```
Apple Swift version 6.4-dev (LLVM 7559aa20bf50b88, Swift 4201e579bea2dd7)
```
... | 2026-05-07T08:22:18 | 2026-05-07T08:25:47 | {} | NONE |
swiftlang | swift | 4,397,471,561 | 88,826 | Jiaxu-Li | @swift-ci Please test | 2026-05-07T13:20:23 | 2026-05-07T13:20:23 | {} | NONE |
swiftlang | swift | 4,390,011,467 | 88,174 | broken-circle | Opened #88898. | 2026-05-06T16:18:45 | 2026-05-06T23:07:55 | {} | CONTRIBUTOR |
swiftlang | swift | 4,393,973,726 | 88,829 | shahmishal | @swift-ci please smoke test macos | 2026-05-07T03:29:43 | 2026-05-07T03:29:43 | {} | MEMBER |
swiftlang | swift | 4,396,452,702 | 88,911 | kovdan01 | @swift-ci Please test | 2026-05-07T10:50:53 | 2026-05-07T10:50:53 | {} | CONTRIBUTOR |
swiftlang | swift | 4,396,715,814 | 88,488 | al45tair | @swift-ci Please smoke test Windows platform | 2026-05-07T11:30:48 | 2026-05-07T11:30:48 | {} | CONTRIBUTOR |
swiftlang | swift | 4,397,903,217 | 88,917 | egorzhdan | @swift-ci please test | 2026-05-07T14:15:53 | 2026-05-07T14:15:53 | {} | CONTRIBUTOR |
swiftlang | swift | 4,392,848,331 | 88,897 | etcwilde | Let's use ~`${Python3_INTERPRETER}`~ `${Python3_EXECUTABLE}` instead of fishing it out of the target property and assigning it to a variable. Otherwise, that's a good catch. Thanks for fixing this.
Edit: Use Python3_EXECUTABLE, we haven't bumped our minimum CMake version to 3.30 yet. | 2026-05-06T23:04:25 | 2026-05-06T23:05:09 | {
"+1": 1
} | MEMBER |
swiftlang | swift | 4,392,863,820 | 88,811 | xedin | @swift-ci please test macOS platform | 2026-05-06T23:07:40 | 2026-05-06T23:07:40 | {} | CONTRIBUTOR |
swiftlang | swift | 4,393,086,058 | 88,810 | Catfish-Man | @swift-ci please test | 2026-05-07T00:05:12 | 2026-05-07T00:05:12 | {} | CONTRIBUTOR |
swiftlang | swift | 4,393,104,961 | 88,726 | jckarter | @swift-ci Please smoke test macOS | 2026-05-07T00:10:13 | 2026-05-07T00:10:13 | {} | CONTRIBUTOR |
swiftlang | swift | 4,393,107,626 | 88,894 | tshortli | @swift-ci please smoke test macOS | 2026-05-07T00:10:54 | 2026-05-07T00:10:54 | {} | CONTRIBUTOR |
swiftlang | swift | 4,393,273,951 | 88,894 | tshortli | @swift-ci please smoke test macOS | 2026-05-07T00:51:45 | 2026-05-07T00:51:45 | {} | CONTRIBUTOR |
swiftlang | swift | 4,393,797,822 | 88,342 | Catfish-Man | @swift-ci please test | 2026-05-07T02:40:37 | 2026-05-07T02:40:37 | {} | CONTRIBUTOR |
swiftlang | swift | 4,394,302,100 | 88,907 | natecook1000 | @swift-ci Please build toolchain macOS platform | 2026-05-07T05:11:26 | 2026-05-07T05:11:26 | {} | MEMBER |
swiftlang | swift | 4,394,341,138 | 88,775 | compnerd | @swift-ci please test Windows platform | 2026-05-07T05:23:08 | 2026-05-07T05:23:08 | {} | MEMBER |
swiftlang | swift | 4,395,858,193 | 88,866 | aidan-hall | @swift-ci test windows | 2026-05-07T09:25:26 | 2026-05-07T09:25:26 | {} | CONTRIBUTOR |
swiftlang | swift | 4,396,747,653 | 88,846 | AnthonyLatsis | @swift-ci please test macOS | 2026-05-07T11:35:36 | 2026-05-07T11:35:36 | {} | COLLABORATOR |
swiftlang | swift | 4,393,368,403 | 88,860 | airspeedswift | oops I forgot to push the actual fix | 2026-05-07T01:17:07 | 2026-05-07T01:17:07 | {} | MEMBER |
swiftlang | swift | 4,393,561,762 | 88,903 | j-hui | @swift-ci please smoke test | 2026-05-07T01:54:12 | 2026-05-07T01:54:12 | {} | CONTRIBUTOR |
swiftlang | swift | 4,395,379,456 | 88,909 | j-hui | @swift-ci please smoke test | 2026-05-07T08:16:58 | 2026-05-07T08:16:58 | {} | CONTRIBUTOR |
swiftlang | swift | 4,395,369,183 | 88,173 | marcomasser | > If anyone can provide a self-contained project or Swift source file that reproduces this bug, it would be very helpful.
I just ran into this issue myself and found the following minimal reproducer:
```swift
class Test<T> {}
```
That’s the whole code necessary. Just put this into a Swift package’s target that has Mai... | 2026-05-07T08:15:19 | 2026-05-07T08:26:35 | {} | NONE |
swiftlang | swift | 4,395,857,102 | 88,866 | aidan-hall | @swift-ci test macos x86 | 2026-05-07T09:25:16 | 2026-05-07T09:25:16 | {} | CONTRIBUTOR |
swiftlang | swift | 4,396,648,523 | 88,641 | hamishknight | Thank you for the PR! I should note that @kathygray-pl is also working on a fix here (#88645), apologies for not spotting this PR sooner | 2026-05-07T11:20:59 | 2026-05-07T11:21:56 | {
"+1": 1
} | CONTRIBUTOR |
swiftlang | swift | 4,396,667,840 | 88,913 | eeckstein | @swift-ci smoke test | 2026-05-07T11:24:01 | 2026-05-07T11:24:01 | {} | CONTRIBUTOR |
swiftlang | swift | 4,397,713,515 | 88,915 | eeckstein | @swift-ci test | 2026-05-07T13:52:04 | 2026-05-07T13:52:04 | {} | CONTRIBUTOR |
swiftlang | swift | 4,398,253,984 | 48,614 | marcomasser | This issue is gone in Swift 6.3.2 (and possibly earlier). | 2026-05-07T14:58:39 | 2026-05-07T14:58:39 | {} | NONE |
swiftlang | swift | 4,393,668,257 | 88,621 | hnrklssn | This required *slightly* more changes than I initially hoped, since we no longer exit early in the presence of any template specialisation in the signature, but it's still pretty small. To be safe I've run a SWB that came back clean, so the changes to the return type importing seem to be okay.
CC @Xazax-hun @DougGre... | 2026-05-07T02:11:34 | 2026-05-07T02:11:34 | {} | MEMBER |
swiftlang | swift | 4,396,651,512 | 88,683 | egorzhdan | @swift-ci please test | 2026-05-07T11:21:29 | 2026-05-07T11:21:29 | {} | CONTRIBUTOR |
swiftlang | swift | 4,397,596,588 | 88,591 | aidan-hall | Closing in favour of https://github.com/swiftlang/swift/pull/88914: a smaller more complete solution. | 2026-05-07T13:36:59 | 2026-05-07T13:36:59 | {} | CONTRIBUTOR |
swiftlang | swift | 4,397,871,766 | 88,801 | xavgru12 | Updated the example so it is more clear. This is a change that needs to happen throughout the code, not specific to a part. This originally comes from xedin, I only created the issue | 2026-05-07T14:11:48 | 2026-05-07T14:14:18 | {} | CONTRIBUTOR |
swiftlang | swift | 4,398,302,096 | 88,918 | kovdan01 | Tagging @asl @JaapWijnen | 2026-05-07T15:04:28 | 2026-05-07T15:04:28 | {} | CONTRIBUTOR |
swiftlang | swift | 4,392,840,212 | 88,892 | xedin | If this was accepted it's a miscompile because this is overload on throws vs. typed throws and that's incomparable, this was missed before and now this hole has been closed (via https://github.com/swiftlang/swift/pull/87708). Also note that when this expression is type-checked the type of the error in context is not ac... | 2026-05-06T23:02:37 | 2026-05-06T23:02:37 | {} | CONTRIBUTOR |
swiftlang | swift | 4,392,897,018 | 88,897 | etcwilde | @swift-ci please test | 2026-05-06T23:15:51 | 2026-05-06T23:15:51 | {} | MEMBER |
swiftlang | swift | 4,393,034,188 | 88,900 | lorentey | Related package manager change: https://github.com/swiftlang/swift-package-manager/pull/10032
swift-format appears to have automated this process (https://github.com/swiftlang/swift-format/pull/1199)
I expect we'll also need a similar version update in swift-testing (cc @grynspan), and possibly elsewhere (?)
| 2026-05-06T23:51:18 | 2026-05-06T23:51:18 | {} | MEMBER |
swiftlang | swift | 4,394,495,439 | 88,908 | hnrklssn | @swift-ci please smoke test | 2026-05-07T06:06:07 | 2026-05-07T06:06:07 | {} | MEMBER |
swiftlang | swift | 4,397,753,493 | 88,801 | MaxDesiatov | @xavgru12 would you be able to update PR description to provide more context? It's unclear what exactly this issue is about, which functions and areas of code it's referring to, what's the purpose of the replacement, what either of these function does, and what's the final goal to be achieved. | 2026-05-07T13:57:08 | 2026-05-07T13:57:08 | {} | CONTRIBUTOR |
swiftlang | swift | 4,392,828,907 | 88,897 | etcwilde | @compnerd, I think you broke something ~5 years ago in https://github.com/swiftlang/swift/pull/30921. :p | 2026-05-06T23:00:19 | 2026-05-06T23:00:19 | {} | MEMBER |
swiftlang | swift | 4,393,369,231 | 88,860 | airspeedswift | @swift-ci please smoke test | 2026-05-07T01:17:20 | 2026-05-07T01:17:20 | {} | MEMBER |
swiftlang | swift | 4,392,801,148 | 88,829 | airspeedswift | @swift-ci please smoke test | 2026-05-06T22:55:37 | 2026-05-07T03:28:34 | {} | MEMBER |
swiftlang | swift | 4,397,883,655 | 88,712 | charles-zablit | @swift-ci please smoke test | 2026-05-07T14:13:22 | 2026-05-07T14:13:22 | {} | CONTRIBUTOR |
swiftlang | swift | 4,392,913,833 | 88,882 | drexin | @swift-ci smoke test | 2026-05-06T23:20:00 | 2026-05-06T23:20:00 | {} | CONTRIBUTOR |
swiftlang | swift | 4,393,108,319 | 88,894 | tshortli | @swift-ci please smoke test Linux | 2026-05-07T00:11:06 | 2026-05-07T00:11:06 | {} | CONTRIBUTOR |
swiftlang | swift | 4,393,974,516 | 88,829 | shahmishal | @swift-ci please smoke test Linux | 2026-05-07T03:29:58 | 2026-05-07T03:29:58 | {} | MEMBER |
swiftlang | swift | 4,395,862,321 | 88,866 | aidan-hall | @swift-ci test macos | 2026-05-07T09:26:03 | 2026-05-07T09:26:03 | {} | CONTRIBUTOR |
swiftlang | swift | 4,397,468,406 | 88,826 | Jiaxu-Li | Thank you! I have added coverage for these cases. | 2026-05-07T13:19:57 | 2026-05-07T13:19:57 | {} | NONE |
swiftlang | swift | 4,398,298,570 | 88,865 | kovdan01 | Closing in favor of #88918 (change PR branch to allow stack of PRs) | 2026-05-07T15:04:02 | 2026-05-07T15:04:02 | {} | CONTRIBUTOR |
swiftlang | swift | 4,393,141,421 | 88,886 | tshortli | @swift-ci please test macOS | 2026-05-07T00:19:05 | 2026-05-07T00:19:05 | {} | CONTRIBUTOR |
swiftlang | swift | 4,393,795,696 | 83,073 | Catfish-Man | @swift-ci please test | 2026-05-07T02:39:57 | 2026-05-07T02:39:57 | {} | CONTRIBUTOR |
swiftlang | swift | 4,394,212,724 | 77,880 | airspeedswift | wMinimal reproducer without `Data`:
```swift
enum E: Error { case foo }
struct Holder {
mutating func withBytes<T>(_ body: (UnsafeMutableRawPointer) throws ... | 2026-05-07T04:43:33 | 2026-05-07T04:43:50 | {} | MEMBER |
swiftlang | swift | 4,397,863,543 | 87,715 | mikeash | @compnerd @rjmccall Any comments on the new version that uses the attribute? | 2026-05-07T14:10:44 | 2026-05-07T14:10:44 | {} | CONTRIBUTOR |
swiftlang | swift | 4,398,242,609 | 87,177 | airspeedswift | Please verify with 6.3 or later (I tested with latest main but 6.3 has the fix) | 2026-05-07T14:57:10 | 2026-05-07T14:57:10 | {} | MEMBER |
swiftlang | swift | 4,398,396,870 | 88,923 | artemcm | @swift-ci test | 2026-05-07T15:16:09 | 2026-05-07T15:16:09 | {} | CONTRIBUTOR |
swiftlang | swift | 4,398,711,681 | 88,904 | drexin | > Just because I'm curious: is there a reason for diagnosing this in IRGen rather than the frontend?
Because we don't know the actual size until IRGen. | 2026-05-07T15:55:20 | 2026-05-07T15:55:20 | {} | CONTRIBUTOR |
swiftlang | swift | 4,398,969,163 | 88,896 | nkcsgexi | @swift-ci please smoke test | 2026-05-07T16:25:09 | 2026-05-07T16:25:09 | {} | CONTRIBUTOR |
swiftlang | swift | 4,398,977,280 | 88,924 | mikeash | @swift-ci please test | 2026-05-07T16:26:12 | 2026-05-07T16:26:12 | {} | CONTRIBUTOR |
swiftlang | swift | 4,399,288,824 | 88,904 | airspeedswift | Updated with a runtime trap for the unspecialized case, and fixed 32-bit platforms. | 2026-05-07T17:07:14 | 2026-05-07T17:07:14 | {} | MEMBER |
swiftlang | swift | 4,399,660,059 | 88,896 | sepy97 | > Is there no test we can add to verify the fix?
I don't see how it can be tested... add all possible flags and check the binary if there is nothing after ENDBLOCK?
There is a need to prevent this failure from being silent -- I was planning on adding the assert to the writer | 2026-05-07T17:49:12 | 2026-05-07T17:49:12 | {} | CONTRIBUTOR |
swiftlang | swift | 4,400,638,326 | 88,905 | j-hui | @swift-ci please test windows platform | 2026-05-07T20:02:18 | 2026-05-07T20:02:18 | {} | CONTRIBUTOR |
swiftlang | swift | 4,401,277,040 | 86,339 | MahdiBM | @hnrklssn thank you! | 2026-05-07T21:22:22 | 2026-05-07T21:22:22 | {} | CONTRIBUTOR |
swiftlang | swift | 4,401,579,970 | 83,073 | Catfish-Man | @swift-ci please test | 2026-05-07T22:16:22 | 2026-05-07T22:16:22 | {} | CONTRIBUTOR |
swiftlang | swift | 4,401,614,952 | 87,715 | rjmccall | No, if this achieves our goals, I'm happy with it. | 2026-05-07T22:24:09 | 2026-05-07T22:24:09 | {
"+1": 1
} | CONTRIBUTOR |
swiftlang | swift | 4,401,668,273 | 86,339 | hnrklssn | Np! Note that it will still not work if there are any other explicit template instantiations in the signature - we just realised that the `std::span __noescape` _itself_ is not an issue, since it will be replaced in the macro expansion, so we managed to add support for that particular case relatively easily. Full templ... | 2026-05-07T22:36:22 | 2026-05-07T22:36:22 | {} | MEMBER |
swiftlang | swift | 4,401,916,226 | 88,788 | glessard | @swift-ci please smoke test | 2026-05-07T23:31:19 | 2026-05-07T23:31:19 | {} | CONTRIBUTOR |
swiftlang | swift | 4,401,927,584 | 87,715 | mikeash | @swift-ci please test | 2026-05-07T23:34:14 | 2026-05-07T23:34:14 | {} | CONTRIBUTOR |
swiftlang | swift | 4,402,273,991 | 88,909 | j-hui | This PR is stacked on top of https://github.com/swiftlang/swift/pull/87871 (which makes subscripts synthesized on-demand) and only adds a single commit (https://github.com/swiftlang/swift/pull/88909/commits/3821a4fce4a5f3cb9c937357a78244e151120319) | 2026-05-08T00:50:17 | 2026-05-08T00:50:17 | {} | CONTRIBUTOR |
swiftlang | swift | 4,402,740,209 | 88,788 | glessard | @swift-ci please smoke test | 2026-05-08T02:14:59 | 2026-05-08T02:14:59 | {} | CONTRIBUTOR |
swiftlang | swift | 4,403,029,630 | 88,926 | airspeedswift | @swift-ci please smoke test | 2026-05-08T03:18:03 | 2026-05-08T03:18:03 | {} | MEMBER |
swiftlang | swift | 4,398,937,489 | 88,926 | airspeedswift | @swift-ci please smoke test | 2026-05-07T16:21:06 | 2026-05-07T16:21:06 | {} | MEMBER |
swiftlang | swift | 4,399,623,307 | 88,929 | sepy97 | @swift-ci test | 2026-05-07T17:44:36 | 2026-05-07T17:44:36 | {} | CONTRIBUTOR |
swiftlang | swift | 4,400,465,456 | 88,847 | meg-gupta | @swift-ci test macOS platform | 2026-05-07T19:36:46 | 2026-05-07T19:36:46 | {} | CONTRIBUTOR |
swiftlang | swift | 4,400,735,653 | 88,896 | nkcsgexi | @swift-ci please smoke test | 2026-05-07T20:16:43 | 2026-05-07T20:16:43 | {} | CONTRIBUTOR |
swiftlang | swift | 4,401,574,220 | 88,810 | Catfish-Man | @swift-ci please smoke test Windows platform | 2026-05-07T22:15:10 | 2026-05-07T22:15:10 | {} | CONTRIBUTOR |
swiftlang | swift | 4,402,902,767 | 88,945 | j-hui | @swift-ci please smoke test | 2026-05-08T02:46:43 | 2026-05-08T02:46:43 | {} | CONTRIBUTOR |
swiftlang | swift | 4,403,161,228 | 88,946 | tshortli | @swift-ci please test | 2026-05-08T03:53:13 | 2026-05-08T03:53:13 | {} | CONTRIBUTOR |
swiftlang | swift | 4,398,435,979 | 88,884 | gottesmm | swiftlang/swift-testing#1705
@swift-ci smoke test | 2026-05-07T15:21:06 | 2026-05-07T15:21:06 | {} | CONTRIBUTOR |
swiftlang | swift | 4,398,774,756 | 88,804 | drexin | @swift-ci smoke test macos | 2026-05-07T16:02:13 | 2026-05-07T16:02:13 | {} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.