-
Notifications
You must be signed in to change notification settings - Fork 874
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.
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
temp test setup: try to migrate the LSP job #4921
Conversation
distribution: 'zulu' | ||
|
||
- name: java/java.lsp.server | ||
run: ant $OPTS -Dcluster.config=java -Djavac.compilerargs=-nowarn -Dbuild.compiler.deprecation=false -f java/java.lsp.server test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure if it matters for this test. But maybe inline the $OPTS here. Since I forgot a '-' where it is declared which causes yaml to add a newline at the end of the list.
OPTS: >-
-Dmetabuild.jsonurl=https://raw.githubusercontent.com/apache/netbeans-jenkins-lib/master/meta/netbeansrelease.json
-Dtest-unit-sys-prop.ignore.random.failures=true
would be correct (note the -
after >
)
it is fixed in the original PR, forgot to add it here.
0f0ccfb
to
3627ec3
Compare
This is really weird. I think I've found the culprit, but WHY the thing happens is not (yet) obvious. The
But WHY has been And from the
is also strange: as if the |
clearly touching any of the source after |
would it help to upload the workspace for inspection and then diff (e.g with meld) the build before and after test? Maybe there is more wrong which could give clues what is going on there. - name: Prepare Artifact
run: tar -I 'zstd -9 -T0' -cf /tmp/ws.tar.zst --exclude ".git" .
- name: Upload Workspace
uses: actions/upload-artifact@v3
with:
name: ws
path: /tmp/ws.tar.zst
retention-days: 5
if-no-files-found: error |
Interesting -- how would I fetch that artifact ? |
f20dc4a
to
f4cc7a9
Compare
So - cause found. This is a combination of 3 participants:
As JDK8 is itypically not reinstalled each time on developer's machine - and if it was, it would be through some conventional Then, The tests were finally run, but the required |
Relevant parts from the log: Cause of the actual test failure:
Files present at the end of the compilation:
Files present at the time of test execution:
There's no Why the
Because of
Why the
I can fix this bug. |
207ee93
to
91e24ce
Compare
I've force-pushed clean up changes + fixes. |
scroll down in the summary page of the workflow run (which didn't set
interesting! We could setup all JDKs first, then use their env vars, since they all should set different vars. However, the regular workflow would build in a primary job which produces the tar artifact as described above, then this test would run in a secondary job on a different JDK. This means each job would only setup one JDK. So this situation of setting up two JDKs in the same job should not occur outside of the job we did setup for this debugging PR here. (but we have other places which do that - so this is good to know) Also keep in mind that this is the first thing I tried. I simply added the LSP job to the existing pipeline. Interesting that the job intended for debugging purposes added another problem to the mix :)
i was afraid that something like this could happen. All the hooks and wedges added a lot of non standard behavior over the years. I would suggest the following: lets extract all java changes from this PR into a fresh PR and get this PR in. Once its in, I update #4817 so that it is using a regular secondary job for the LSP testing - just like everything else. would this be ok? amazing work @sdedic, thanks a lot! |
this is just a test setup which tries to run the LSP job on github without running anything else.
not intended to be merged, only for debugging.