inducer / inducer/relate

relate test-code conflicts between files

Open
#1,248 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
435
Forks
124
Avg merge
5h 40m
Merged PRs (30d)
14

Description

I was in the middle of setting up the CI test following the script

```
run_yamls=()
for i in $( git grep --name-only PythonCodeQuestion *.yml ) ; do
# FIXME: https://github.com/inducer/relate/issues/951
if ! grep data_files "$i" > /dev/null ; then
run_yamls+=("$i")
fi
done

relate test-code "${run_yamls[@]}"
```

This ends up reusing the module from previous yml. To be specific, `np.linalg.qr = not_allowed` is set inside
```
problem-bank/homework-problems/eigenvalue/code-qr-iteration-givens.yml
```
Then, when running the next file, `code-qr-iteration-shift.yml`, the call of `np.linalg.qr` triggers the assertion error.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the shown `relate test-code "${run_yamls[@]}"` command and reproduce the failure using `problem-bank/homework-problems/eigenvalue/code-qr-iteration-givens.yml` followed by `code-qr-iteration-shift.yml`. Trace how `relate test-code` loads each YAML and determine why the module state from the first file is reused. Done means the two files can run in sequence without the `np.linalg.qr` assertion error.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing-qa, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.