Skip to content

Conversation

@haakon-e
Copy link
Member

@haakon-e haakon-e commented Nov 20, 2025

  • this enables support for Julia v1.12
  • retain JET v0.9 to support Julia v1.11

@haakon-e haakon-e force-pushed the he/ci-jet-v0-10-v0-11-in-buildkite branch from 3f18865 to ca2fc47 Compare November 20, 2025 17:39
Copy link
Member

@imreddyTeja imreddyTeja left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have you tried running ci with 1.12 yet?

@haakon-e
Copy link
Member Author

I have not run the entirety of ci, no. Perhaps we could chat about how to do this sometime?

  • I know I can update the climacommon version in .buildkite/pipeline.yml, but I don't want to mess up the precompile cache for all other runs, even if just to test running the entirety of ci on v1.12.

This proposed change is mostly motivated by wanting to make use of quality-of-life improvements in v1.12; the simulations I've been running so far have not complained.

It is impossible to precompile the .buildkite environment in v1.12 without this change, so note that this PR does not propose we upgrade ci from 1.11 to 1.12, rather it is intended for users who'd like to start working with v1.12 before a formal upgrade. I think we can upgrade the entire pipeline to v1.12 at a later time.

@imreddyTeja
Copy link
Member

I have not run the entirety of ci, no. Perhaps we could chat about how to do this sometime?

  • I know I can update the climacommon version in .buildkite/pipeline.yml, but I don't want to mess up the precompile cache for all other runs, even if just to test running the entirety of ci on v1.12.

This proposed change is mostly motivated by wanting to make use of quality-of-life improvements in v1.12; the simulations I've been running so far have not complained.

It is impossible to precompile the .buildkite environment in v1.12 without this change, so note that this PR does not propose we upgrade ci from 1.11 to 1.12, rather it is intended for users who'd like to start working with v1.12 before a formal upgrade. I think we can upgrade the entire pipeline to v1.12 at a later time.

I'm not completely confident in this, but I think precompile caches are in different folders for different Julia minor versions.
I was mainly asking about this to guess how easy adding "official" support for 1.12 will be.

@haakon-e haakon-e force-pushed the he/ci-jet-v0-10-v0-11-in-buildkite branch from ca2fc47 to f4c88b8 Compare November 25, 2025 00:52
@nefrathenrici nefrathenrici force-pushed the he/ci-jet-v0-10-v0-11-in-buildkite branch from f4c88b8 to 45b12eb Compare November 26, 2025 21:25
@haakon-e haakon-e force-pushed the he/ci-jet-v0-10-v0-11-in-buildkite branch from 45b12eb to e49ca15 Compare December 8, 2025 23:59
- this enables support for Julia v1.12
- retain JET v0.9 to support Julia v1.11
@haakon-e haakon-e force-pushed the he/ci-jet-v0-10-v0-11-in-buildkite branch from dd184a1 to ff12b9e Compare December 12, 2025 23:06
@haakon-e
Copy link
Member Author

This change is part of the following stack:

Change managed by git-spice.

@haakon-e haakon-e mentioned this pull request Dec 12, 2025
@haakon-e
Copy link
Member Author

@imreddyTeja See the stacked PR for julia v1.12 status. I propose we merge this, which keeps buildkite to 1.11, but allows developer work with 1.12, then we can keep track of #4168 and what needs to be done for 1.12.

A cursory glance at the failing tests suggests that bumping the ref counter should be sufficient. I haven't looked at how performance (SYPD) is affected.

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.

3 participants