xfail compilation test for spectroscopy schedule

Konstantin Lehmannrequested to merge
nv-xfail-spec-trigger-count into main

Explanation of changes

Three things happened when this test was written:

  1. No hardware config was given (None) and the compilation was skipped. The wrong fixture was used (fixed in this MR) and the function here did not test properly. One version (originally copy&pasted) is fixed here. For the original function, see #394.
  2. The qblox hardware config did not have the necessary instruments to execute this schedule. Fixed in this MR.
  3. The trigger_count acquisition protocol is not present yet in the qblox backend. This will be fixed in !567 (merged). For the time being, I xfail the test. @dvos2, when this MR (571) gets merged into main, please merge it back into !567 (merged), remove the xfail and test if the test passes.

Merge checklist

See also merge request guidelines

  • Merge request has been reviewed (in-depth by a knowledgeable contributor), and is approved by a project maintainer.
  • New code is covered by unit tests (or N/A).
  • New code is documented and docstrings use numpydoc format (or N/A).
  • New functionality: considered making private instead of extending public API (or N/A).
  • Public API changed: added @deprecated (or N/A).
  • Tested on hardware (or N/A).
  • CHANGELOG.md and AUTHORS.md have been updated (or N/A).
  • Windows tests in CI pipeline pass (manually triggered by maintainers before merging).

For reference, the issues workflow is described in the contribution guidelines.

Edited by Edgar Reehuis

Merge request reports