lundi 22 mars 2021

GitHub throws Test-Error without any description

I am currently facing some issues when trying to run the tests from GitHub onto my project. Everything seems to work but i will always get this error when trying to use "Test":


Run npm test -- --configuration=ci
  npm test -- --configuration=ci
  shell: C:\Program Files\PowerShell\7\pwsh.EXE -command ". '{0}'"

> ionic-base-app@0.0.0 test D:\a\ionic-base-app\ionic-base-app
> ng test "--configuration=ci"

22 03 2021 12:15:45.888:INFO [karma-server]: Karma v4.4.1 server started at http://0.0.0.0:9876/
22 03 2021 12:15:45.891:INFO [launcher]: Launching browsers Chrome, ChromeHeadless with concurrency unlimited
22 03 2021 12:15:45.895:INFO [launcher]: Starting browser Chrome
22 03 2021 12:15:45.914:INFO [launcher]: Starting browser ChromeHeadless
22 03 2021 12:15:53.195:INFO [Chrome 78.0.3882 (Windows 10.0.0)]: Connected on socket fH43nkyvGU-MUaiiAAAA with id 13445804
22 03 2021 12:15:53.207:INFO [HeadlessChrome 78.0.3882 (Windows 10.0.0)]: Connected on socket xv2LDdIUaaftCx0EAAAB with id 37247542
Chrome 78.0.3882 (Windows 10.0.0): Executed 0 of 0 SUCCESS (0 secs / 0 secs)

Chrome 78.0.3882 (Windows 10.0.0): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
HeadlessChrome 78.0.3882 (Windows 10.0.0): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Chrome 78.0.3882 (Windows 10.0.0): Executed 0 of 0 SUCCESS (0.003 secs / 0 secs)
HeadlessChrome 78.0.3882 (Windows 10.0.0): Executed 0 of 0 SUCCESS (0 secs / 0 secs)
Chrome 78.0.3882 (Windows 10.0.0): Executed 0 of 0 SUCCESS (0.003 secs / 0 secs)
HeadlessChrome 78.0.3882 (Windows 10.0.0): Executed 0 of 0 SUCCESS (0.014 secs / 0 secs)
TOTAL: 0 SUCCESS
TOTAL: 0 SUCCESS
npm ERR! Test failed.  See above for more details.
Error: Process completed with exit code 1.

When trying to test my local installation (same as in GitHub) I do not get any error. Using the command npm test.

But i do also get the same output like above on my local installation using npm test -- --configuration=ci.

Did i missed something to reconfigure or is it like a bug in GitHub?

Aucun commentaire:

Enregistrer un commentaire