Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-31278

exit code 137 (i.e. OutOfMemoryError) in core module

    XMLWordPrintableJSON

Details

    Description

      The following build failed due to a 137 exit code indicating an OutOfMemoryError:
      https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=46643&view=logs&j=77a9d8e1-d610-59b3-fc2a-4766541e0e33&t=125e07e7-8de0-5c6c-a541-a567415af3ef&l=7847

      [...]
      Mar 01 05:29:06 [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.65 s - in org.apache.flink.runtime.io.compression.BlockCompressionTest
      Mar 01 05:29:06 [INFO] Running org.apache.flink.runtime.dispatcher.DispatcherCachedOperationsHandlerTest
      Mar 01 05:29:07 [INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.142 s - in org.apache.flink.runtime.dispatcher.DispatcherCachedOperationsHandlerTest
      Mar 01 05:29:08 [INFO] Running org.apache.flink.runtime.dispatcher.MemoryExecutionGraphInfoStoreTest
      ##[error]Exit code 137 returned from process: file name '/usr/bin/docker', arguments 'exec -i -u 1001  -w /home/vsts_azpcontainer 5953b171e8ed4caba7af2b326533e249211ed4dcc48640edb3c1b0cbbcdf1a21 /__a/externals/node/bin/node /__w/_temp/containerHandlerInvoker.js'.
      Finishing: Test - core
      

      This build ran on an Azure pipeline machine (Azure Pipelines 9) and, therefore, cannot be caused by FLINK-18356. That said, there was a concurrent 137 exit code build failure happening on agent "Azure Pipelines 21" (see 20230301.3) ~10mins later

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              mapohl Matthias Pohl
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: