Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Task Build quality check error when running regex on a big task log file. #210

Open
thomasfinchbr opened this issue Apr 10, 2023 · 2 comments
Assignees

Comments

@thomasfinchbr
Copy link

Context

  • Extension: BuildQualityChecks
  • Environment: Azure DevOps Server
    • Server version: * Azure DevOps Server 2020 Update 1.2*
  • Agent type: Lunix/Raspbaerry self-hosted agent
    • Agent version: Latest (2.218.1). Also tested with 2.181.2
  • Pipeline type: yaml pipeline

Task timeout increase and return error 137
When running the task with the config below I get an error when checking for errors in a log file with about 550K lines.
It was also necessary to increase the timeout to 15mim.

The same configuration with task version 6 runs fine, and finishes in only 30s.

Task config:
- task: BuildQualityChecks@8 displayName: Check errors - ${{ parameters.TestType }} inputs: checkWarnings: true warningFailOption: fixed warningThreshold: ${{ parameters.WarningThreshold }} warningFilters: '/FAILURE TEST CASE/' warningTaskFilters: /^Run package - ${{ parameters.TestType }}/ runTitle: Check errors - ${{ parameters.TestType }}

Error code:
##[error]Exit code 137 returned from process: file name '/home/pi/apps/fw_agent/externals/node10/bin/node', arguments '"/home/pi/apps/fw_agent/_work/_tasks/BuildQualityChecks_16a2ad20-f191-11e5-bed4-ab22bcd17937/8.2.1/task.js"'.

@ReneSchumacher ReneSchumacher self-assigned this Apr 13, 2023
@ReneSchumacher
Copy link
Member

Hi @thomasfinchbr,

we will need to investigate this. A Raspberry Pi is a very resource constrained environment and we have never tested our tasks on such a device. Error 137 means that the task ran out of memory. I'm not aware of any big changes in how we handle warning filters between version 6.x and 8.x, but I will check the code to be sure.

Did you post the full task configuration? Or have you enabled additional features of the task like warning statistics?

@thomasfinchbr
Copy link
Author

The above configuration for the task is the full configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants