Debug intel after #8883

larsevj · 2024-10-04T10:32:33Z

Issue
Resolves #my_issue

Approach
Short description of the approach

(Screenshot of new behavior in GUI if applicable)

PR title captures the intent of the changes, and is fitting for release notes.
Added appropriate release note label
Commit history is consistent and clean, in line with the contribution guidelines.
Make sure unit tests pass locally after every commit (git rebase -i main --exec 'pytest tests/ert/unit_tests -n logical -m "not integration_test"')

When applicable

When there are user facing changes: Updated documentation
New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
Large PR: Prepare changes in small commits for more convenient review
Bug fix: Add regression test for the bug
Bug fix: Create Backport PR to latest release

Also adjusted which tests have the integration_tests marker

This removes duplication by merging in coverage generation and doctest into the same workflow

eivindjahren and others added 11 commits September 16, 2024 13:17

Move cli tests to ui_tests/cli

4bc6e0d

Move interaction focused gui tests to ui_tests

599906c

Merge integration_tests into unit_tests

156e202

Also adjusted which tests have the integration_tests marker

Adjust test workflows to new categories

41bae75

This removes duplication by merging in coverage generation and doctest into the same workflow

Update documentation with test categories

0497c30

Remove integration_test markers in ui_tests

3fa28b1

Avoid polluting .slurm_submit* files from test

415a315

Add group to openpbs tests

8282958

Make flaky tracking test a ui test

83d7fc6

Separate gui and cli tests for speed

46198c6

Debug mac intel

8176bc1

larsevj closed this Oct 4, 2024

larsevj deleted the debug_intel_after branch October 4, 2024 12:12