Fix Celery tests in Potel

[antonpirker]

No description provided.

[codecov]

❌ 8883 Tests Failed:

Tests completed	Failed	Passed	Skipped
18225	8883	9342	4111

View the top 3 failed tests by shortest run time

tests.test_scope test_with_use_isolation_scope_data

Stack Traces | 0.001s run time

tests/test_scope.py:496: in test_with_use_isolation_scope_data
    assert current_scope_in._tags == {"before_current_scope": 1}
E   AssertionError: assert {'tag1': 'value', 'before_current_scope': 1} == {'before_current_scope': 1}
E     
E     Common items:
E     {'before_current_scope': 1}
E     Left contains 1 more item:
E     {'tag1': 'value'}
E     
E     Full diff:
E       {
E           'before_current_scope': 1,
E     +     'tag1': 'value',
E       }

tests.test_scope test_with_use_isolation_scope_data

Stack Traces | 0.001s run time

tests/test_scope.py:496: in test_with_use_isolation_scope_data
    assert current_scope_in._tags == {"before_current_scope": 1}
E   AssertionError: assert {'tag1': 'value', 'before_current_scope': 1} == {'before_current_scope': 1}
E     
E     Common items:
E     {'before_current_scope': 1}
E     Left contains 1 more item:
E     {'tag1': 'value'}
E     
E     Full diff:
E       {
E           'before_current_scope': 1,
E     +     'tag1': 'value',
E       }

tests.test_scope test_with_use_scope_data

Stack Traces | 0.001s run time

tests/test_scope.py:690: in test_with_use_scope_data
    assert isolation_scope_in._tags == {"before_isolation_scope": 1}
E   AssertionError: assert {'tag1': 'value', 'before_isolation_scope': 1} == {'before_isolation_scope': 1}
E     
E     Common items:
E     {'before_isolation_scope': 1}
E     Left contains 1 more item:
E     {'tag1': 'value'}
E     
E     Full diff:
E       {
E           'before_isolation_scope': 1,
E     +     'tag1': 'value',
E       }

To view more test analytics, go to the Test Analytics Dashboard
Got feedback? Let us know on Github

[antonpirker]

This just makes the diff of failing tests way easier to read

[sl0thentr0py]

let's do this in __exit__ above since we are already setting INTERNAL_ERROR there.

[antonpirker]

But if people do not use the contextmanager, the status will not be set.

[antonpirker]

When thinking of it, thats probably ok. If you use the context manager, we take care of the status. If you start/finish spans manually, you need to take care of the status