Thank you for opening a new pull request.

Before your PR can be merged it will first need to pass continuous integration tests and be reviewed. Sometimes the review process can be slow, so please be patient.

While you're waiting, please feel free to review other open PRs. While only a subset of people are authorized to approve pull requests for merging, everyone is encouraged to review open pull requests. Doing reviews helps reduce the burden on the core team and helps make the project's code better for everyone.

One or more of the following people are relevant to this code:

• @Qiskit/terra-core

All committers have signed the CLA.

Pull Request Test Coverage Report for Build 13922990398

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 9 unchanged lines in 2 files lost coverage.
• Overall coverage increased (+0.01%) to 88.074%

Totals
Change from base Build 13920468265:	0.01%
Covered Lines:	72591
Relevant Lines:	82420

💛 - Coveralls

Strange - I've agreed to the CLA but it still says 'not signed yet' here. Clicking 'recheck' here doesn't change that.

No worries - I can see you've signed it in the CLA admin panel, so I've kicked the bot to have another look at the PR. Sometimes it gets a bit stuck - I'll give it an hour or so and hopefully it'll sort itself out.

@radams78: ah, I see the problem on closer inspection. You made the commit in this PR with an email that's not associated with your @radams78 account, but actually @robin-test-stack. You'll either need to sign the CLA with that account to make the bot happy, or you need to force-push over this branch with a new commit that's associated with an email address attached to @radams78 (I'm assuming of course that you made the first commit - if it was somebody else, they need to sign the CLA).

(edit: or reassign the email addresses in GitHub if your intent is to have your chalmers.se email associated with @radams78)

Sorry about that. Done now. (How much work can it be to change one character in a comment?)

Ha, sorry that was a bit of a faff. Thanks for coming back to it.

On the plus side, at least it shouldn't be a problem again if you use either account, and that should go for any Qiskit repo - the bot aggregates license signings on any Qiskit repo that uses the CLA (which tbf is probably all of them).