-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Ensure dag.test uses serialized dag for testing #56660
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure dag.test uses serialized dag for testing #56660
Conversation
tatiana
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ephraimbuddy Thanks a lot for working on this so quickly.
Would it be worth to update the PR description to mention it closes #56657?
Yes. Done. Thanks |
|
I noticed the task is failing when executing: |
airflow-core/src/airflow/api_fastapi/execution_api/datamodels/taskinstance.py
Outdated
Show resolved
Hide resolved
kaxil
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fundamental question: Should dag.test() create a temporary serialized DAG version like it was doing in one of the early 3.0.x version, or should it bypass the serialization requirement entirely?
The command option( |
yeah is there much downside to just creating it? |
Yeah I am in favor of making it consistent to |
5d8bd17 to
5873cd6
Compare
|
I have updated this PR to enable dag parsing in the dag.test method |
829c6cf to
d959325
Compare
d959325 to
5e9b466
Compare
kaxil
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor nitpicks -- lgtm otherwise
957da39 to
fcc70fc
Compare
While `dag test` command uses serialized dag, dag.test was using in-memory serialized dag making direct usage of dag.test method resulting in error. This PR fixes this and ensures dag.test parses dag if the dag is not parsed
fcc70fc to
7f5e18c
Compare
* Ensure dag.test uses serialized dag for testing While `dag test` command uses serialized dag, dag.test was using in-memory serialized dag making direct usage of dag.test method resulting in error. This PR fixes this and ensures dag.test parses dag if the dag is not parsed * fixup! Ensure dag.test uses serialized dag for testing * Update query to v2 and do backcompat for 3.1 * Remove backcompat * Return previous behaviour with SerializedDag (cherry picked from commit 6d977a9)
…56820) * Ensure dag.test uses serialized dag for testing (#56660) * Ensure dag.test uses serialized dag for testing While `dag test` command uses serialized dag, dag.test was using in-memory serialized dag making direct usage of dag.test method resulting in error. This PR fixes this and ensures dag.test parses dag if the dag is not parsed * fixup! Ensure dag.test uses serialized dag for testing * Update query to v2 and do backcompat for 3.1 * Remove backcompat * Return previous behaviour with SerializedDag (cherry picked from commit 6d977a9) * fixup! Ensure dag.test uses serialized dag for testing (#56660)
* Ensure dag.test uses serialized dag for testing While `dag test` command uses serialized dag, dag.test was using in-memory serialized dag making direct usage of dag.test method resulting in error. This PR fixes this and ensures dag.test parses dag if the dag is not parsed * fixup! Ensure dag.test uses serialized dag for testing * Update query to v2 and do backcompat for 3.1 * Remove backcompat * Return previous behaviour with SerializedDag
* Ensure dag.test uses serialized dag for testing While `dag test` command uses serialized dag, dag.test was using in-memory serialized dag making direct usage of dag.test method resulting in error. This PR fixes this and ensures dag.test parses dag if the dag is not parsed * fixup! Ensure dag.test uses serialized dag for testing * Update query to v2 and do backcompat for 3.1 * Remove backcompat * Return previous behaviour with SerializedDag
* Ensure dag.test uses serialized dag for testing While `dag test` command uses serialized dag, dag.test was using in-memory serialized dag making direct usage of dag.test method resulting in error. This PR fixes this and ensures dag.test parses dag if the dag is not parsed * fixup! Ensure dag.test uses serialized dag for testing * Update query to v2 and do backcompat for 3.1 * Remove backcompat * Return previous behaviour with SerializedDag
While
dag testcommand uses serialized dag, dag.test was usingin-memory serialized dag making direct usage of dag.test method
resulting in error.
This PR fixes this and ensures dag.test parses dag if the dag is not
parsed
Closes: #56657