Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: 11/06/24 upstream sync #131

Merged
merged 111 commits into from
Nov 12, 2024
Merged

CI: 11/06/24 upstream sync #131

merged 111 commits into from
Nov 12, 2024

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented Nov 6, 2024

Daily sync with upstream

Jake VanderPlas and others added 30 commits October 30, 2024 15:13
…ble with NumPy.

Previously, this change did not account for that fact that `device_get` may be called on objects that have a non-NumPy-compatible `dtype` attribute, such as tensorflow tensors. This change adds new dtype handling aimed at being robust to this case.

Reverts 2bed1e8

PiperOrigin-RevId: 691568933
…kind is `TPU v5`.

PiperOrigin-RevId: 691586791
Part of a plan to move away from our "abstract value" lattice to more traditional types.

PiperOrigin-RevId: 691626481
…batching and simple transposition.

PiperOrigin-RevId: 691706218
… commits SMEM

Users are expected to call `pltpu.commit_smem` manually instead.

PiperOrigin-RevId: 691724662
Also start moving the existing C++ tests to Python.

PiperOrigin-RevId: 691729887
PiperOrigin-RevId: 691830491
PiperOrigin-RevId: 691843537
These APIs were all removed 3 or more months ago, and the registrations
here cause them to raise informative AttributeErrors. Enough time has
passed now that we can remove these.
PiperOrigin-RevId: 691972341
… ir.Context's __init__.

mlir.ir.Context has the unfortunate behavior that it loads all dialects linked into the binary, even those we have no intention of using. This is fairly benign in JAX's usual configuration, but if JAX is linked together with other MLIR-using software it can be problematic.

PiperOrigin-RevId: 691984229
Also improved the corresponding test cases to ensure better coverage and accuracy.

This PR is similar to jax-ml#22283, which adds lowering for `lax.sign`.

PiperOrigin-RevId: 691988164
This is currently causing failures on main.
PiperOrigin-RevId: 693732928
Since we only wait on one semaphore, we should enforce this in the verifier.

PiperOrigin-RevId: 693770055
Surprised that we didn't test f32 dot_general on TPU (?) Even tpu_ops_test doesn't exercise it.

PiperOrigin-RevId: 693777426
@charleshofer charleshofer self-requested a review November 6, 2024 22:43
jakevdp and others added 16 commits November 12, 2024 09:53
…126)

* Rename the CI flow to 'ROCm CI' and only run it on PRs to the rocm-main branch

* Change name to 'ROCm CPU CI'
* Add file for opening PRs upstream

* Add HEAD_REF as environment variable

* Fill out code for making a new branch and opening a PR to upstream

* Add names for steps

* Fix yaml

* Fix yaml again

* Leave a comment on the old PR linking to the new one

* Add proper permissions for creating banches and opening PRs

* Fix YAML
* Checkout main before trying to switch to it

* Fix the checkout command
@charleshofer charleshofer merged commit 9afbd23 into rocm-main Nov 12, 2024
7 checks passed
@charleshofer charleshofer deleted the ci-upstream-sync-11_1 branch November 12, 2024 16:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.