Skip to content
This repository has been archived by the owner on Mar 14, 2024. It is now read-only.

Error with reports with focused or disabled tests #9

Open
ldeveber opened this issue Jan 25, 2018 · 8 comments
Open

Error with reports with focused or disabled tests #9

ldeveber opened this issue Jan 25, 2018 · 8 comments

Comments

@ldeveber
Copy link

Protractor is failing with the following when a test is disabled or focused:

[2018-01-25 13:07:34.138] [ERROR] - TypeError: First argument must be a string, Buffer, ArrayBuffer, Array, or array-like object.
    at Function.Buffer.from (buffer.js:183:11)
    at new Buffer (buffer.js:158:17)
    at Reporter.writeImage (/Users/xxx/projects/yy-static/protractor/node_modules/protractor-pretty-html-reporter/reporter.js:169:22)
    at Reporter.specDone (/Users/xxx/projects/yy-static/protractor/node_modules/protractor-pretty-html-reporter/reporter.js:117:18)
    at dispatch (/Users/xxx/projects/yy-static/protractor/node_modules/jasmine-core/lib/jasmine-core/jasmine.js:4522:28)
    at ReportDispatcher.specDone (/Users/xxx/projects/yy-static/protractor/node_modules/jasmine-core/lib/jasmine-core/jasmine.js:4493:11)
    at Spec.specResultCallback [as resultCallback] (/Users/xxx/projects/yy-static/protractor/node_modules/jasmine-core/lib/jasmine-core/jasmine.js:1220:18)
    at complete (/Users/xxx/projects/yy-static/protractor/node_modules/jasmine-core/lib/jasmine-core/jasmine.js:565:12)
    at QueueRunner.runnerConfig.onComplete (/Users/xxx/projects/yy-static/protractor/node_modules/jasmine-core/lib/jasmine-core/jasmine.js:558:46)
    at Immediate._onImmediate (/Users/xxx/projects/yy-static/protractor/node_modules/jasmine-core/lib/jasmine-core/jasmine.js:4382:12)
    at runCallback (timers.js:789:20)
    at tryOnImmediate (timers.js:751:5)
    at processImmediate [as _immediateCallback] (timers.js:722:5)

I'm using jasmine 2.9 with protractor 5.2.2.

@cpaika
Copy link

cpaika commented Jan 25, 2018

+1

2 similar comments
@AlexMarchini
Copy link

+1

@SnarkyArtificer
Copy link

👍

@stuisme
Copy link
Owner

stuisme commented Jan 26, 2018

It looks like it's related to the screenshot functionality.

What browser versions are being used?

@ldeveber
Copy link
Author

I'm using Chrome, not headless when these errors are appearing.

@rakeshrk21
Copy link

did we figure out a resolution to this?

@cpaika
Copy link

cpaika commented Dec 4, 2019

@ldeveber Would possibly remember the fix, but we did end up fixing it on our end. It was a long time ago so I forgot the specific fix unfortunately 😞

@ldeveber
Copy link
Author

I unfortunately do not remember what I did without looking at the code, which I no longer have access to :(

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

No branches or pull requests

6 participants