Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connection tests as CI cronjob #507

Open
callumforrester opened this issue May 7, 2024 · 3 comments
Open

Connection tests as CI cronjob #507

callumforrester opened this issue May 7, 2024 · 3 comments
Labels
enhancement New feature or request python Pull requests that update Python code

Comments

@callumforrester
Copy link
Contributor

As a developer I would like to be kept apprised of the ongoing accuracy of the system tests and hence the PV definitions on the beamline so that I can correct errors when PVs change.

Should consider how best to setup CI accounting for:

  • Keeping PVs read-only so we don't affect the beamline
  • Deciding whom to notify of specific failures
  • One big CI job or one per beamline?

Acceptance Criteria

@DominicOram
Copy link
Contributor

I think we should really try and bump this up the priority and run it on PRs too. It would have caught #480 (comment)

@stan-dot stan-dot added enhancement New feature or request python Pull requests that update Python code labels May 23, 2024
@stan-dot
Copy link
Contributor

bump this up the priority

in jira or on the github project?

@DominicOram
Copy link
Contributor

Wherever the core team would like to prioritise it. For MX #261 is probably a higher priority and is somewhat related so we can try and prioritise that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request python Pull requests that update Python code
Projects
None yet
Development

No branches or pull requests

3 participants