[BUG] Pipeline.get_status_tree returns no slots for aborted pipeline with no children about appengine-pipelines HOT 3 OPEN

This is indeed a strange outcome, but this is also strange code. I am not sure what the right thing here is.
Why do you have code filling the outputs above the status check? What do you expect the caller to see in that case?

from appengine-pipelines.

@tkaitchuck - The whole scenario is more complex then you see here. We autogenerate pipeline DAG in the code (we call them workflows), so in general there is more than one pipeline (the single-pipeline workflow example, I've posted above, is a special case). When one of the pipeline in a DAG fails, it's actually a critical situation for the whole workflow and all pipelines in the DAG should be aborted (that's why we raise Abort there). Later on, when we display the whole DAG status in our UI (using output generated by get_status_tree()), we would like to show user particular pipeline that has failed - we cannot depend on built-in pipeline status as all pipelines in the DAG have 'aborted' state in case of Abort exception being raised. That's why all our pipelines has "status" slot.

It looks like problem is in this line: https://github.com/GoogleCloudPlatform/appengine-pipelines/blob/master/python/src/pipeline/pipeline.py#L3178
The slots are added to the status tree only for the "child" pipelines, i.e. slot is not added for root pipeline. Is there a reason for it?

I'd like to open a pull request for this issue, but I'm having problems with running unit tests. Is there some README how to run them?

from appengine-pipelines.

I added a shell script to make it easier.
d6078c7

Run that with the argument 'test' and set the environment variable to point to your SDK.

from appengine-pipelines.