Łukasz Gajowy created BEAM-4367:
-----------------------------------

             Summary: Phrase-triggered job (IOIT) never stopped running.
                 Key: BEAM-4367
                 URL: https://issues.apache.org/jira/browse/BEAM-4367
             Project: Beam
          Issue Type: Bug
          Components: testing
            Reporter: Łukasz Gajowy
            Assignee: Jason Kuster


+Steps to reproduce:+ 

1. Define a new Jenkins' job and allow "Phrase triggering" it and timmer 
triggering (cron job).
2. Type "Run seed job" in a pull request comment to trigger Jenkins Seed job on 
the PR.
3. Type the phrase to trigger the job. (eg. "Run Java ParquetIO Performance 
Test")
4. Run the seed job again (from master branch).

+Expected Result:

+The job gets triggered only few times (once would be best). It never triggers 
from cron after the seed job from the master branch is run because there's no 
job definition on master.

+Actual result:+

The job never stops triggering even though seed job from the master branch was 
run many times.

This happened while developing ParquetIO. The ParquetIO IT kept running for 15 
times more (as the time of writing this issue) even though seed job from master 
should have canceled it. Is it due to the fact that the seed job (from step 2) 
failed?

+See:
+[https://builds.apache.org/view/A-D/view/Beam/job/beam_PerformanceTests_ParquetIOIT/]
 
[https://builds.apache.org/view/A-D/view/Beam/job/beam_SeedJob/] 
[https://builds.apache.org/view/A-D/view/Beam/job/beam_SeedJob/1725/console] 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to