Skip to content

Conversation

jgphpc
Copy link
Collaborator

@jgphpc jgphpc commented Aug 13, 2025

  • update test for new uenv: /capstor/scratch/cscs/biddisco/uenvs/paraview-silo-gh200-6.0.0-2025-08-08.squashfs
  • Share the command line used to run the test
UENV=$PWD/JB/paraview-silo-gh200-6.0.0-2025-08-08.squashfs reframe \
 -c cscs-reframe-tests.git/checks/apps/paraview/paraview.py --system daint:normal
  • need a deployed uenv

  • cscs-ci run alps-daint-uenv;MY_UENV=$PWD/paraview-silo-gh200-6.0.0-2025-08-08.squashfs (there is no deployed uenv yet)

@jgphpc jgphpc self-assigned this Aug 13, 2025
@jgphpc jgphpc requested review from Copilot and ekouts August 13, 2025 13:26
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR updates the ParaView test configuration to work with ParaView version 6.0, changing from hardcoded version-specific paths to dynamic symlink resolution. The update enables testing with a new uenv (user environment) for ParaView 6.0.0.

  • Replace hardcoded ParaView 5.13 paths with dynamic symlink approach
  • Add symlink creation commands to locate ParaView installation dynamically
  • Update environment variable paths to use relative paths through symlinks

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@jgphpc jgphpc marked this pull request as draft August 26, 2025 07:22
time_limit = '3m'
executable = '/user-environment/ParaView-5.13/bin/pvbatch'
executable = './ParaView/bin/pvbatch'
# executable = '/user-environment/ParaView-5.13/bin/pvbatch'
Copy link
Collaborator

Choose a reason for hiding this comment

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

Does it make sense to remove the comment?

'CATALYST_IMPLEMENTATION_NAME': 'paraview',
'CATALYST_IMPLEMENTATION_PATHS':
'/user-environment/ParaView-5.13/lib64/catalyst',
'CATALYST_IMPLEMENTATION_PATHS': '$PWD/ParaView/lib64/catalyst',
Copy link
Collaborator

Choose a reason for hiding this comment

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

Does it make sense to use /user-environment/Paraview, instead of $PWD?

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