Andrey Anshin

> Yeah. We might want to remove or simplify the test. Yeah the test is hacky because we have to change some settings into the runtime for allow us to...

We need a two counters 🤣 - Time spend to adjusts something to coverage or codecov - Time spend to fix impersonation tests

BTW, in attempt to fix some flakey tests we discuss to run specific tests isolated from other tests, for avoid some unpredictable behavior and side effect which it may add...

Yeah, something like that. It would be nice to have run `isolated` over the all backends and pythons versions. Still no idea how to isolate each hacky tests of each...

BTW we could mark temporary `tests/core/test_impersonation_tests.py` as `quarantined` (not a first time) and create a task for move it into `isolated` and implements it.

@ephraimbuddy I think it worthwhile to check it again after we move impersonations as quarantined

This kind of task not a straight forward, required to someone check what kind of core / providers dependencies not ready for 3.12 yet, or we use outdated dependencies or...

@deepak4babu Sorry for the late response. Is this problem still actual (maybe it resolve into the new version of Airflow). If it still relevant could you provide minimum reproducible example?...

Assumption 1 --- Maybe it happen because we use [dill==0.3.1.1.1](https://github.com/apache/airflow/blob/eb0f00cf9c4c71fd871c970857da481d097a4733/constraints-3.11.txt#L263) which was released at Sep 28, 2019 and Python 3.11 was released Oct 24, 2022? ```console root@567a6cdeef08:/opt/airflow# pipdeptree --packages dill...

Maybe it is a good time to think about old issue https://github.com/apache/airflow/issues/7870