Skip to content

explicitly set compilation profile in tests and notebooks - #458

Merged
sgrava merged 2 commits into
mainfrom
sg/explicitly-set-compilation-profile-in-tests-and-notebooks
Aug 19, 2026
Merged

sgrava merged 2 commits into
mainfrom
sg/explicitly-set-compilation-profile-in-tests-and-notebooks

Conversation

@sgrava

@sgrava sgrava commented Aug 18, 2026

Copy link
Copy Markdown
Collaborator

Following #455

Some tests and some notebooks are implicitly relying on max_energy profile.
We can fix this here by explicitly setting the profile to be max energy.

This prevents fallout in the event of changing the default compilation strategy.

Changes

Fixed the fallout from the default change: 9 test call sites (test_program.py, test_backends_integration.py) that relied on the old implicit MAX_ENERGY default now pass it explicitly, and 7 notebooks under docs/ that relied on it now pass profile="max_energy" explicitly to keep them runnable.

@sgrava sgrava added this to the v1.4 milestone Aug 18, 2026
@sgrava sgrava linked an issue Aug 18, 2026 that may be closed by this pull request
4 tasks
@sgrava
sgrava requested a review from abussy-pasqal August 18, 2026 15:32
@github-actions

github-actions Bot commented Aug 18, 2026

Copy link
Copy Markdown
PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-08-19 06:59 UTC

@sgrava
sgrava merged commit c4b3941 into main Aug 19, 2026
16 checks passed
@sgrava
sgrava deleted the sg/explicitly-set-compilation-profile-in-tests-and-notebooks branch August 19, 2026 06:59
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.

set default compilation

2 participants