Merge release candidate copy into master #708
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ack to default.qubit (#689) * Initial commit. * Update changelog * Auto update version * trigger ci * Unused import. * Auto update version * trigger ci * Fix imports. * Auto update version * Fix LightningException * make format * Auto update version from '0.36.0-dev34' to '0.36.0-dev35' * Auto update version from '0.36.0-dev35' to '0.36.0-dev36' * Auto update version from '0.36.0-dev36' to '0.36.0-dev37' * Make python -m pip install consistent. * Fix ImportError * Auto update version from '0.36.0-dev37' to '0.36.0-dev38' * --force-reinstall * Auto update version from '0.36.0-dev38' to '0.36.0-dev39' * Remove --force-reinstall * Auto update version from '0.36.0-dev39' to '0.36.0-dev40' * Auto update version from '0.36.0-dev42' to '0.36.0-dev43' * Auto update version from '0.36.0-dev43' to '0.36.0-dev44' * Spec CMAKE_CXX_COMPILER * Fix quotes. * Remove quotes * Hardcode g++-11 * use env.COMPILER * which g++ * Revert * Downgrade pip * Pin libomp. * Revert wheel_linux * Upload artifacts. * Comment upload trigger * Install pip==23 * Revert libomp * try testing outside cibuildwheel * yum install devtools * yum install devtools * Do not install python * Revert changes * Don't editable install. * Not edit install * Not edit install * Fix cov path * Explicit mcm tests path * Fix qml.QuantumFunctionError error messages. --------- Co-authored-by: Dev version update bot <github-actions[bot]@users.noreply.github.com> Co-authored-by: ringo-but-quantum <[email protected]> Co-authored-by: AmintorDusko <[email protected]>
* Try update lightning CI paths
* Auto update version
* Update kokkos tests to trigger on changes to pl core
* Auto update version
* Split tests_linux.yml into cpp/python.
* Auto update version from '0.36.0-dev36' to '0.36.0-dev38'
* Split GPU tests into cpp/python.
* Split MPI-GPU tests into cpp/python.
* Fix LGPU triggers.
* Remove python tests from LGPU-C++.
* Remove upload-to-codecov-linux-cpp from LGPUMPI tests.
* Rename test workflows.
* Update changelog.
* Change group names.
* Use paths-ignore to simplify workflow paths
* Auto update version from '0.36.0-dev38' to '0.36.0-dev39'
* Fix test names.
* you may only define one of `paths` and `paths-ignore` for a single event
* Fix formatting
* Auto update version from '0.36.0-dev39' to '0.36.0-dev40'
* Change to paths-ignore in no-bin tests.
* Auto update version from '0.36.0-dev40' to '0.36.0-dev41'
* trigger ci
* Change error message.
* Split build/test jobs.
* Revert pennylane_lightning/lightning_kokkos/lightning_kokkos.py
* Fix setup.py command
* Comment workflows
* Comment pull_request:
* Copy wheels to github.workspace /wheels
* SKIP_COMPILATION=True
* Revert SKIP_COMPILATION=True
* Remove duplicate python actions.
* Split LQ-test into 5 groups.
* Update requirements-dev.txt
* 2 groups
* 1 group
* 7 groups
* Refactor LKokos tests
* Auto update version from '0.36.0-dev42' to '0.36.0-dev43'
* Fix cache id
* Fix needs
* Remove all builds
* put back CMAKE_PREFIX_PATH
* install fake lightning
* Fix compat paths
* Auto update version from '0.36.0-dev42' to '0.36.0-dev43'
* Revert changes.
* Update changelog
* trigger ci
* build_and_cache_Kokkos_linux.yml not concurrent.
* Remove C++ tests from compat tests (skipped anyways).
* Use ${{ github.ref }}-${{ github.event }}-${{ inputs.lightning-version }}-${{ inputs.pennylane-version }} for concurrency groups.
* PL_BACKEND: ${{ matrix.pl_backend }}
* Update changelog
* Install wheel package.
* Auto update version from '0.36.0-dev43' to '0.36.0-dev44'
* Install scipy wheel in one place.
* Comment job triggers.
* Add LK[cpu] est durations.
* trigger ci
* Use sha independent keys.
* trigger ci
* build_and_cache_Kokkos
* Change LK keys
* ls -l
* Install version nonce
* Do not skip comp.
* Trade ref for sha in key
* Install after PL
* ref ==> sha
* Reorder
* Try LQ workflows.
* Use actions/setup-python
* Revert triggers.
* Provide correct cov path.
* Revert pennylane_lightning/core/src/utils/config.h
* LK uses 5 groups.
* Restore wheels to main
* main/wheels
* Revert cache paths
* Fix ls -l
* fail-on-cache-miss: true
* Introduce env.GITHUB_WORKSPACE
* Use artifacts
* Fix paths
* No ls -l
* Download to github.workspace
* fix wheel name
* WHEEL_NAME
* Add blas.
* Use outputs.
* Send wheel name
* Fix artifact name
* Fix name
* Use WHEEL_NAME var
* artifacts kokkos
* fix wheel name
* Restore bins.
* Clean up
* Split Linux CPU python tests into 2.
* Fix compat workflows.
* Split format and tidy workflows.
* fix lkcpu
* fix concurrency group
* Do not use editable installs.
* Split full kokkos tests except unitary_correct
* Upload LK test durations.
* duration-paths
* Unique test_durations
* Unique test_durations
* Unique test_durations
* Fix path
* Update python_lightning_kokkos_test_durations
* Remove obsolete all and SERIAL tests.
* Update changelog
* Creating the `LightningTensor` device class based on the new API (#671)
* empty commit (triggering CI)
* Auto update version
* Definition of the two front-end classes
* adding the `lightning_tensor` string to the supported backends in `setup.py`
* adding `__init__.py` file to directly import the `lightning_tensor` device class
* re-naming file
* Auto update version
* Creating the first prototype of initial MPS state tensor using `quimb`
* providing the `backend`, `method` parameters and making `wires` optional
* Changing names and structure
* Auto update version
* adding method required by the new device API design
* Auto update version
* using the `kwargs` parameter in `LightningTensor` and `CircuitMPS` in `quimb`
* taking some further inputs from the new device API
* Perhaps decided the overall structure of `LIghtningTensor`
* Auto update version
* adding docs to methods
* temporary changes so that `pylint` does not complain at this stage
* running `isort`
* re-running formatter after `isort`
* re-running formatter after `isort`
* Applying suggested formatting change from CI
* adding tmp unit tests
* Adding `quimb` in `requirements.txt`
* runing `isort` on mps test
* removing `quimb` from requirement and deleting unit tests for `lightning.tensor`
* Auto update version
* re-inserting unit tests with an additional `yml` file
* running isort on quimb test
* changing name of yml file
* preventing error in import
* updating yml file
* inserting `quimb` package in requirements-dev
* strange error with `quimb`
* strange error with `quimb`
* specifying scipy version
* removing installation of scipy from yml file
* removing the new `yml` file
* testing if tests are tested
* Covering all lines in tests
* forgot final line for formatter
* Python formatter on CI complaints
* covering missing lines
* formatter on CI complaints
* Trying not to skip test if Cpp is enabled
* skipping tests if Cpp is enabled
* removing the only line not covered by tests so far
* Auto update version
* Applying suggestions from code review and making the `state` attribute private (new API design)
* Python formatter
* removing params from `QuimbMPS`
* Auto update version
* removing `**kwargs` from `QuimbMPS`
* removing unnecessary param at this stage
* covering test line
* formatter...
* removing param description
* Making `pylint` happy
* forgot new arg in test
* Updating base class and `preprocess` function
* Updating `LightningTensor` class with new names from more advanced PR
* Auto update version
* Auto update version
* Triggering CI
* Auto update version
* Trying to remove pin from `quimb` in `requirements.dev`
* Auto update version
* Auto update version
* Removing infos on derivatives and using config options to pass parameters to interface
* Usual `pylint` failures
* Trying to solve formatting errors
* typo in docstring
* Sunday update: improved docstrings and structure
* Removing method that was supposed to be in next PR
* removing old TODO comment
* Removing changes from the `setup.py` file
* restoring previous format to `setup.py`
* Auto update version from '0.36.0-dev34' to '0.36.0-dev41'
* Auto update version from '0.36.0-dev40' to '0.36.0-dev41'
* Removing kwargs as suggested from code review
* Addressing comments from CR
* Skipping tests if CPP binary is available
* Auto update version from '0.36.0-dev42' to '0.36.0-dev43'
* Auto update version from '0.36.0-dev43' to '0.36.0-dev44'
* Restoring name in changelog (?)
* Increasing time limit for Python tests
* Applying suggestions from code review
---------
Co-authored-by: Dev version update bot <github-actions[bot]@users.noreply.github.com>
Co-authored-by: ringo-but-quantum <[email protected]>
* Increase tolerance for a flaky test (test_single_return_value) (#703)
* update dev version
* increase tolerance
* update changelog
* trigger CIs
* Auto update version from '0.36.0-dev44' to '0.36.0-dev45'
---------
Co-authored-by: ringo-but-quantum <[email protected]>
* Auto update version from '0.36.0-dev45' to '0.36.0-dev46'
* Remove LTensor stuff
* Update changelog
* Revert requirements-dev.txt
* trigger ci
* Update python_lightning_kokkos_test_durations
* Restore 'all' tests in tests_lkcuda_python.yml
* Fix durations paths.
* Try --splitting-algorithm=least_duration
* Try no -n auto lkcpu tests
* One last test.
---------
Co-authored-by: Rashid N H M <[email protected]>
Co-authored-by: Dev version update bot <github-actions[bot]@users.noreply.github.com>
Co-authored-by: ringo-but-quantum <[email protected]>
Co-authored-by: Pietropaolo Frisoni <[email protected]>
Co-authored-by: Amintor Dusko <[email protected]>
* use map wires instead of map_to_standard_wires * oops * Update .github/CHANGELOG.md * black * Trigger CIs * add test * black on tests * Update .github/CHANGELOG.md --------- Co-authored-by: AmintorDusko <[email protected]> Co-authored-by: Ali Asadi <[email protected]>
|
This will be done later deliberately. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before submitting
Please complete the following checklist when submitting a PR:
All new features must include a unit test.
If you've fixed a bug or added code that should be tested, add a test to the
testsdirectory!All new functions and code must be clearly commented and documented.
If you do make documentation changes, make sure that the docs build and
render correctly by running
make docs.Ensure that the test suite passes, by running
make test.Add a new entry to the
.github/CHANGELOG.mdfile, summarizing thechange, and including a link back to the PR.
Ensure that code is properly formatted by running
make format.When all the above are checked, delete everything above the dashed
line and fill in the pull request template.
Context:
Description of the Change:
Benefits:
Possible Drawbacks:
Related GitHub Issues: