Issue #7190: remove deprecated setClassLoader methods#7778
Conversation
44e9aac to
1034af4
Compare
|
Same problem in pgjdbc project Did you send PR to them ? |
|
PR was sent to pgjdbc/pgjdbc#1726 . |
|
New failure @nmancus1 , please review at https://github.com/checkstyle/checkstyle/blob/master/.ci/wercker.sh all execution points with prefix "no-error" and create PR for such projects. |
|
@nmancus1 When providing this update PRs to external groups, please add some context to the PR information so they know why we need this change accepted. See some of my previous PRs as examples: |
|
@rnveach How can I generate the failing regression locally, so that I can provide that output in the PRs I'm submitting (similar to your example)? PR's sent( I'll update as I make them ): |
|
CI is simply execute single command line that we can execute on linux local, example - Line 88 in c7ae67e same commands should work on your linux local laptop, execution if from repo root directory. |
|
@nmancus1 , please remove from commit not your changes. apex-core did not update for 3 years, according to github https://github.com/apache/apex-core , I did a fork https://github.com/checkstyle/apex-core , @nmancus1 , please send PR to our fork, please update https://github.com/checkstyle/checkstyle/blob/master/.ci/wercker.sh#L103 to use checkstyle's fork. |
I'm lazy, I wanted to run all of the commands via script, without writing a new one :)
I'll get this fixed up this today. |
Just copy single command from CI config, like |
I understand this and want something similar so I can execute same CI commands locally on my checkstyle VM server which I use for regression reports. The issue is going to be keeping it in-synch with the YMLs as CI can change regulary. For now, you will have to create such a script manually. I would move this type of discussion to a new issue if you want to continue to add it to checkstyle in some form. |
1034af4 to
7dffd09
Compare
|
@romani I have ran all of the wercker scripts locally, and none are failing for me, but CI still fails when I push. Can you let me know what is failing since I can't view the logs? |
|
Wercker is failing on orekit We need to update checkout commit in wercker.sh. |
Without seeing what you did, Wercker is special in that it has a pre-execution command before each command run. https://github.com/checkstyle/checkstyle/blob/master/wercker.yml#L58 |
@romani I am struggling to get apex past
Should I submit a PR for this as 'minor"? |
Verify will run the tests of the repo. For regression, we don't want any tests being run. Please look at the original command used for apex. https://github.com/checkstyle/checkstyle/blob/master/.ci/wercker.sh#L105 |
So, just to be clear, it is ok to submit a PR to checkstyle's apex repo that will not pass |
|
It is the 3 year old project @romani mentioned. If they have failing tests on a clean master, then you would be wasting your time on fixing a project that is not even maintained by the owners. If it was an active project, yes, the PR sent to them should pass their CI and we could ask their maintainers for their help resolving any CI issues. None of us know their project in any details to know how to help. From our end, these projects are only used for regression. We just need to make sure we have a command to run regression on them and ensure a stable build, only for regression purposes. We always skip tests on these projects to speed up execution time and because we are not involved in testing their own project. Just their checkstyle portion. |
|
Ok. Thanks for explaining. |
|
@nmancus1 , apex PR is merged - https://github.com/checkstyle/apex-core/pull/1 |
PR is here: #7786 |
Orekit was merged, but we specific commit in regression because of their unstable CI. This needs to be updated for the CI in this PR to pass. |
Then why does methods distance in wercker fail, which looks because its maven-checkstyle-plugin was not updated to the newest version? |
I failed to |
|
Please reconfirm the others with the clean install too. |
|
@rnveach Can we add arguments to maven to specify the correct plugin version? |
|
Wercker is restarted, Travis is failing on spelling from Sha commit value. |
I am not seeing your issue. Why can't you update the version number at https://github.com/checkstyle/contribution/blob/fdc04f5789658cf002832c6eb5ea33ccd1c5b09a/checkstyle-tester/pom.xml#L14 ? |
Lack of sleep and inexperience. Thanks for pointing that out. PR submitted. |
86e9c7c to
980a3b0
Compare
|
What should I do about htmlunit: #7778 (comment) ? I thought it would be easier to move to GitHub, but if that complicates things, I'll submit a PR over there, too, and stick with SVN. |
|
Update to contribution merged. Wecker doesn't need a restart as it hasn't started yet. |
Have they fully switched to Github and put SVN in a read only state? If so, switch to Github should be in this PR unless @romani has a complaint since it now seems it is directly tied to their maven version. Either this PR or another, you are relied on this change for this PR. |
This doesn't look like it is connected to this issue. If so, move this to another PR so it can be merged faster. |
.ci/wercker.sh
Outdated
| mvn -e compile checkstyle:check -Dcheckstyle.version=${CS_POM_VERSION} | ||
| checkout_from https://github.com/HtmlUnit/htmlunit | ||
| cd .ci-temp/htmlunit | ||
| mvn -e compile -DskipTests=true -Dcheckstyle.version=${CS_POM_VERSION} |
There was a problem hiding this comment.
This command is incomplete. We need more than a compile. Please see the pervious command and commands from other places. I don't see why actual command would change since they just moved from SVN to Git.
It appears so: https://github.com/HtmlUnit/htmlunit/releases/tag/2.33 I'm not sure how to determine if their SVN is in a read only state, but there hasn't been any commits to SVN since 2018 that I can see. I have reverted 599231b . I need to uncomment this block of script, right? #7778 (comment). What else do I need to take care of so that this can get merged? Do you want me to squash all commits besides ef07590 and 09f466b? |
Since its been 2 years and if the Git repository is still active, then it seems highly likely that SVN isn't used anymore and so the commit must remain here. If it is not literally read only, then if usage seems that way, then it is good enough for me. They won't push a commit to it after 2 years of abandoning it.
#7778 (comment) #7778 (comment) Any commits remaining that are attached to this issue must have the issue in the commit message. IE: Make CI happy. We will only merge when CI is green. I am not talking about random failures like timeout issues which we see happen from time to time. I am talking full on errors, violations, etc... Don't forget to rebase on latest master.
No. Leave them all separate. |
1df00c6 to
9f3a670
Compare
| checkout_from https://github.com/HtmlUnit/htmlunit | ||
| cd .ci-temp/htmlunit | ||
| mvn -e compile checkstyle:check -Dcheckstyle.version=${CS_POM_VERSION} | ||
| cd ../ |
There was a problem hiding this comment.
cd changed from cd htmlunit to cd .ci-temp/htmlunit. Since we are cding into a second directory, don't we need to cd out an additional directory too?
There was a problem hiding this comment.
Actually, we are deleting the htmlunit folder so we should only go out 1. Please double confirm. I am seeing out projects with a double cd and I think atleast 1 might be wrong.
There was a problem hiding this comment.
What I have is correct, there are other errors in this file, like what you've mentioned. There are a few that do that, but they end up living in .ci-temp and never getting deleted, just updated, which I guess could be either good or bad, but the intended action of rm'ing the directories isn't carried out.
There was a problem hiding this comment.
Would you like me to tidy this file up along with the hipparchus directory removal and submit as one PR?
There was a problem hiding this comment.
Yes, feel free to make another PR ensure the temp folder is tidied up. Not in this PR. I was asking @romani since he knows linux better than me: can we remove the f option for rm -rf but not make it prompt? This way it will complain if directory doesn't exist and catch this problem for us.
http://man7.org/linux/man-pages/man1/rm.1.html
There was a problem hiding this comment.
In my experience (I have much more with Linux than with programming), only the -i flag will make it prompt when rm'ing, despite what the man page says. Since it is a git repo though, it might be necessary to use -f because of the protected files. I'll take a look tonight.
There was a problem hiding this comment.
Let's move all noticed points to improve to separate issue/PRs .
It is better to merge this PR sooner.
There was a problem hiding this comment.
@nmancus1 Do you still plan to do this?
There was a problem hiding this comment.
@rnveach yes, I completed it today. I just wanted to run through and test each one again before submitting PR.

Issue #7190: remove deprecated setClassLoader methods