JulianJaffePinterest edited a comment on pull request #10920:
URL: https://github.com/apache/druid/pull/10920#issuecomment-877498085


   @samarthjain do you know who maintains the Travis checks on PRs? I'm trying 
to figure out what's happening with the intelliJ inspections test (it's the 
only [failing 
check](https://app.travis-ci.com/github/apache/druid/jobs/523127037) for most 
of my recent builds). The errors are
   ```[ERROR] pom.xml:1790 -- Element forkCount is not allowed here #loc
   [ERROR] pom.xml:1790 -- Element forkCount is not allowed here #loc
   [ERROR] pom.xml:1790 -- Cannot resolve symbol 'forkCount' #loc
   [ERROR] pom.xml:1790 -- Cannot resolve symbol 'forkCount' #loc
   [ERROR] pom.xml:1791 -- Element reuseForks is not allowed here #loc
   [ERROR] pom.xml:1791 -- Element reuseForks is not allowed here #loc
   [ERROR] pom.xml:1791 -- Cannot resolve symbol 'reuseForks' #loc
   [ERROR] pom.xml:1791 -- Cannot resolve symbol 'reuseForks' #loc
   ```
   which are args being passed to the surefire plugin when the parallel-test 
profile is set. I haven't made any changes to that profile (or to the base pom 
beyond adding the new module), and I've even removed the surefire configuration 
changes I made in the spark extension, but the error remains. I'm pretty sure 
it's erroneous, since all the other checks are able to execute maven commands. 
Googling hasn't turned up much beyond a suggestion to check the bundled xml 
schema used by the inspector so it would be great to talk to someone who knows 
a little more about what's happening under the hood for this check
   
   Follow up: I solved this problem by explicitly setting the surefire version 
in the plugin section where the complaining configuration lived, even though 
the version was already set in the plugin management section.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to