我尝试使用GitHub Actions在默认Angular项目上设置CI管道。我可以成功地在本地运行单元测试,但使用GitHub Actions时遇到问题。我需要更改什么才能成功运行?
name: Node.js CI
on:
push:
branches: [ master ]
pull_request:
branches: [ master ]
jobs:
build:
runs-on: ubuntu-latest
strategy:
matrix:
node-version: [10.x, 12.x, 14.x]
steps:
- uses: actions/checkout@v2
- name: Use Node.js ${{ matrix.node-version }}
uses: actions/setup-node@v1
with:
node-version: ${{ matrix.node-version }}
- run: npm ci
- run: npm run build --if-present
- run: npm test
以下是此步骤的日志输出
> ng test
Compiling @angular/core/testing : es2015 as esm2015
Compiling @angular/platform-browser/testing : es2015 as esm2015
Compiling @angular/compiler/testing : es2015 as esm2015
Compiling @angular/platform-browser-dynamic/testing : es2015 as esm2015
Compiling @angular/common/testing : es2015 as esm2015
Compiling @angular/router/testing : es2015 as esm2015
- Generating browser application bundles...
17 12 2020 20:14:02.566:WARN [karma]: No captured browser, open http://localhost:9876/
17 12 2020 20:14:02.708:INFO [karma-server]: Karma v5.1.1 server started at http://localhost:9876/
17 12 2020 20:14:02.709:INFO [launcher]: Launching browsers Chrome with concurrency unlimited
17 12 2020 20:14:02.713:INFO [launcher]: Starting browser Chrome
✔ Browser application bundle generation complete.
- Generating browser application bundles...
✔ Browser application bundle generation complete.
17 12 2020 20:14:07.847:WARN [karma]: No captured browser, open http://localhost:9876/
17 12 2020 20:14:08.707:ERROR [launcher]: Cannot start Chrome
[2646:2646:1217/201408.612463:ERROR:browser_main_loop.cc(1434)] Unable to open X display.
17 12 2020 20:14:08.707:ERROR [launcher]: Chrome stdout:
17 12 2020 20:14:08.707:ERROR [launcher]: Chrome stderr: [2646:2646:1217/201408.612463:ERROR:browser_main_loop.cc(1434)] Unable to open X display.
17 12 2020 20:14:08.712:INFO [launcher]: Trying to start Chrome again (1/2).
17 12 2020 20:14:08.860:ERROR [launcher]: Cannot start Chrome
[2682:2682:1217/201408.854964:ERROR:browser_main_loop.cc(1434)] Unable to open X display.
17 12 2020 20:14:08.861:ERROR [launcher]: Chrome stdout:
17 12 2020 20:14:08.861:ERROR [launcher]: Chrome stderr: [2682:2682:1217/201408.854964:ERROR:browser_main_loop.cc(1434)] Unable to open X display.
17 12 2020 20:14:08.863:INFO [launcher]: Trying to start Chrome again (2/2).
17 12 2020 20:14:09.006:ERROR [launcher]: Cannot start Chrome
[2711:2711:1217/201409.000191:ERROR:browser_main_loop.cc(1434)] Unable to open X display.
17 12 2020 20:14:09.006:ERROR [launcher]: Chrome stdout:
17 12 2020 20:14:09.007:ERROR [launcher]: Chrome stderr: [2711:2711:1217/201409.000191:ERROR:browser_main_loop.cc(1434)] Unable to open X display.
17 12 2020 20:14:09.008:ERROR [launcher]: Chrome failed 2 times (cannot start). Giving up.
2条答案
按热度按时间ccgok5k51#
如果你不想按照另一个答案中的建议修改你的package.json、karma.conf或者安装Puppeteer(不管是什么),你可以修改你的GitHub动作配置,把
--watch=false
和--browsers=ChromeHeadless
标记传递给底层脚本。第一个“浮动”
--
很重要...它告诉NPM将任何后续参数传递给它调用的脚本,而不是尝试对npm求值。因此,如果npm test
调用ng test
,上面的代码实际上将调用ng test --watch=false --browsers=ChromeHeadless
。--watch=false
将修复“运行永不结束”的问题,该问题是由ng test
监视文件更改以触发测试重新运行引起的。--browsers=ChromeHeadless
将修复GitHub Actions无法在没有显示屏的系统上运行完整的Chrome浏览器(因此错误输出中出现“无法打开X显示屏”)。因此,它将运行一个特殊的无头版本来模拟显示屏部分,而不是运行完整的Chrome浏览器。mspsb9vt2#
你需要安装puppeteer等一些额外的配置
在
restartOnFileChange: true,
下的karma.conf.js中添加在package.json中,将测试脚本更新为
"test": "ng test --watch=false --browsers=ChromeHeadlessCustom",