| 476 | |
| 477 | === Unable to access STASHmaster from branch on ARCHER === |
| 478 | |
| 479 | Some suites may reference files held in the repository for use at runtime. The most common example of this is the STASHmaster file. To make a change to the STASHmaster file requires editing the file in a branch and setting the path to this in the suite. However the method described in the instructions below will not work on ARCHER: |
| 480 | |
| 481 | https://code.metoffice.gov.uk/doc/um/latest/um-training/stashmaster.html |
| 482 | |
| 483 | You will get an error like: |
| 484 | {{{ |
| 485 | [FAIL] file:STASHmaster=source=fcm:um.xm_tr/rose-meta/um-atmos/HEAD/etc/stash/STASHmaster@31236: bad or missing value |
| 486 | Received signal ERR |
| 487 | }}} |
| 488 | |
| 489 | This is because the job tries to access the repository from the ARCHER queues, which will not work. Note this will work on the XCS machines, so if you are porting a suite, it may have something like this in. |
| 490 | |
| 491 | The solution is to make the suite extract the file on PUMA and then copy over to ARCHER with the other suite files. |
| 492 | |
| 493 | You will have a line in `app/um/rose-app.conf` such as: |
| 494 | {{{ |
| 495 | [file:STASHmaster] |
| 496 | source=fcm:um.xm_tr/rose-meta/um-atmos/HEAD/etc/stash/STASHmaster@31236 |
| 497 | }}} |
| 498 | |
| 499 | This should be removed, and the following added to the `rose-suite.conf` file: |
| 500 | {{{ |
| 501 | [file:app/um/file/STASHmaster] |
| 502 | source=fcm:um.xm_tr/rose-meta/um-atmos/HEAD/etc/stash/STASHmaster@31236 |
| 503 | }}} |
| 504 | |
| 505 | |
| 506 | Note the `source=` line is identical but the target `[file:]` line needs to reflect the intended location in the suite directory structure. |
| 507 | |
| 508 | This will extract the file on PUMA and install it to the `app/um` directory on ARCHER which will have exactly the same affect as extracting on ARCHER directly would have done. |
| 509 | |
| 510 | This method will work for any similar files. |