swagger-api / swagger-api/swagger-codegen

[Java Spring Boot] - Issue with circleci CI tests for spring-mvc

Open
#7,862 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Mustache
Stars
17.8k
Forks
6k
PR merge metrics
No merged PRs in 30d

Description

Description

There seems to be an issue with the circle CI tests for spring-mvc. On multiple pull requests I've observed an issue where the test step mvn -q verify -Psamples fails.

https://circleci.com/gh/swagger-api/swagger-codegen/4228?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
https://circleci.com/gh/swagger-api/swagger-codegen/4227?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
https://circleci.com/gh/swagger-api/swagger-codegen/4173?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
https://circleci.com/gh/swagger-api/swagger-codegen/4054?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
...

Error seems to be:

[ERROR] Failed to execute goal org.eclipse.jetty:jetty-maven-plugin:9.2.15.v20160210:start (start-jetty) on project swagger-spring-mvc-j8-localdatetime: Failure: ShutdownMonitorThread already started -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :swagger-spring-mvc-j8-localdatetime

Swagger-codegen version

2.4.0-SNAPSHOT

Swagger declaration file content or url

N/A

Command line used for generation

mvn -q verify -Psamples

Steps to reproduce
  1. Submit PR to master.
Related issues/PRs
Suggest a fix/enhancement

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the CircleCI failure with mvn -q verify -Psamples, focusing on the spring-mvc sample that reports ShutdownMonitorThread already started. Review the Maven verification setup and the swagger-spring-mvc-j8-localdatetime sample named in the error. Done means the samples verification completes successfully without the Jetty shutdown-monitor error.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring-boot
Domain
backend, ci-cd, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.