使用Puppeteer捕获ChromeHeadless启动器的问题

问题描述 投票:0回答:1

有人可以帮我解决这个问题吗?

[我正在获取[[启动器]:ChromeHeadless在60000毫秒内未捕获,导致死亡。”当管道(Jenkins)尝试使用业力执行测试时(使用ChromeHeadless的Puppeteer)]

我们根据客户端的要求将启动器从Phantomjs更改为ChromeHeadless;

我们已经尝试了很多事情,直到现在还没有任何效果,我也不知道如何解决。

有关项目配置的一些信息:

我们按如下方式使用角度7,业力依赖关系和操纵up:

package.json
{
  "name": "xxxxxxxx",
  "version": "0.0.0",
  "license": "my",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "test": "ng test -c karma.conf.js -cc --browsers MyChromeHeadless",
    "lint": "ng lint",
    "e2e": "ng e2e"
  },
  "dependencies": {
    "@angular-devkit/build-angular": "^0.13.9",
    "@angular/animations": "7.2.15",
    "@angular/common": "7.2.15",
    "@angular/compiler": "7.2.15",
    "@angular/core": "7.2.15",
    "@angular/forms": "7.2.15",
    "@angular/http": "7.2.15",
    "@angular/platform-browser": "7.2.15",
    "@angular/platform-browser-dynamic": "7.2.15",
    "@angular/router": "7.2.15",
    "@ng-bootstrap/ng-bootstrap": "1.0.0-beta.4",
    "@ngx-translate/core": "^8.0.0",
    "angl-spawebbgrl": "^6.2.0",
    "angular2-text-mask": "^8.0.4",
    "angular2-tinymce": "2.1.2",
    "angular2-ui-switch": "^1.2.0",
    "bootstrap": "^3.3.7",
    "core-js": "2.4.1",
    "font-awesome": "^4.7.0",
    "intl": "^1.2.5",
    "jquery": "^3.4.1",
    "moment": "^2.24.0",
    "ng2-bs3-modal": "^0.10.4",
    "ng2-translate": "^5.0.0",
    "ngx-bootstrap": "1.9.3",
    "ngx-toastr": "^6.5.0",
    "puppeteer": "^2.0.0",
    "rxjs": "6.5.3",
    "rxjs-compat": "^6.0.0-rc.0",
    "text-mask-addons": "^3.7.0",
    "tslib": "^1.9.0",
    "xlsx": "^0.12.0",
    "zone.js": "0.8.29"
  },
  "devDependencies": {
    "@angular/cli": "^7.3.9",
    "@angular/compiler-cli": "^7.2.15",
    "@angular/language-service": "^7.2.15",
    "@types/jasmine": "3.4.6",
    "@types/jasminewd2": "2.0.8",
    "@types/node": "8.10.59",
    "bower-art-resolver": "^2.0.10",
    "chai": "4.2.0",
    "codelyzer": "3.0.1",
    "jasmine-core": "3.5.0",
    "jasmine-spec-reporter": "4.2.1",
    "karma": "^4.4.1",
    "karma-chai": "0.1.0",
    "karma-chrome-launcher": "3.1.0",
    "karma-cli": "2.0.0",
    "karma-coverage": "^2.0.1",
    "karma-coverage-istanbul-reporter": "2.1.0",
    "karma-jasmine": "2.0.1",
    "karma-jasmine-html-reporter": "1.4.2",
    "karma-junit-reporter": "2.0.1",
    "karma-mocha": "^1.1.1",
    "karma-sinon": "1.0.5",
    "mocha": "^6.2.2",
    "mocha-junit-reporter": "1.23.1",
    "protractor": "^6.0.0",
    "selenium-webdriver": "^3.6.0",
    "sinon": "1.17.5",
    "ts-node": "3.0.4",
    "tslint": "5.3.2",
    "typescript": "^3.1.1"
  },
  "optionalDependencies": {
  }
}

我们的业力配置:

karma.conf.js

module.exports = function (config) {

  const process = require('process');
  process.env.CHROME_BIN = require('puppeteer').executablePath();

  config.set({
    basePath: '',
    frameworks: ['jasmine', '@angular-devkit/build-angular'],
    plugins: [
      require('karma-jasmine'),
      require('karma-coverage'),
      require('karma-coverage-istanbul-reporter'),
      require('karma-chrome-launcher'),
      require('karma-jasmine-html-reporter'),
      require('@angular-devkit/build-angular/plugins/karma')
    ],
    files:[
      'src/test.ts'
    ],
    client:{
      clearContext: false // leave Jasmine Spec Runner output visible in browser
    },
    coverageIstanbulReporter: {
      dir: require('path').join(__dirname, 'coverage'), reports: [ 'html', 'lcovonly' ],
      fixWebpackSourcePaths: true,
      dir: 'coverage',
      'report-config':  { html: { subdir: 'html'} }
    },
    reporters: ['progress', 'kjhtml', 'coverage'], 
    port: 9876,
    logLevel: config.LOG_DEBUG,
    autoWatch: false,
    singleRun: true,
    browsers: ['MyChromeHeadless'], 
    customLaunchers: {
    MyChromeHeadless: {
        base: 'ChromeHeadless',
        flags: [
          '--no-sandbox',
          '--proxy-auto-detect'
        ]
      }
    }
  });
};

当詹金斯尝试执行测试,但在本地运行一切正常时,会发生此错误。此问题特定于在Linux机器上运行的管道;

[有人来帮助我获得[[发射器]:ChromeHeadless在60000毫秒内未捕获,导致死亡。”固定?

欢迎任何建议。 Tkx!

jenkins-pipeline puppeteer docker-machine google-chrome-headless karma-chrome-launcher
1个回答
0
投票

只是检查,但是您确定在流水线计算机上安装了有效版本的Chrome,并且已设置路径以便启动程序可以找到它吗?

听起来像是laucher只是在尝试启动HC时就超时了,最明显的问题是谁无法找到要运行的版本。

© www.soinside.com 2019 - 2024. All rights reserved.