Conversation
| @@ -168,39 +168,6 @@ int main(int argc, char** argv) { | |||
| }); | |||
| } | |||
|
|
|||
| // --- launch_small_kernel --- | |||
There was a problem hiding this comment.
These were duplicated before. Cleaning up.
|
/ok to test 5ecba20 |
|
@danielfrg the pre-commit is still failing: to conserve our CI resources, it'll be best if you cancel the workflow asap, because you'll need another run anyway after the pre-commit fixes. You can use To make the "CI: Enforce assignee/label/milestone on PRs" workflow happy: do you have the ability to assign a milestone? |
|
|
I believe something isn't right with my recent |
|
Cursor GPT-5.4 Extra High Fast findings (both confirmed manually):
|
This explains it: Sorry for the accident. I'm looking into applying the missing changes here, because this is the perfect test case. |
GitHub merged PR 1913 before the later local commits were pushed, so replay the recovered SPDX policy follow-ups and related license fixes here. Context: #1913 (comment) Made-with: Cursor
|
I just pushed the missing commits from PR #1913 here as one commit (i.e. missing changes squashed): f2c0838 Now the check behaves as I expected (below). I'll try to fix that next. |
The naming-rule suppressions used to live under cuda_bindings/benchmarks, so move the needed legacy-path suppressions to the relocated benchmarks/cuda_bindings pytest-legacy path and drop the stale old-path entry. Made-with: Cursor
|
@danielfrg I pushed two more commits (on top of the commit that fixed the PR #1913 accident): The first one was closely related to the PR #1913 work. The second one I jump on to be sure I want to stop here and hand this back to you. There are still the issues reported under #1948 (comment). Could you take it from here? |
Description
Follow up #1580
This one was pretty much all AI generated but seems to lgmt.
The other big change is moving the benchmark to the top level of the repo as we agreeded.
The new results still look on par:
Checklist