Skip to content

Update the R path on seneca #2904

@hsoh-u

Description

@hsoh-u

Replace italics below with details for this issue.

RAL IT upgrade the R (R-4.3.1 to R-4.4.0). The path for R should be changed at seneca.

Regarding R for use on RAL Linux machines, we have built the newest R-4.4.0 and made this the default version.

The error messages

DEBUG 1: Finish ascii2nc by met_test(10408) at 2024-06-07 07:25:20Z
/d1/projects/MET/MET_regression/develop/NB20240607/MET-develop/internal/test_unit/bin/mpnc.sh: line 11: /nrit/ral/R-4.3.1/bin/Rscript: Permission denied

ERROR: /d1/projects/MET/MET_regression/develop/NB20240607/MET-develop/internal/test_unit/perl/unit.pl unit_ascii2nc.xml failed.

Describe the Problem

Provide a clear and concise description of the bug here.

The nightly builds at seneca failed because the R path (/nrit/ral/R-4.3.1) exists, but not accessible. It should be modified to /nrit/ral/R-4.4.0.

Expected Behavior

Provide a clear and concise description of what you expected to happen here.

The unit tests from the nightly builds at seneca should run without erros.

Environment

Describe your runtime environment:
1. Machine: (e.g. HPC name, Linux Workstation, Mac Laptop) seneca
2. OS: (e.g. RedHat Linux, MacOS) RedHat Linux
3. Software version number(s) mainv11.0, main_v11.1, and develop

To Reproduce

Describe the steps to reproduce the behavior:
*1. Go to 'seneca
*2. Login as met_test
*3. Run unit tests

Post relevant sample data following these instructions:
https://dtcenter.org/community-code/model-evaluation-tools-met/met-help-desk#ftp

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys here or state NONE.

Define the Metadata

Assignee

  • Select engineer(s) or no engineer required
  • Select scientist(s) or no scientist required

Labels

  • Review default alert labels
  • Select component(s)
  • Select priority
  • Select requestor(s)

Milestone and Projects

  • Select Milestone as the next bugfix version
  • Select Coordinated METplus-X.Y Support project for support of the current coordinated release
  • Select MET-X.Y.Z Development project for development toward the next official release

Define Related Issue(s)

Consider the impact to the other METplus components.

Bugfix Checklist

See the METplus Workflow for details.

  • Complete the issue definition above, including the Time Estimate and Funding Source.
  • Fork this repository or create a branch of main_<Version>.
    Branch name: bugfix_<Issue Number>_main_<Version>_<Description>
  • Fix the bug and test your changes.
  • Add/update log messages for easier debugging.
  • Add/update unit tests.
  • Add/update documentation.
  • Push local changes to GitHub.
  • Submit a pull request to merge into main_<Version>.
    Pull request: bugfix <Issue Number> main_<Version> <Description>
  • Define the pull request metadata, as permissions allow.
    Select: Reviewer(s) and Development issue
    Select: Milestone as the next bugfix version
    Select: Coordinated METplus-X.Y Support project for support of the current coordinated release
  • Iterate until the reviewer(s) accept and merge your changes.
  • Delete your fork or branch.
  • Complete the steps above to fix the bug on the develop branch.
    Branch name: bugfix_<Issue Number>_develop_<Description>
    Pull request: bugfix <Issue Number> develop <Description>
    Select: Reviewer(s) and Development issue
    Select: Milestone as the next official version
    Select: MET-X.Y.Z Development project for development toward the next official release
  • Close this issue.

Metadata

Metadata

Assignees

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions