The GitHub Actions job "Build Images" on airflow.git has succeeded. Run started by GitHub user dstandish (triggered by dstandish).
Head commit for run: b4f12f8aa0ae4770bb192fffee71f7a79b249c87 / Daniel Standish <[email protected]> Test patch_already_checked directly (and separate from the other tests) The "already_checked" label was added to a few "expected pods" recently, when we changed it to patch even in the case of a successful pod. Since we are changing the "patch" code to patch with the latest read on the pod that we have (i.e. using the `remote_pod` variable), and no longer the pod object stored on `k.pod`, the label no longer shows up in those tests (that's because in k.pod isn't actually a read of the remote pod, but just happens to get mutated in the patch function before it is used to actually patch the pod). Further, since the `remote_pod` is a local variable, we can't observe it in tests. So we have to read the pod using k8s api. _But_, our "find pod" function excludes "already checked" pods! So we have to make this configurable. So, now we have a proper integration test for the "already_checked" behavior (there was already a unit test). Report URL: https://github.com/apache/airflow/actions/runs/2333955780 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
