Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-70681

Automatically execute a large number of the same tasks, and the "Hard kill!" log appears.

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Blocker Blocker
    • jenkinsfile-runner
    • Jenkins ver. 2.176.2,

      Jenkins automatically executes a task more than 100 times, and a "hard kill!" log appears on the way to run, causing the task to stop directly.
      Jenkins is using the java-based appium automated test platform.
      Since the running job is only executing the same task repeatedly, it should not be a problem of the running program.

      Jenkins Log:

      [2023-02-20T08:34:42.242Z] 2023/02/20
      [Pipeline] echo
      [2023-02-20T08:34:42.262Z] ループカウント = 1 / 100回目開始
      [Pipeline] build
      [2023-02-20T08:34:42.403Z] Scheduling project: xxxx
      [2023-02-20T08:34:50.953Z] Starting building: xxxx #1280
      [Pipeline] bat
      [2023-02-20T08:44:33.222Z] 
      [2023-02-20T08:44:33.222Z] C:\Program Files (x86)\Jenkins\workspace\xxxxx>echo 2023/02/20 
      [2023-02-20T08:44:33.222Z] 2023/02/20
      [Pipeline] echo
      [2023-02-20T08:44:33.241Z] ループカウント = 1 / 100回目終了

      .....

      [2023-02-20T23:51:27.657Z] ループカウント = 77 / 100回目開始
      [Pipeline] build
      [2023-02-20T23:51:27.673Z] Scheduling project: xxxx
      [2023-02-20T23:51:35.941Z] Starting building: xxxx #1356
      Hard kill!
      Finished: ABORTED

       

      Please help analyze the cause and how to solve it.

      thank you.

          [JENKINS-70681] Automatically execute a large number of the same tasks, and the "Hard kill!" log appears.

          cheng created issue -
          cheng made changes -
          Summary Original: Jenkins automatically executes a task for more than 100 times, and the "Hard kill!" log appears, resulting in the failure of continuous task execution. New: Automatically execute a large number of the same tasks, and the "Hard kill!" log appears.
          cheng made changes -
          Description Original: Jenkins automatically executes a task more than 100 times, and a "hard kill!" log appears on the way to run, causing the task to stop directly.
          Jenkins is using the java-based appium automated test platform.
          Since the running job is only executing the same task repeatedly, it should not be a problem of the running program.

          Jenkins Log:

          [2023-02-20T08:34:42.242Z] 2023/02/20
          [Pipeline] echo
          [2023-02-20T08:34:42.262Z] ループカウント = 1 / 100回目開始
          [Pipeline] build
          [2023-02-20T08:34:42.403Z] Scheduling project: iwama
          [2023-02-20T08:34:50.953Z] Starting building: iwama #1280
          [Pipeline] bat
          [2023-02-20T08:44:33.222Z] 
          [2023-02-20T08:44:33.222Z] C:\Program Files (x86)\Jenkins\workspace\iwamastart>echo 2023/02/20 
          [2023-02-20T08:44:33.222Z] 2023/02/20
          [Pipeline] echo
          [2023-02-20T08:44:33.241Z] ループカウント = 1 / 100回目終了

          .....

          [2023-02-20T23:51:27.657Z] ループカウント = 77 / 100回目開始
          [Pipeline] build
          [2023-02-20T23:51:27.673Z] Scheduling project: iwama
          [2023-02-20T23:51:35.941Z] Starting building: iwama #1356
          {color:#FF0000}Hard kill!{color}
          Finished: ABORTED

           

          Please help analyze the cause and how to solve it.

          thank you.
          New: Jenkins automatically executes a task more than 100 times, and a "hard kill!" log appears on the way to run, causing the task to stop directly.
          Jenkins is using the java-based appium automated test platform.
          Since the running job is only executing the same task repeatedly, it should not be a problem of the running program.

          Jenkins Log:

          [2023-02-20T08:34:42.242Z] 2023/02/20
          [Pipeline] echo
          [2023-02-20T08:34:42.262Z] ループカウント = 1 / 100回目開始
          [Pipeline] build
          [2023-02-20T08:34:42.403Z] Scheduling project: xxxx
          [2023-02-20T08:34:50.953Z] Starting building: xxxx #1280
          [Pipeline] bat
          [2023-02-20T08:44:33.222Z] 
          [2023-02-20T08:44:33.222Z] C:\Program Files (x86)\Jenkins\workspace\xxxxx>echo 2023/02/20 
          [2023-02-20T08:44:33.222Z] 2023/02/20
          [Pipeline] echo
          [2023-02-20T08:44:33.241Z] ループカウント = 1 / 100回目終了

          .....

          [2023-02-20T23:51:27.657Z] ループカウント = 77 / 100回目開始
          [Pipeline] build
          [2023-02-20T23:51:27.673Z] Scheduling project: xxxx
          [2023-02-20T23:51:35.941Z] Starting building: xxxx #1356
          {color:#ff0000}Hard kill!{color}
          Finished: ABORTED

           

          Please help analyze the cause and how to solve it.

          thank you.
          cheng made changes -
          Assignee New: cheng [ c1041651283 ]
          cheng made changes -
          Assignee Original: cheng [ c1041651283 ] New: Daniel Beck [ danielbeck ]
          Daniel Beck made changes -
          Assignee Original: Daniel Beck [ danielbeck ]

          Daniel Beck added a comment -

          Please do not assign issues to other people unless you know they're working on it (or planning to).

          Daniel Beck added a comment - Please do not assign issues to other people unless you know they're working on it (or planning to).

          Mark Waite added a comment -

          Very old Jenkins version with insufficient detail to duplicate the problem and no further information from the submitter. Closing as "Cannot reproduce".

          Mark Waite added a comment - Very old Jenkins version with insufficient detail to duplicate the problem and no further information from the submitter. Closing as "Cannot reproduce".
          Mark Waite made changes -
          Resolution New: Cannot Reproduce [ 5 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            Unassigned Unassigned
            c1041651283 cheng
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: