Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Integration tests are regularly failing on CI #12689

Closed
philwebb opened this issue Mar 30, 2018 · 4 comments
Closed

Integration tests are regularly failing on CI #12689

philwebb opened this issue Mar 30, 2018 · 4 comments
Labels
type: task A general task
Milestone
2.0.1

Comments

@philwebb
Copy link
Member

See https://ci.spring.io/teams/spring-boot/pipelines/spring-boot/jobs/build/builds/1093 for example.

Hijack shows logs like this:

# Created on 2018-03-29T23:47:49.343
Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream '#   http://bugreport.java.com/bugreport/crash.jsp'.
java.lang.IllegalArgumentException: Stream stdin corrupted. Expected comma after third character in command '#   http://bugreport.java.com/bugreport/crash.jsp'.
	at org.apache.maven.plugin.surefire.booterclient.output.ForkClient$OperationalData.<init>(ForkClient.java:506)
	at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.processLine(ForkClient.java:212)
	at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:179)
	at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:88)
	at java.lang.Thread.run(Thread.java:748)


# Created on 2018-03-29T23:47:49.344
Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream '# The crash happened outside the Java Virtual Machine in native code.'.
java.lang.IllegalArgumentException: Stream stdin corrupted. Expected comma after third character in command '# The crash happened outside the Java Virtual Machine in native code.'.
	at org.apache.maven.plugin.surefire.booterclient.output.ForkClient$OperationalData.<init>(ForkClient.java:506)
	at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.processLine(ForkClient.java:212)
	at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:179)
	at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:88)
	at java.lang.Thread.run(Thread.java:748)


# Created on 2018-03-29T23:47:49.344
Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream '# See problematic frame for where to report the bug.'.
java.lang.IllegalArgumentException: Stream stdin corrupted. Expected comma after third character in command '# See problematic frame for where to report the bug.'.
	at org.apache.maven.plugin.surefire.booterclient.output.ForkClient$OperationalData.<init>(ForkClient.java:506)
	at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.processLine(ForkClient.java:212)
	at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:179)
	at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:88)
	at java.lang.Thread.run(Thread.java:748)


# Created on 2018-03-29T23:47:49.344
Corrupted STDOUT by directly writing to native stream in forked JVM 1. Stream '#'.
java.lang.IllegalArgumentException: Stream stdin corrupted. Expected comma after third character in command '#'.
	at org.apache.maven.plugin.surefire.booterclient.output.ForkClient$OperationalData.<init>(ForkClient.java:506)
	at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.processLine(ForkClient.java:212)
	at org.apache.maven.plugin.surefire.booterclient.output.ForkClient.consumeLine(ForkClient.java:179)
	at org.apache.maven.plugin.surefire.booterclient.output.ThreadedStreamConsumer$Pumper.run(ThreadedStreamConsumer.java:88)
	at java.lang.Thread.run(Thread.java:748)
@philwebb philwebb added this to the 2.0.x milestone Mar 30, 2018
@philwebb philwebb added the type: task A general task label Mar 30, 2018
@philwebb
Copy link
Member Author

Also seeing a lot of http://maven.apache.org/surefire/maven-failsafe-plugin/faq.html#corruptedstream

@philwebb philwebb modified the milestones: 2.0.x, 2.0.1 Mar 30, 2018
philwebb added a commit that referenced this issue Mar 30, 2018
@philwebb
Attempt to fix server test CI failures
3278242 
Switch surefire configuration so that forking isn't used. This seems to
prevent the "Corrupted STDOUT by directly writing to native stream"
errors and will hopefully reduce failures on the CI server.

See gh-12689
philwebb added a commit that referenced this issue Mar 30, 2018
@philwebb
Second attempt to fix server test CI failures
69cbf13 
Switch process redirection off and instead consume streams
and copy to System.out/System.err.

See gh-12689
mbhave added a commit that referenced this issue Apr 3, 2018
@mbhave
Don't force snapshot update for integration tests
fa4a3ab 
See if that fixes intermittent NoClassDefFoundError.

See gh-12689
@philwebb
Copy link
Member Author

philwebb commented Apr 5, 2018

Seems to be generally a bit better

screen shot 2018-04-04 at 8 48 57 pm

@philwebb philwebb closed this as completed Apr 5, 2018
@mbhave
Copy link
Contributor

mbhave commented Apr 5, 2018

Some of it might be because we moved away from snapshots right before the release but we can reopen if it goes back to being red.

@philwebb
Copy link
Member Author

philwebb commented Apr 6, 2018

Yeah, I'm not totally convinced correlation implies causation

@bclozel bclozel mentioned this issue Apr 4, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: task A general task
Projects
None yet
Milestone
2.0.1
Development

No branches or pull requests
2 participants
@philwebb @mbhave