Debug intel macs

[larsevj]

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

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.97%. Comparing base (47c7f5f) to head (fdfe43d).

Additional details and impacted files

@@                      Coverage Diff                       @@
##           test_branch_intel_tests_debug    #8881   +/-   ##
==============================================================
  Coverage                          90.96%   90.97%           
==============================================================
  Files                                343      343           
  Lines                              21286    21286           
==============================================================
+ Hits                               19363    19364    +1     
+ Misses                              1923     1922    -1     

Flag	Coverage Δ
gui-tests	76.21% <ø> (-0.03%)	⬇️
integration-tests	53.42% <ø> (ø)
unit-tests	68.97% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.