Failed to read proto message: unexpected EOF

[haroon-sheikh]

Failed to read proto message: unexpected EOF

Expected behavior

Tell us what should happen

Actual behavior

Continuously logs the following error message and stuck in a loop at the end of execution

Failed to read proto message: unexpected EOF
Failed to read proto message: unexpected EOF
Failed to read proto message: unexpected EOF
...

Gauge version

Gauge version: 1.0.4
Commit Hash: 3a9a647

Plugins
-------
html-report (4.0.7)
java (0.7.1)
screenshot (0.0.1)
spectacle (0.1.3)
xml-report (0.2.1)

[haroon-sheikh]

Sometimes see this warning instead.

Plugin [Html Report] with pid [200] did not exit after 30.00 seconds. Forcefully killing it.

[haroon-sheikh]

I'm getting a loop of following message thrown at the end of the execution:

[html-report] 2019/02/12 14:21:49 Failed to read proto message: proto: can't skip unknown wire type 6\n
[html-report] 2019/02/12 14:21:49 Failed to read proto message: proto: can't skip unknown wire type 6\n
[html-report] 2019/02/12 14:21:49 Failed to read proto message: proto: can't skip unknown wire type 6\n

[ocary]

On some runs I'm seeing
[html-report] 2019/02/14 15:31:32 Failed to read proto message: proto: can't skip unknown wire type 4
repeated many, many times.

Gauge version: 1.0.4
Commit Hash: 3a9a647

Plugins
-------
html-report (4.0.7)
java (0.7.1)
xml-report (0.2.1)

[zabil]

Looks like this is happening after the upgrade from 4.0.6 to 4.0.7

[haroon-sheikh]

yeah looks like 4.0.7 is having problems with killing itself.

[ocary]

Looks like this is happening after the upgrade from 4.0.6 to 4.0.7

I'm switching back to HTML-report 4.0.6, then will run my regression suite then will keep an eye on console log file sizes, to confirm this is a 4.0.7 issue.

[BugDiver]

@haroon-sheikh @ocary Could you please try to install latest nightlies of gauge and html-report and see if they fix this issue?

[ocary]

@BugDiver -

1. Next week, I'll see what I can do to get a nightly installed in the env that was having issues. 50% chance of being successful due to other limitations.

2. There is an issue with html-report 4.0.7+ with the content that goes into xml-report. Defect opened in xml-report. Failure message not included in XML report. xml-report#16

[alpha1592]

• This issue was there with html-report 4.0.6 as well. i upgraded to 4.0.7 to see if the issue would be resolved. It did not.
• This has happened to me on three separate machines.
• Is this issue due to large number of test scenarios (1200+ in my case) being executed as part of a suite?
• Also, when this issue happens, an hour+ long execution and its results are lost. is there a way where we can salvage the results by re-running the html-report plugin against some raw results or execution history being stored somewhere?

[alpha1592]

any update on this?

[sriv]

I am investigating this. I do see the issue occur intermittently when running on html-report 4.0.7 in a low-spec machine. But this is not consistent enough to yield a possible cause.

With html-report 4.0.6, I haven't been able to see this issue.

@alpha1592 - do you run your specs in parallel?

[alpha1592]

Yes, i usually run the full suite in parallel mode. I have mostly seen this error when running in parallel and a large number of scenarios. However, I have seen this error in single threaded mode as well. This issue has also been seen on two very different hardware specs as well (below). I have never seen this issue when running a spec file here or there through intelliJ. Only seen this error when running from command line outside of IntelliJ. Hope this helps...

in \env\default\default.properties i have enable_multithreading = false

Command to Start the Test Suite (Single) - takes 1 hour to execute
mvn gauge:execute -DspecsDir=specs/

Command to Start the Test Suite (In Parallel) - takes 25 mins to execute
mvn gauge:execute -DspecsDir=specs/ -DinParallel=true -Dnodes=6

Hardware Specs
Server 1 (run only in single mode)

• Windows Server 2012 VM x64
• 2 vCores
• 4 GB RAM

Server 2

• Windows Server 2012 VM x64
• 8 vCores
• 16 GB RAM

Tests

• 35 Specs (Some specs are over 5,000 lines)
• 1,200 Scenarios

[sriv]

@alpha1592 - what is the output of gauge -v on the machine where you see this issue?

[alpha1592]

Gauge version: 1.0.4
Commit Hash: 3a9a647

Plugins
-------
flash (0.0.1)
html-report (4.0.7)
java (0.7.1)
json-report (0.2.2)
screenshot (0.0.1)
spectacle (0.1.3)
xml-report (0.2.1)

Manifest.json

{
  "Language": "java",
  "Plugins": [
    "html-report",
    "flash"
  ]
}

Java Version

java version "1.8.0_191"
Java(TM) SE Runtime Environment (build 1.8.0_191-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode)

[haroon-sheikh]

I'm seeing a similar behaviour when it's a larger set of suites running in parallel.

[sriv]

hi @alpha1592 @haroon-sheikh - can you please try the latest html-report nightly build and see if this is better?

Essentially we implemented a change (ref getgauge/gauge#1239) which allowed gauge to send data to the html-report in chunks. I have disabled this change, since I noticed that the chunks weren't getting through properly in certain cases. And this isn't consistent. I have disabled this capability.

[haroon-sheikh]

I'll try it today and let you know.

[alpha1592]

I'll give it a try...
How is it expected to work now...
will html-report going to create the report as execution is going... or is it done all at the end of the test execution?

[sriv]

html-report is still generated at the end of execution. There needs to be some changes in gauge to enable reports receiving data impromptu.

[nehashri]

@haroon-sheikh @alpha1592 Were you able to give this a try? If this fixes the unexpected EOF issue, we can look at making a html report plugin release.

[bimalviswam]

It started happening when I upgraded from gague 1.0.5 to 1.0.6.

Switched back to gauge 1.0.5 and html-report 4.0.6 and issue does not appear anymore.

[adea11]

I am also now having this issue. It only just starts today after upgrading @getgauge/cli to 1.0.6

Plugins

flash (0.0.1)
html-report (4.0.8)
js (2.3.5)
json-report (0.3.1)
screenshot (0.0.1)
spectacle (0.1.3)
xml-report (0.2.1)

[alpha1592]

I am still on 1.0.5. still having the issue.

[nehashri]

@bimalviswam @adea11 @alpha1592 we will try to fix this issue soon. We have also started to work on #221 to fix this issue in a proper way.

[chuv13]

html-report is fine for me. it's json-report that's producing this:

[haroon-sheikh]

@nehashri Do we have an update on this please. This is happening a lot more with the latest version of gauge. 1.0.5 seems to be more stable.

[chuv13]

[nehashri]

@chuv13 latest json-report is released, can you please see if it fails with the latest too?

[alpha1592]

any updates on this?
Gauge updates have slowed down recently...? any reason why we don't see faster updates?

[zabil]

To keep track of updates please follow https://github.com/orgs/getgauge/projects/6

[savin0ff]

periodically i have the same issue, today i had it again with next configuration:

2019/11/13 03:53:29 Failed to read proto message: unexpected EOF
2019/11/13 03:53:29 Failed to read proto message: unexpected EOF
03:53:29 [Thread-1] INFO config.DefaultHooks - 13.11.2019 03:53:29   ### 'click ...' step started ###
2019/11/13 03:53:29 Failed to read proto message: unexpected EOF
2019/11/13 03:53:29 Failed to read proto message: unexpected EOF
2019/11/13 03:53:29 Failed to read proto message: unexpected EOF
2019/11/13 03:53:29 Failed to read proto message: unexpected EOF
[html-report] 2019/11/13 03:53:29 Failed to read proto message: proto: can't skip unknown wire type 6
[html-report] 2019/11/13 03:53:29 Failed to read proto message: proto: can't skip unknown wire type 6
[html-report] 2019/11/13 03:53:29 Failed to read proto message: proto: can't skip unknown wire type 6
[html-report] 2019/11/13 03:53:29 Failed to read proto message: proto: can't skip unknown wire type 6

openjdk version "1.8.0_222"
OpenJDK Runtime Environment (build 1.8.0_222-8u222-b10-1ubuntu1~18.04.1-b10)
OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode)


Gauge version: 1.0.6
Commit Hash: 2bc49db

Plugins
-------
flash (0.0.1)
html-report (4.0.8)
java (0.7.3)
screenshot (0.0.1)

started using maven plugin with args: -DinParallel=true -Dnodes=2 -Denv=ext -Dtags=regression

may be it's somehow connected with network, our company network is very complex and sometimes internet connection can be lost/switched...
I'm so tired about this problem and thinking about another BDD framework...

[zabil]

@savin0ff can you try downgrading it to 1.0.5 till it's fixed?

[savin0ff]

ok, i'll try to downgrade gauge...and again it happened with -Dnodes=1

[html-report] 2019/11/14 05:36:28 Failed to read proto message: proto: gauge_messages.ImplementationFileGlobPatternResponse: illegal tag 0 (wire type 3)
[html-report] 2019/11/14 05:36:28 Failed to read proto message: proto: gauge_messages.ImplementationFileGlobPatternResponse: illegal tag 0 (wire type 3)
[html-report] 2019/11/14 05:36:28 Failed to read proto message: proto: gauge_messages.ImplementationFileGlobPatternResponse: illegal tag 0 (wire type 3)
2019/11/14 05:36:28 Failed to read proto message: proto: bad wiretype for field gauge_messages.Message.MessageType: got wiretype 2, want 0
2019/11/14 05:36:28 Failed to read proto message: proto: bad wiretype for field gauge_messages.Message.MessageType: got wiretype 2, want 0
2019/11/14 05:36:28 Failed to read proto message: proto: bad wiretype for field gauge_messages.Message.MessageType: got wiretype 2, want 0
2019/11/14 05:36:28 Failed to read proto message: proto: bad wiretype for field gauge_messages.Message.MessageType: got wiretype 2, want 0

[negiDharmendra]

We are working on a fix for this issue as disscused in getgauge/gauge#1476.

[negiDharmendra]

We have pushed some fixes to Gauge, Gauge-Java and html-report to address this issue. Please give it a try and provide your valuable feedback.

Note: You will have to build all of them( Gauge, Gauge-Java and html-report) from source as we have not released them yet.

• Build Gauge from source.
  Prerequisite: Go lang 1.13.4

  run go run build/make.go && go run build/make.go --install

• Build Html-Report from source.
  Prerequisite: Go lang 1.13.4, Gauge

  run go run build/make.go && go run build/make.go --install

• Build Gauge Java from source.

[taplar]

We've been having issues similar to the ones listed here. We were originally getting a type 5 or 6 error. We've tried downgrading the various plugins and gauge install, and now we are back on gauge 1.0.4 java 0.6.9 and we are still getting the EOF error.

So today I started looking into building from source gauge and gauge java, however the environments we run gauge on are VMs which do not have access to the internet, only the intranet, so I have to make distros to test them out.

I've installed NSIS so the --distro option would have access to the makensis executable, however when I try to run this I get the following error:

$ go run build/make.go && go run build/make.go --distro
Command line defined: "PRODUCT_VERSION=1.0.7"
Command line defined: "GAUGE_DISTRIBUTABLES_DIR=D:\Users\***\Repositories\Github\gauge\deploy\gauge-1.0.7-windows.x86_64"
Command line defined: "OUTPUT_FILE_NAME=D:\Users\***\Repositories\Github\gauge\deploy\gauge-1.0.7-windows.x86_64.exe"
Processing config: D:\Users\***\Programs\NSIS\nsisconf.nsh
Processing script file: "build\install\windows\gauge-install.nsi" (ACP)
Error: unterminated string parsing line at macro:_IncludeStrFunction:7
Error in macro _IncludeStrFunction on macroline 7
!include: error in script: "EnvVarUpdate.nsh" on line 49
Error in script "build\install\windows\gauge-install.nsi" on line 21 -- aborting creation process
panic: exit status 1

goroutine 1 [running]:
main.runProcess(0x6ebcf6, 0xc, 0xc000097dd8, 0x4, 0x4)
        D:/Users/***/Repositories/Github/gauge/build/make.go:64 +0x19c
main.createWindowsInstaller()
        D:/Users/***/Repositories/Github/gauge/build/make.go:280 +0x4ca
main.createWindowsDistro()
        D:/Users/***/Repositories/Github/gauge/build/make.go:268 +0x3c
main.createDistro()
        D:/Users/***/Repositories/Github/gauge/build/make.go:263 +0x95
main.createGaugeDistributables(0xc000016900)
        D:/Users/***/Repositories/Github/gauge/build/make.go:256 +0x1af
main.main()
        D:/Users/***/Repositories/Github/gauge/build/make.go:190 +0x11c
exit status 2

Also as an additional question, it seems these issues are related to changes around screenshots? If so, would turning off screenshots prevent this issue until a fix has been officially released?

[negiDharmendra]

Notes for testing: Make sure screenshots are available in the report for the following conditions.

• When Gauge, runners, and HTML-Report are installed from the Github master branch.
• When Gauge is installed from the Github master branch and runners and HTML-Report are the released one.

Note: Screenshots will not be available in the report when one of them( runners, HTML-Report) is from the Github master branch or released one.

New API to implement custom screenshots.
We have introduced a new custom_screenshot_writer API to take custom screenshots. While implementing the new API user should take care of capturing and writing the screenshot into the location configured by screenshots_dir env variable.

• custom_screenshot_writer for java
• custom_screenshot_writer for python
• custom_screenshot_writer for ruby
• custom_screenshot_writer for js

[Debashis9012]

This issue has been verified and found fixed against the below versions:

Gauge version: 1.0.7
Commit Hash: 50fb6484

Plugins
-------
html-report (4.0.9)
java (0.7.4)

[haroon-sheikh]

@Debashis9012 When is 1.0.7 planned to be released?

[Debashis9012]

@haroon-sheikh Most probably we will release gauge 1.0.7 by next week.

[Debashis9012]

Reopening it as we need to test gauge-python and gauge-ruby runners and also we need to update the gauge documentation for custom_screenshot_writer

[coding-lama]

Hi folks, any news on the gauge 1.0.7 release?

[zabil]

On the last mile of testing, the latest changes. This should come out by next week.

[sriv]

An update: We detected some issues with the recent changes that sometimes messes up multi threaded parallel execution.

This is holding up the release(s). We are working on this.

[jonathangiber]

Still getting EOF failed to read proto with the following versions

Your Environment Information -----------
linux, 1.0.7, ed7b4fd6
html-report (4.0.9), java (0.7.3), spectacle (0.1.4), xml-report (0.2.3)
.......................

Running in 48 parallel

[sriv]

hi @jonathangiber - please update gauge-java to 0.7.4 and try.