potiuk commented on PR #30588:
URL: https://github.com/apache/airflow/pull/30588#issuecomment-1511551998
Ah ! I KNOW WHY! :exploding_head:
And it's a bug (or rather lack of consitency) in our CI environment (which
was uncovered by the cross-package side effect)! I will fix it shortly to
always behave consistently! It was worth to debug that one, as it will prevent
similar side-effects to slip through accidentally.
It's not MEMORY. It's folder/package sequence that was somewhat random :)
The thing is that when "Other" test type is executed, Breeze will select
folders that remained from all other test types. And it lists the directory by
`find` command output. The sequence of returned folders is somewhat arbitrary,
mostly based on the sequence the directories were created when `git checkout`
was executed.
So sometimes the directories (and tests were executed in this sequence):
```
tests/decorators/test_external_python.py
tests/operators/test_python.py
```
That would be fine, because pickle.loads was monkeypatched AFTER the
external_python tests were run. But in other evnironment it could be executed
in this sequence:
```
tests/operators/test_python.py
tests/decorators/test_external_python.py
```
And the side effect from test_python.py would end up in a faiure,
Defaiult sequence might be different on self-hosted runners or public
runners, or local copy (for example public runners have a different "real"
filesystem, where the self-hosted ones have tmpfs backed one, which could be
enough to makae the checkout work with mostly consistent sequence (and
different) in both cases.
That's why also it was difficult to reproduce locally.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
