I saw HttpError from the console log
<https://scans.gradle.com/s/b3s5klq6ohydi/console-log#L6817> in the job you
provided above
<https://builds.apache.org/job/beam_PostCommit_Python3_Verify_PR/77/>:

"error": {
"code": 404,
"message": "(b8b815bd6683759f): Information about job
2019-03-06_04_32_19-1780414729477627626 could not be found in our system.
Please double check the id is correct. If it is please contact customer
support.",
"status": "NOT_FOUND"
}

Looks like it's caused by Dataflow service flaky, not your test. Since the
current postcommit
<https://builds.apache.org/job/beam_PostCommit_Python_Verify/> is green
now, you can run postcommit again.

Mark


On Wed, Mar 6, 2019 at 10:04 AM Juta Staes <juta.st...@ml6.eu> wrote:

> Hi all,
>
> I am working on adding Python 3 integration tests to the post commit tests.
>
> Since yesterday none of the post commit tests seem to pass. There are
> errors in the build jobs as can be seen in the Post-Commit Tests Status
> table at https://github.com/apache/beam/pull/7946 (and in other prs as
> well) and at
> https://builds.apache.org/job/beam_PostCommit_Python3_Verify_PR/77/console
>
> AssertionError: Job did not reach to a terminal state after waiting 
> indefinitely.
>
>
> Yesterday my tests did pass:
> https://builds.apache.org/job/beam_PostCommit_Python3_Verify_PR/61/console but
> failed on a build timed out.
>
> Does someone has any idea what is happening with the post commit tests?
>
> Thanks!
>
> --
>
> [image: https://ml6.eu] <https://ml6.eu/>
>
> * Juta Staes*
> ML6 Gent
> <https://www.google.be/maps/place/ML6/@51.037408,3.7044893,17z/data=!3m1!4b1!4m5!3m4!1s0x47c37161feeca14b:0xb8f72585fdd21c90!8m2!3d51.037408!4d3.706678?hl=nl>
>
> **** DISCLAIMER ****
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
> This message contains confidential information and is intended only for the
> individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately by e-mail if you have received this e-mail by mistake and
> delete this e-mail from your system. If you are not the intended recipient
> you are notified that disclosing, copying, distributing or taking any
> action in reliance on the contents of this information is strictly
> prohibited.
>

Reply via email to