There is a problem that is still not fixed in Python: https://builds.apache.org/job/beam_PostCommit_Python_Verify/4909/console
On Wed, May 9, 2018 at 12:07 PM Andrew Pilloud <[email protected]> wrote: > Post commits are no longer failing on status pushes. Now that I know about > the seed job, I'll figure out how to test my changes in the future. Sorry > for all the trouble! > > Andrew > > On Wed, May 9, 2018 at 11:36 AM Pablo Estrada <[email protected]> wrote: > >> I was able to trigger a build again just now. >> >> On Wed, May 9, 2018 at 11:27 AM Andrew Pilloud <[email protected]> >> wrote: >> >>> The manual launch button doesn't exist for me. I am not a committer, so >>> I don't have a login to Jenkins. >>> >>> On Wed, May 9, 2018 at 11:16 AM Lukasz Cwik <[email protected]> wrote: >>> >>>> You can also just manually launch a seed job from within Jenkins >>>> pointing at apache/master as its source. >>>> >>>> On Wed, May 9, 2018 at 11:10 AM Andrew Pilloud <[email protected]> >>>> wrote: >>>> >>>>> I've not heard of seed jobs before, but from what I've been told I >>>>> need to create a PR with a empty '.test-infra/jenkins' folder then type >>>>> 'Run Seed Job' in a comment to apply the revert? Doing that now. >>>>> >>>>> Andrew >>>>> >>>>> On Wed, May 9, 2018 at 11:08 AM Lukasz Cwik <[email protected]> wrote: >>>>> >>>>>> I am also seeing the delayed launch of the tests. >>>>>> >>>>>> On Wed, May 9, 2018 at 10:56 AM Pablo Estrada <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> Does this require a Seed Job rerun? I'm seeing Python postcommits >>>>>>> breaking as well >>>>>>> >>>>>>> On Wed, May 9, 2018 at 10:49 AM Alan Myrvold <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> I saw ~1-2 hour latency for the trigger happening yesterday. Not >>>>>>>> sure what would cause it to stop or be slow. >>>>>>>> >>>>>>>> On Wed, May 9, 2018 at 10:45 AM Lukasz Cwik <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> It seems as though precommits are no longer triggering and trigger >>>>>>>>> requests like 'Run Java PreCommit' are no longer honored. >>>>>>>>> >>>>>>>>> On Wed, May 9, 2018 at 10:22 AM Andrew Pilloud < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> I broke all the post commits with this. Sorry! It has been >>>>>>>>>> reverted. I'm going to follow up with Apache Infra about getting the >>>>>>>>>> right >>>>>>>>>> credentials configured on the Jenkins plugin. >>>>>>>>>> >>>>>>>>>> Andrew >>>>>>>>>> >>>>>>>>>> On Tue, May 8, 2018 at 1:38 PM Andrew Pilloud < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> Yep, mess with the groovy scripts appears to be the answer. We >>>>>>>>>>> use different jenkins libraries to handle PRs vs pushes to master >>>>>>>>>>> but I >>>>>>>>>>> think I finally figured it out. Change is here: >>>>>>>>>>> https://github.com/apache/beam/pull/5305 >>>>>>>>>>> >>>>>>>>>>> Andrew >>>>>>>>>>> >>>>>>>>>>> On Mon, May 7, 2018 at 12:40 PM Kenneth Knowles <[email protected]> >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> I think you want to mess with the groovy scripts in >>>>>>>>>>>> .test-infra/jenkins >>>>>>>>>>>> >>>>>>>>>>>> Kenn >>>>>>>>>>>> >>>>>>>>>>>> On Mon, May 7, 2018 at 11:12 AM Andrew Pilloud < >>>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> The Github branches page shows the status of the latest commit >>>>>>>>>>>>> on each branch and provides a set of links to the jobs run on >>>>>>>>>>>>> that commit. >>>>>>>>>>>>> But it doesn't appear Jenkins is publishing status from post >>>>>>>>>>>>> commit jobs. >>>>>>>>>>>>> This seems like a simple oversight that should be easy to fix. >>>>>>>>>>>>> Could >>>>>>>>>>>>> someone point me in the right direction to fix this? >>>>>>>>>>>>> >>>>>>>>>>>>> Andrew >>>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>> Got feedback? go/pabloem-feedback >>>>>>> <https://goto.google.com/pabloem-feedback> >>>>>>> >>>>>> -- >> Got feedback? go/pabloem-feedback >> <https://goto.google.com/pabloem-feedback> >> > -- Got feedback? go/pabloem-feedback
