Re: Something May Be Wrong with the Travis CI Tests
Very good point. I was looking into this recently, but since time is a
limited matter, I did not really dig into it. It has to do with the test
discovery. The python_operator does not match the given pattern test*.py:
Could you try to prepend the filename with test_. For example,
Op za 13 okt. 2018 om 13:51 schreef Deng Xiaodong <xd.deng.r@xxxxxxxxx>:
> Hi folks, especially our committers,
> Something may be wrong with our Travis CI tests, unless I
> misunderstood/missed something.
> I'm checking *DockerOperator*, and some implementations inside are not
> making sense to me. But no CI tests ever failed due to it. When I check the
> log of the historical Travis CI, surprisingly, I found the test of
> DockerOperator never really run (you search any one of the recent Travis
> To prove this, I forked the latest master branch and tried to add "self
> .assertTrue(1 == 0)" into the code of tests/operators/docker_operator.py
> and tests/operators/python_operator.py
> which would for sure fail the tests. However, and as I suspected, the
> Travis CI passed (
> https://github.com/XD-DENG/incubator-airflow/commits/patch-6). This means
> these two tests were never invoked during the Travis CI, and I believe
> these two are not the only tests affected.
> May anyone take a look into this? If I did misunderstand/miss something,
> kindly let me know.
> Many thanks!