Monitoring Tasks Notes

From Genecats
Revision as of 16:58, 24 March 2017 by Cath (talk | contribs) (Adding a page to document procedures and notes for QA monitoring tasks.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

This page is intended to document procedures and notes for various QA monitoring tasks.

Cronjob: Results from checkGbibMd5.sh

Hiram generally requests the push of vXXX gBiB Store Push push request example. This push is usually done soon after the Tuesday release of CGIs to the RR/world. However, if this push is not done before this script runs, then you may see the md5 mismatch. It is recommended to wait until the end of the week (an possibly the end of Friday following the release) to give Hiram time to do the push. Check the push request group for the latest store push. If the md5sums still do not match after the push, then let Hiram know.

The /cluster/home/qateam/bin/scripts/checkGbibMd5.sh script checks for matching 'modify' times between beta's hgTracks and RR's hgTracks:

ssh qateam@hgwbeta stat -c %y /usr/local/apache/cgi-bin/hgTracks 2017-03-20 10:31:02.000000000 -0700

ssh qateam@hgw1 stat -c %y /usr/local/apache/cgi-bin/hgTracks 2017-03-20 10:31:02.000000000 -0700

If those dates match, the md5sums are compared between the local gbibBeta with the version on the store, which should also match, but in this case they don't match.

md5sum /usr/local/apache/htdocs/gbib/gbibBeta.zip | awk '{print $1}'
14e5f65fd19ecf43af05a313f884d26c
curl -s https://genome-store.ucsc.edu/media/products/gbib.zip | md5sum | awk '{print $1}'
0a90536be4f4e2fdb3e2d865762db818