Bugzilla – Full Text Bug Listing
|
Description
Lakshmi P Shanmugam
@Guillermo, This fails on both Mac and Windows, didn't try on Linux. Please take a look. i don't see how this could work... i download this: https://download.eclipse.org/eclipse/downloads/drops4/I20200722-0610/download.php?dropFile=eclipse-SDK-I20200722-0610-win32-x86_64.zip if i look into the plugins i do see: org.eclipse.swt.browser.chromium.win32.win32.x86_64_3.115.0.v20200722-1012.jar But that is the small native wrapper right? Where is the com.make.chromium.cef.win32.win32.x86_64_0.4.0.202005172227 (or the same kind of thing?) that is about 55MB? (In reply to Johan Compagner from comment #2) > i don't see how this could work... > > i download this: > > https://download.eclipse.org/eclipse/downloads/drops4/I20200722-0610/ > download.php?dropFile=eclipse-SDK-I20200722-0610-win32-x86_64.zip > > if i look into the plugins i do see: > > org.eclipse.swt.browser.chromium.win32.win32.x86_64_3.115.0.v20200722-1012. > jar > > But that is the small native wrapper right? > > Where is the > > com.make.chromium.cef.win32.win32.x86_64_0.4.0.202005172227 > > (or the same kind of thing?) > > that is about 55MB? The cef binaries are not shipped with Eclipse. They need to be downloaded by the user from the chromium site or installed from a p2 repo. Links are in Bug 549585 - https://bugs.eclipse.org/bugs/show_bug.cgi?id=549585#c16 (In reply to Lakshmi Shanmugam from comment #1) > @Guillermo, > This fails on both Mac and Windows, didn't try on Linux. Please take a look. Hi @Lakshmi and @Niraj This seems to got broken here: https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/166513 By removing the version from the name in the cargo lib. The issue is that later the swt jni lib is linked to it, and then the cargo lib renamed with the version, so the linking of the swt jni lib gets broken. Then its partially reverted here: https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/166545 But not entirely. I don't known the reason for these changes so reverting to the original state may not be desired? Maybe if you can comment on the problems you had I can try to provide a fix. BTW, there was and code added to handle these version increments automatically: https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/159486/17/bundles/org.eclipse.swt/buildSWT.xml#336 Please comment on the issues you saw before that led to these changes, so I can help with the fixes. Many thanks for all the effort. New Gerrit change created: https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/166686 For Mac, there are these two files that are required and are missing in the git repo: https://git.eclipse.org/r/c/platform/eclipse.platform.swt.binaries/+/159487/11/bundles/org.eclipse.swt.browser.chromium.cocoa.macosx.x86_64/chromium-3071/chromium_subp-4936r6.app/Contents/PkgInfo https://git.eclipse.org/r/c/platform/eclipse.platform.swt.binaries/+/159487/11/bundles/org.eclipse.swt.browser.chromium.cocoa.macosx.x86_64/chromium-3071/chromium_subp-4936r6.app/Contents/Info.plist Those were removed in this commit: https://git.eclipse.org/c/platform/eclipse.platform.swt.binaries.git/commit/?id=d3a32985f057cf50ef33d1a2d8ba06b4d0e112f7 Gerrit change https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/166686 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=b95adfc813d504c9566038b7fc88fa09772d19cf New Gerrit change created: https://git.eclipse.org/r/c/platform/eclipse.platform.swt.binaries/+/166688 (In reply to Guillermo Zunino from comment #6) > For Mac, there are these two files that are required and are missing in the > git repo: > > https://git.eclipse.org/r/c/platform/eclipse.platform.swt.binaries/+/159487/ > 11/bundles/org.eclipse.swt.browser.chromium.cocoa.macosx.x86_64/chromium- > 3071/chromium_subp-4936r6.app/Contents/PkgInfo > > https://git.eclipse.org/r/c/platform/eclipse.platform.swt.binaries/+/159487/ > 11/bundles/org.eclipse.swt.browser.chromium.cocoa.macosx.x86_64/chromium- > 3071/chromium_subp-4936r6.app/Contents/Info.plist > > Those were removed in this commit: > https://git.eclipse.org/c/platform/eclipse.platform.swt.binaries.git/commit/ > ?id=d3a32985f057cf50ef33d1a2d8ba06b4d0e112f7 Thanks Guillermo, looks like this got removed by the build job. I've fixed it now. (In reply to Guillermo Zunino from comment #4) > (In reply to Lakshmi Shanmugam from comment #1) > > @Guillermo, > > This fails on both Mac and Windows, didn't try on Linux. Please take a look. > > Hi @Lakshmi and @Niraj > > This seems to got broken here: > https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/166513 > > By removing the version from the name in the cargo lib. The issue is that > later the swt jni lib is linked to it, and then the cargo lib renamed with > the version, so the linking of the swt jni lib gets broken. > > > Then its partially reverted here: > https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/166545 > > But not entirely. > > > I don't known the reason for these changes so reverting to the original > state may not be desired? Maybe if you can comment on the problems you had I > can try to provide a fix. > > BTW, there was and code added to handle these version increments > automatically: > https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/159486/17/ > bundles/org.eclipse.swt/buildSWT.xml#336 > > Please comment on the issues you saw before that led to these changes, so I > can help with the fixes. > > Many thanks for all the effort. Hi Guillermo, Thanks for looking into this. We removed the version from Cargo.toml since it was not being updated on version change and was causing build failures. The actual problem was that old version in the file was not changed after rebase, so subsequent runs were not updating the file. Same for chromium.properties. We fixed the properties file yesterday. Cargo.toml is fixed now, we will start a new build. Gerrit change https://git.eclipse.org/r/c/platform/eclipse.platform.swt.binaries/+/166688 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.swt.binaries.git/commit/?id=6d97aa321c1d1caf1c9d3cc275e3f03424f7d343 New Gerrit change created: https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/166690 Gerrit change https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/166690 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=504f1fc675f68e03693097550591c1228b1c81fa New Gerrit change created: https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/166702 Gerrit change https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/166702 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=05c2e84f05d1e1f6fcaab652264e84f9502bf23f New Gerrit change created: https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/166728 Gerrit change https://git.eclipse.org/r/c/platform/eclipse.platform.swt/+/166728 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=c97278ba22cb39aae72c4543f105b36a9257c6e2 @Guillermo, The Eclipse build [1] fails during notarization of the Eclipse SDK with this error: path\": \"eclipse-SDK-I20200723-1030-macosx-cocoa-x86_64-8555742938851320738.dmg/Eclipse.app/Contents/Eclipse/plugins/org.eclipse.swt.browser.chromium.cocoa.macosx.x86_64_3.115.0.v20200723-1410.jar/chromium-3071/chromium_subp-4936r10.app/Contents/MacOS/chromium_subp\",\n \"message\": \"The signature of the binary is invalid.\ I also manually checked the signature of MacOS/chromium_subp in the binaries repo on mac using codesign -v chromium_subp I get this error: chromium_subp: code has no resources but signature indicates they must be present Not sure what is the issue. May be a Resources folder is required? [1] Eclipse build console log - https://ci.eclipse.org/releng/job/I-build-4.17/99/console [2] SWT native job where signing of the executables happens - https://ci.eclipse.org/releng/job/1-SWT-Increment_if_needed_chromium/configure (In reply to Lakshmi Shanmugam from comment #18) > @Guillermo, > The Eclipse build [1] fails during notarization of the Eclipse SDK with this > error: > > path\": > \"eclipse-SDK-I20200723-1030-macosx-cocoa-x86_64-8555742938851320738.dmg/ > Eclipse.app/Contents/Eclipse/plugins/org.eclipse.swt.browser.chromium.cocoa. > macosx.x86_64_3.115.0.v20200723-1410.jar/chromium-3071/chromium_subp-4936r10. > app/Contents/MacOS/chromium_subp\",\n \"message\": \"The signature of > the binary is invalid.\ > > I also manually checked the signature of MacOS/chromium_subp in the binaries > repo on mac using > codesign -v chromium_subp > I get this error: chromium_subp: code has no resources but signature > indicates they must be present > > Not sure what is the issue. May be a Resources folder is required? > > > [1] Eclipse build console log - > https://ci.eclipse.org/releng/job/I-build-4.17/99/console > [2] SWT native job where signing of the executables happens - > https://ci.eclipse.org/releng/job/1-SWT-Increment_if_needed_chromium/ > configure I'll take a look. (In reply to Guillermo Zunino from comment #19) > (In reply to Lakshmi Shanmugam from comment #18) > > @Guillermo, > > The Eclipse build [1] fails during notarization of the Eclipse SDK with this > > error: > > > > path\": > > \"eclipse-SDK-I20200723-1030-macosx-cocoa-x86_64-8555742938851320738.dmg/ > > Eclipse.app/Contents/Eclipse/plugins/org.eclipse.swt.browser.chromium.cocoa. > > macosx.x86_64_3.115.0.v20200723-1410.jar/chromium-3071/chromium_subp-4936r10. > > app/Contents/MacOS/chromium_subp\",\n \"message\": \"The signature of > > the binary is invalid.\ > > > > I also manually checked the signature of MacOS/chromium_subp in the binaries > > repo on mac using > > codesign -v chromium_subp > > I get this error: chromium_subp: code has no resources but signature > > indicates they must be present > > > > Not sure what is the issue. May be a Resources folder is required? > > > > > > [1] Eclipse build console log - > > https://ci.eclipse.org/releng/job/I-build-4.17/99/console > > [2] SWT native job where signing of the executables happens - > > https://ci.eclipse.org/releng/job/1-SWT-Increment_if_needed_chromium/ > > configure > > I'll take a look. Thanks. Opened Bug 565506. @Guillermo, Tried latest Eclipse IBuild on Windows: https://download.eclipse.org/eclipse/downloads/drops4/I20200723-1800/ On Win10 BrowserExample with Eclipse SWT Chromium fragment jar "org.eclipse.swt.browser.chromium.win32.win32.x86_64_3.115.0.v20200723-2026.jar" in the classpath, leads to below exception: --------------------------------------------------------------------------- Exception in thread "main" java.lang.SecurityException: class "org.eclipse.swt.browser.ChromiumImpl"'s signer information does not match signer information of other classes in the same package at java.lang.ClassLoader.checkCerts(ClassLoader.java:898) at java.lang.ClassLoader.preDefineClass(ClassLoader.java:668) at java.lang.ClassLoader.defineClass(ClassLoader.java:761) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:468) at java.net.URLClassLoader.access$100(URLClassLoader.java:74) at java.net.URLClassLoader$1.run(URLClassLoader.java:369) at java.net.URLClassLoader$1.run(URLClassLoader.java:363) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:362) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:264) at org.eclipse.swt.browser.BrowserFactory.createChromium(BrowserFactory.java:34) at org.eclipse.swt.browser.BrowserFactory.createWebBrowser(BrowserFactory.java:25) at org.eclipse.swt.browser.Browser.<init>(Browser.java:96) at org.eclipse.swt.examples.browserexample.BrowserExample.<init>(BrowserExample.java:74) at org.eclipse.swt.examples.browserexample.BrowserExample.main(BrowserExample.java:355) With the latest I-build [1], Chromium style browser launches on Mac. Tested both eclipse fragments and standalone swt-chromium.jar. [1] - https://download.eclipse.org/eclipse/downloads/drops4/I20200724-0600/ (In reply to Niraj Modi from comment #21) > @Guillermo, > Tried latest Eclipse IBuild on Windows: > https://download.eclipse.org/eclipse/downloads/drops4/I20200723-1800/ > > On Win10 BrowserExample with Eclipse SWT Chromium fragment jar > "org.eclipse.swt.browser.chromium.win32.win32.x86_64_3.115.0.v20200723-2026. > jar" in the classpath, leads to below exception: > --------------------------------------------------------------------------- > Exception in thread "main" java.lang.SecurityException: class @Guillermo, On Win10, with latest Eclipse IBuild, we got rid of above security error: https://download.eclipse.org/eclipse/downloads/drops4/I20200724-0600/ On Win10, now getting below error while launching BrowserExample: [0724/184959.790:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process. Short of ideas on this error, can you please look into this ? (In reply to Niraj Modi from comment #23) > (In reply to Niraj Modi from comment #21) > > @Guillermo, > > Tried latest Eclipse IBuild on Windows: > > https://download.eclipse.org/eclipse/downloads/drops4/I20200723-1800/ > > > > On Win10 BrowserExample with Eclipse SWT Chromium fragment jar > > "org.eclipse.swt.browser.chromium.win32.win32.x86_64_3.115.0.v20200723-2026. > > jar" in the classpath, leads to below exception: > > --------------------------------------------------------------------------- > > Exception in thread "main" java.lang.SecurityException: class > > @Guillermo, > On Win10, with latest Eclipse IBuild, we got rid of above security error: > https://download.eclipse.org/eclipse/downloads/drops4/I20200724-0600/ > > On Win10, now getting below error while launching BrowserExample: > [0724/184959.790:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to > launch GPU process. > > Short of ideas on this error, can you please look into this ? Niraj, see my comment here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=549585#c115 I'm running in windows with: java -classpath "org.eclipse.swt.examples_3.106.1000.v20200611-1332.jar;swt.jar;swt-chromium.jar;com.make.chromium.cef.win32.win32.x86_64_0.4.0.202005172227.jar" -Dorg.eclipse.swt.browser.DefaultType=chromium org.eclipse.swt.examples.browserexample.BrowserExample cef jar from (http://dl.maketechnology.io/chromium-cef/rls/repository/plugins/com.make.chromium.cef.win32.win32.x86_64_0.4.0.202005172227.jar) I don't got any error and chromium runs fine. This is Windows 10. I tested with java 8 and java 11. Please remove ~/.swt. Maybe there are some old files wrong there from previous attempts. (In reply to Niraj Modi from comment #23) > (In reply to Niraj Modi from comment #21) > > @Guillermo, > > Tried latest Eclipse IBuild on Windows: > > https://download.eclipse.org/eclipse/downloads/drops4/I20200723-1800/ > > > > On Win10 BrowserExample with Eclipse SWT Chromium fragment jar > > "org.eclipse.swt.browser.chromium.win32.win32.x86_64_3.115.0.v20200723-2026. > > jar" in the classpath, leads to below exception: > > --------------------------------------------------------------------------- > > Exception in thread "main" java.lang.SecurityException: class > > @Guillermo, > On Win10, with latest Eclipse IBuild, we got rid of above security error: > https://download.eclipse.org/eclipse/downloads/drops4/I20200724-0600/ > > On Win10, now getting below error while launching BrowserExample: > [0724/184959.790:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to > launch GPU process. > > Short of ideas on this error, can you please look into this ? Hi Niraj, are you still seeing this error? Could you try running with program arg: --disable-gpu ? Thanks. Hi Guillermo, Thanks for checking!! (In reply to Guillermo Zunino from comment #24) > > On Win10, now getting below error while launching BrowserExample: > > [0724/184959.790:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to > > launch GPU process. > > > Please remove ~/.swt. Maybe there are some old files wrong there from > previous attempts. Tried this but I still get the above error. (In reply to Guillermo Zunino from comment #25) > (In reply to Niraj Modi from comment #23) > > (In reply to Niraj Modi from comment #21) > > On Win10, now getting below error while launching BrowserExample: > > [0724/184959.790:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to > > launch GPU process. > > > > Short of ideas on this error, can you please look into this ? > > Hi Niraj, are you still seeing this error? > > Could you try running with program arg: --disable-gpu ? With above option, the error is gone but the browser doesn't load any site contents. Hi Guillermo, Got one specific comment w.r.t to .Net updates that could resolve the gpu related error on Windows: https://github.com/jupyter/notebook/issues/2836#issuecomment-363872311 Please confirm if mentioned KB patches are required on Windows10, here is the command-line option to check: systeminfo | findstr KB4057272 systeminfo | findstr KB4033369 How to interpret the result of above commands: If you get something in the result, then patches are installed otherwise no output. I see blank output my side. (In reply to Niraj Modi from comment #27) > Hi Guillermo, > Got one specific comment w.r.t to .Net updates that could resolve the gpu > related error on Windows: > https://github.com/jupyter/notebook/issues/2836#issuecomment-363872311 > > Please confirm if mentioned KB patches are required on Windows10, here is > the command-line option to check: > systeminfo | findstr KB4057272 > systeminfo | findstr KB4033369 > > How to interpret the result of above commands: > If you get something in the result, then patches are installed otherwise no > output. I see blank output my side. I also see blank output in two different windows where chromium is working. Listing all hotfixes: Hotfix(s): 15 Hotfix(s) Installed. [01]: KB4552931 [02]: KB4503308 [03]: KB4508433 [04]: KB4515383 [05]: KB4516115 [06]: KB4521863 [07]: KB4528759 [08]: KB4537759 [09]: KB4538674 [10]: KB4541338 [11]: KB4552152 [12]: KB4560959 [13]: KB4561600 [14]: KB4565554 [15]: KB4560960 Mass move out to 4.18 We also encountered the issue regarding the output of: [0724/184959.790:ERROR:browser_gpu_channel_host_factory.cc(103)] Failed to launch GPU process. The Browser widget did not correctly load after that and we only had a gray area where it was supposed to be. In our case, this was caused by a restriction to access the chromium executable (in windows C:\Users\USERNAME\.swt\lib\win32\x86_64\chromium-3071\chromium_subp-0102.exe) In many corporate environments it is a default setting to prevent the execution of any program located under the users home directory. Especially in these cases it would be easier and cleaner if these files would not be stored within some arbitrary directory in the user directory. Best case would be if it was configurable in which directory these files should be expected. but you would you configure this? (a setting in the eclipse.ini file?) i find this very weird that that is a setting that the user home dir can't execute stuff. I think thats what most people should install stuff into.. our product does that by default.. Thats where you know it should be fully writable.. i think even chromium does that by default (%LOCALAPPDATA%\xxx) I would configure this via a cli parameter (and thus make it configurable in the ini). And yes, i am aware of the fact, that several programs install themselves into the userhome. The environments i mentioned are very restrictive. In most of these environments, the user is not allowed to install additional software (outside of a specific set of applications). If an application is allowed to be installed (or more likely it is already installed) and known to install itself into the home directory, an exception is made, specifically for that application. Its just a security measure (and not a bad one i think) to restrict the software that is allowed to be installed (and run) on such systems. While it may not be a common case for normal users (since those most likely are their own administrators), in corporations and specifically in government departments, it is not that uncommon for the users to be restricted that way. (At least in Germany) Also, dont confuse writing stuff and executing stuff. The home directory is writeable (the workspace in our software is configured to be stored in the home directory by default) This is purely an issue about the rights to execute stuff located anywhere outside of specific locations and in some cases, this restriction is applied to the home directory and subdirectories. Specifically those unknown to the administrators (and .swt is not a common directory for anyone) (In reply to Michael Fröschen from comment #33) > Also, dont confuse writing stuff and executing stuff. The home directory is > writeable (the workspace in our software is configured to be stored in the > home directory by default) > This is purely an issue about the rights to execute stuff located anywhere > outside of specific locations and in some cases, this restriction is applied > to the home directory and subdirectories. > Specifically those unknown to the administrators (and .swt is not a common > directory for anyone) We are currently working on upgrading chromium browser. could not find enough time to work on this moving the target to 4.19 This may help: the swt.browser.chromium fragments seem corrupted for linux and windows (did not check mac); after editing the file chromium-3071/chromium.properties (within the jar) to fix the file names, it works. For org.eclipse.swt.browser.chromium.gtk.linux.x86_64_3.115.100.v20201202-1103.jar chromium.properties has to be changed to 00=chromium-3071/chromium_subp-4940r23 01=chromium-3071/libchromium_swt_4940r23.so 02=chromium-3071/libswt-chromium-gtk-4940r23.so @Lakshmi Shanmugam we see that linux binaries are broken for linux due the last build failed for v4942r19 while building natives: https://ci.eclipse.org/releng/view/SWT%20Natives/job/gtk_linux_x86_64_pipeline_chromium/195/consoleFull but still the jenkins job was green and the broken binaries were pushed. The error seems to be missing: libnss3.so libnssutil3.so libsmime3.so libnspr4.so in the docker image. Last working native build was using docker image eclipse/platformreleng-centos-swt-build:7 and the failing build is using image eclipse/platformreleng-centos-swt-build:8 . The missing package should probable be added to https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/cje-production/dockerfiles/centos-gtk3-metacity/8-swtBuild/Dockerfile. (In reply to mauro garcia from comment #36) > @Lakshmi Shanmugam > > we see that linux binaries are broken for linux due the last build failed > for v4942r19 while building natives: > https://ci.eclipse.org/releng/view/SWT%20Natives/job/ > gtk_linux_x86_64_pipeline_chromium/195/consoleFull but still the jenkins job > was green and the broken binaries were pushed. > The error seems to be missing: > libnss3.so > libnssutil3.so > libsmime3.so > libnspr4.so > in the docker image. Last working native build was using docker image > eclipse/platformreleng-centos-swt-build:7 and the failing build is using > image eclipse/platformreleng-centos-swt-build:8 . The missing package should > probable be added to > https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/ > tree/cje-production/dockerfiles/centos-gtk3-metacity/8-swtBuild/Dockerfile. Can you please specify which packages need to be added for these missing libraries? The docker image is CentOS 8. packages names to install in centos8 image are: nss nspr nss-util(In reply to Lakshmi P Shanmugam from comment #37) > (In reply to mauro garcia from comment #36) > > @Lakshmi Shanmugam > > > > we see that linux binaries are broken for linux due the last build failed > > for v4942r19 while building natives: > > https://ci.eclipse.org/releng/view/SWT%20Natives/job/ > > gtk_linux_x86_64_pipeline_chromium/195/consoleFull but still the jenkins job > > was green and the broken binaries were pushed. > > The error seems to be missing: > > libnss3.so > > libnssutil3.so > > libsmime3.so > > libnspr4.so > > in the docker image. Last working native build was using docker image > > eclipse/platformreleng-centos-swt-build:7 and the failing build is using > > image eclipse/platformreleng-centos-swt-build:8 . The missing package should > > probable be added to > > https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/ > > tree/cje-production/dockerfiles/centos-gtk3-metacity/8-swtBuild/Dockerfile. > > Can you please specify which packages need to be added for these missing > libraries? The docker image is CentOS 8. Hi! packages names to install in centos8 image are: nss nspr nss-util New Gerrit change created: https://git.eclipse.org/r/c/platform/eclipse.platform.releng.aggregator/+/176062 Gerrit change https://git.eclipse.org/r/c/platform/eclipse.platform.releng.aggregator/+/176062 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/commit/?id=821a1728fe6ecfd24566748f5467bac07b31869a (In reply to mauro garcia from comment #38) > > packages names to install in centos8 image are: > nss > nspr > nss-util(In reply to Lakshmi P Shanmugam from comment #37) > > (In reply to mauro garcia from comment #36) > > > @Lakshmi Shanmugam > > > > > > we see that linux binaries are broken for linux due the last build failed > > > for v4942r19 while building natives: > > > https://ci.eclipse.org/releng/view/SWT%20Natives/job/ > > > gtk_linux_x86_64_pipeline_chromium/195/consoleFull but still the jenkins job > > > was green and the broken binaries were pushed. > > > The error seems to be missing: > > > libnss3.so > > > libnssutil3.so > > > libsmime3.so > > > libnspr4.so > > > in the docker image. Last working native build was using docker image > > > eclipse/platformreleng-centos-swt-build:7 and the failing build is using > > > image eclipse/platformreleng-centos-swt-build:8 . The missing package should > > > probable be added to > > > https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/ > > > tree/cje-production/dockerfiles/centos-gtk3-metacity/8-swtBuild/Dockerfile. > > > > Can you please specify which packages need to be added for these missing > > libraries? The docker image is CentOS 8. > > > Hi! packages names to install in centos8 image are: > nss > nspr > nss-util added via (In reply to Eclipse Genie from comment #40) > Gerrit change > https://git.eclipse.org/r/c/platform/eclipse.platform.releng.aggregator/+/ > 176062 was merged to [master]. > Commit: > http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/ > commit/?id=821a1728fe6ecfd24566748f5467bac07b31869a Resetting the target, please re-target as required. Chromium has been removed via bug 572010 . |