Resurrecting the full regression tests

Open
#251 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
46/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, python, shell
Domain
ci-cd, testing

Research direction

Read regression_check.sh to understand how the full regression check compares grids and FK tables. Then inspect the repository’s workflow and runner configuration to see how it can be run again; the issue notes that access to the self-hosted runner may have changed. Done means the regression check runs on relevant changes and catches differences in grids and FK tables.

Written by the indexing model from the issue text.

Description

bug

We should resurrect the full regression test regression_check.sh given that this would have caught (major) differences both at the level of grids and FK tables whenever changes are made or something breaks.

However, something must have changed in the permission of this repository because now I can no longer see and re-configure the self-hosted runner I set up to run this. (cc @scarlehoff)

Dominant language
Python
Stars
2
Forks
0
Avg merge
10d 34m
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NNPDF/pineko

All issues in NNPDF/pineko

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.