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

Use dedicated hardware and run existing smoke tests #30

Merged
merged 2 commits into from
Jun 13, 2024
Merged

Conversation

jpineda3
Copy link
Collaborator

Pull Request Description

Fixed issues with using dedicated Jenkins agent and can not run existing smoke tests on all three precision boards in test harness.

PR Type

  • Bug fix (change that fixes an issue)
  • New feature (change that adds new functionality)
  • Breaking change (has dependencies in other repos or will cause CI to fail)

PR Checklist

  • I have performed a self-review of the changes
  • I have commented my code, at least hard-to-understand parts
  • I have build all projects affected by the changes in this PR
  • I have tested in hardware affected projects, at the relevant boards
  • I have signed off all commits from this PR
  • I have updated the documentation by running /docs/source/reference_api/gen_sysobj_doc.m script locally, if applies.

JenkinsfileHW Outdated
@@ -42,15 +44,11 @@ lock(label: 'adgt_test_harness_boards') {
harness.set_send_telemetry(false)
harness.set_log_jira(false)
harness.set_enable_resource_queuing(true)
harness.set_lock_agent(true) // Required for MATLAB toolbox tests
harness.set_lock_agent(false) // Required for MATLAB toolbox tests
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Out of curiosity, what is this change about? And do we need to update/remove the comment? Or do we indeed need the argument to be false for the MATLAB toolbox tests?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The agent lock ensures that only one container is running at a time for MATLAB toolbox pipelines. This restriction was placed because of license errors when running MATLAB on multiple containers simultaneously. But now that the agents are using a network license, somehow the restriction is no longer necessary. I removed the comment but retained the setting.

Signed-off-by: Julia Pineda <[email protected]>
@jpineda3 jpineda3 merged commit 3a846c3 into main Jun 13, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants