Gate SingleExcitation not supported on device lightning.qubit

[JMuff22]

Issue description

Running the test for lightning.qubit device produced the following error in tests/test_execute.py

pennylane._device.DeviceError: Gate SingleExcitation not supported on device lightning.qubit

Are the tests out of date or is this a bug?

The full log from pytest can be viewed here:

test_execute.log

This is running in a singularity container and is produced everytime the tests are run.

>>> qml.about()
Name: PennyLane
Version: 0.27.0
Summary: PennyLane is a Python quantum machine learning library by Xanadu Inc.
Home-page: https://github.com/XanaduAI/pennylane
Author: 
Author-email: 
License: Apache License 2.0
Location: /LUMI_CONTAINER/env1/lib/python3.9/site-packages
Requires: appdirs, autograd, autoray, cachetools, networkx, numpy, pennylane-lightning, requests, retworkx, scipy, semantic-version, toml
Required-by: PennyLane-Lightning

Platform info:           Linux-5.3.18-150300.59.68_11.0.76-cray_shasta_c-x86_64-with-glibc2.31
Python version:          3.9.12
Numpy version:           1.24.0
Scipy version:           1.9.3
Installed devices:
- default.gaussian (PennyLane-0.27.0)
- default.mixed (PennyLane-0.27.0)
- default.qubit (PennyLane-0.27.0)
- default.qubit.autograd (PennyLane-0.27.0)
- default.qubit.jax (PennyLane-0.27.0)
- default.qubit.tf (PennyLane-0.27.0)
- default.qubit.torch (PennyLane-0.27.0)
- default.qutrit (PennyLane-0.27.0)
- null.qubit (PennyLane-0.27.0)
- lightning.qubit (PennyLane-Lightning-0.27.0)

[mlxd]

Hi @JMuff22 thanks for reporting this. I am currently unable to replicate your issue locally, or in the CI test suite. As there is a new release of PennyLane (0.28) coming tomorrow, I suggest retrying with the new release and seeing if that improves your issue.

If it still fails, feel free to add a code snippet that replicates your issue, and we can take a look. Given the proximity to the end of the year, it may be some time before we can investigate further. Thanks

[mlxd]

Hi @JMuff22 I will close this issue since I assume the problem was resolved with the above suggest. Feel free to reopen if this is not the case.