Skip to content

Conversation

@northwestwitch
Copy link
Member

@northwestwitch northwestwitch commented Feb 6, 2025

This PR adds a functionality or fixes a bug.

Testing on cg-vm1 server (Clinical Genomics Stockholm)

Prepare for testing

  1. Make sure the PR is pushed and available on Docker Hub
  2. Fist book your testing time using the Pax software available at https://pax.scilifelab.se/. The resource you are going to call dibs on is scout-stage and the server is cg-vm1.
  3. ssh <USER.NAME>@cg-vm1.scilifelab.se
  4. sudo -iu hiseq.clinical
  5. ssh localhost
  6. (optional) Find out which scout branch is currently deployed on cg-vm1: podman ps
  7. Stop the service with current deployed branch: systemctl --user stop scout.target
  8. Start the scout service with the branch to test: systemctl --user start scout@<this_branch>
  9. Make sure the branch is deployed: systemctl --user status scout.target
  10. After testing is done, repeat procedure at https://pax.scilifelab.se/, which will release the allocated resource (scout-stage) to be used for testing by other users.
Testing on hasta server (Clinical Genomics Stockholm)

Prepare for testing

  1. ssh <USER.NAME>@hasta.scilifelab.se
  2. Book your testing time using the Pax software. us; paxa -u <user> -s hasta -r scout-stage. You can also use the WSGI Pax app available at https://pax.scilifelab.se/.
  3. (optional) Find out which scout branch is currently deployed on cg-vm1: conda activate S_scout; pip freeze | grep scout-browser
  4. Deploy the branch to test: bash /home/proj/production/servers/resources/hasta.scilifelab.se/update-tool-stage.sh -e S_scout -t scout -b <this_branch>
  5. Make sure the branch is deployed: us; scout --version
  6. After testing is done, repeat the paxa procedure, which will release the allocated resource (scout-stage) to be used for testing by other users.

How to test:

  1. how to test it, possibly with real cases/data

Expected outcome:
The functionality should be working
Take a screenshot and attach or copy/paste the output.

Review:

  • code approved by
  • tests executed by GitHub actions

@northwestwitch northwestwitch changed the title Updated the GitHub MongoDB action to version to 1.12 in automatic tests workflow Fix tests by pulling mongo image from ecr.aws instead of Docker Hub Feb 6, 2025
@northwestwitch northwestwitch marked this pull request as ready for review February 6, 2025 10:39
@codecov
Copy link

codecov bot commented Feb 6, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.42%. Comparing base (00dc9b1) to head (113ef90).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5220   +/-   ##
=======================================
  Coverage   84.42%   84.42%           
=======================================
  Files         327      327           
  Lines       19830    19830           
=======================================
  Hits        16741    16741           
  Misses       3089     3089           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@northwestwitch northwestwitch marked this pull request as draft February 6, 2025 13:24
@northwestwitch
Copy link
Member Author

Marking this PR as a draft. Tests are working again all of a sudden so perhaps it was a temporary hiccup in the actions. Let's see how it goes!

@northwestwitch
Copy link
Member Author

Closing this PR for now, but let's remember it exists if that problem shows up again

@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 7, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Reached our docker pull rate limit?

2 participants