Community
Participate
Working Groups
The daily builds are failing because of problems in SWT build input job. full log: https://ci.eclipse.org/releng/job/SWT-Increment_if_needed/618/console relevant error message get_version: [script] Warning: Nashorn engine is planned to be removed from a future JDK release [echo] Version=4950r3; New=4950r4; New comma_ver=4,950,4,0 get_new_tag: [script] Warning: Nashorn engine is planned to be removed from a future JDK release BUILD FAILED /home/jenkins/agent/workspace/SWT-Increment_if_needed/eclipse.platform.swt/bundles/org.eclipse.swt/buildSWT.xml:389: Unable to determine new tag
New Gerrit change created: https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/190197
SWT build input tagging has reached the upper limit of 'z'. We tried a SWT build input with force native but it didn't worked out: https://ci.eclipse.org/releng/view/SWT%20Natives%20without%20chromium/job/SWT-Increment_if_needed/622/console We are investigating to update the SWT tagging logic via build script or manually.
Gerrit change https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/190197 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=907792290b41e6823b66faa31aab7ea7269d1d1c
Windows machine seems offline: https://ci.eclipse.org/releng/view/SWT%20Natives%20without%20chromium/job/win32_x86_64/79/console Raised gitlab issue: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/827
(In reply to Niraj Modi from comment #4) > Windows machine seems offline: > https://ci.eclipse.org/releng/view/SWT%20Natives%20without%20chromium/job/ > win32_x86_64/79/console > > Raised gitlab issue: > https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/827 Windows machine is up and SWT build input worked now. Triggered below Eclipse IBuild: I20220131-0700
Re-triggered Eclipse IBuild: 20220131-0800
(In reply to Niraj Modi from comment #6) > Re-triggered Eclipse IBuild: > 20220131-0800 There was no nightly build today. Is the job disabled now or just not triggered again?
(In reply to Andrey Loskutov from comment #7) > (In reply to Niraj Modi from comment #6) > > Re-triggered Eclipse IBuild: > > 20220131-0800 > > There was no nightly build today. Is the job disabled now or just not > triggered again? Checked with Sravan on this, we decided to re-open below gitlab issue: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/824
(In reply to Niraj Modi from comment #6) > Re-triggered Eclipse IBuild: > 20220131-0800 Since Eclipse IBuild ran successfully, closing. Raised bug 578503 to improve the SWT's build tagging logic.
