From shane.lontis at oracle.com Sat May 1 01:05:28 2021 From: shane.lontis at oracle.com (SHANE LONTIS) Date: Sat, 1 May 2021 11:05:28 +1000 Subject: [buildbot-admin] [External] : Re: [fips-sponsors] buildbot workers In-Reply-To: References: <55F65A75-CCA4-4406-8AB7-094B979720BB@akamai.com> <874kfpocnm.wl-levitte@openssl.org> Message-ID: <414D2E4B-8473-473D-8DB8-2A54271E66C7@oracle.com> Gcc command not found implies it didn?t work :) https://fips.buildbot.openssl.org/#/builders/26/builds/2 > On 1 May 2021, at 5:14 am, Salz, Rich wrote: > > I have the environment setup. > I ran create-worker and it build the config files. > I did the start subcommand and it said > rsalz at 198.18.66.178:~$ buildbot-worker start /w/openssl-buildbot > Following twistd.log until startup finished.. > The buildbot-worker appears to have (re)started correctly. > rsalz at 198.18.66.178:~$ > > I went to the buildbot page. How can I tell if my machine is working? > > > _______________________________________________ > fips-sponsors mailing list > fips-sponsors at openssl.org > https://urldefense.com/v3/__https://mta.openssl.org/mailman/listinfo/fips-sponsors__;!!GqivPVa7Brio!JlTRpqfqQBghM-83tuRObtNDQLIbrgf5vz8yXP2_BrS6DNoa1kqDEanJME2I8SGWcQ$ -------------- next part -------------- An HTML attachment was scrubbed... URL: From rsalz at akamai.com Sat May 1 14:32:01 2021 From: rsalz at akamai.com (Salz, Rich) Date: Sat, 1 May 2021 14:32:01 +0000 Subject: [buildbot-admin] [fips-sponsors] [External] : Re: buildbot workers In-Reply-To: <414D2E4B-8473-473D-8DB8-2A54271E66C7@oracle.com> References: <55F65A75-CCA4-4406-8AB7-094B979720BB@akamai.com> <874kfpocnm.wl-levitte@openssl.org> <414D2E4B-8473-473D-8DB8-2A54271E66C7@oracle.com> Message-ID: * Gcc command not found implies it didn?t work :) * https://fips.buildbot.openssl.org/#/builders/26/builds/2 So I guess I didn?t wait long enough for a status to show up. Thanks. Now to debug that. -------------- next part -------------- An HTML attachment was scrubbed... URL: From levitte at openssl.org Mon May 3 08:34:57 2021 From: levitte at openssl.org (Richard Levitte) Date: Mon, 03 May 2021 10:34:57 +0200 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> Message-ID: <87zgxcmczy.wl-levitte@openssl.org> On Mon, 26 Apr 2021 20:25:34 +0200, Madhur Walia wrote: > > Hi Matt, > > Thank you for the instructions. However, we are facing couple of issues while starting buildbot-worker, > > For both platforms, we pointed Certificate/SSL settings to a custom directory in buildbot.tac as per your recommendation. We also tried importing both certs, isrg-root-xi & lets-encrypt-r3 to trust store of OS but no luck. > > Photon, > Getting error, " builtins.NameError: name 'optionsForClientTLS' is not defined" as shown in Photon1 screenshot attached. > Also ran a curl command to check SSL connectivity, seems to be failing, attached screenshot Photon2. Please check your versions of the following packages: - buildbot (should be at least version 2.6.0) - twisted (should be at least version 17.9.0 according to buildbot 2.6.0 requirements) 'optionsForClientTLS' is a method that appeared in twisted version 14.0. > Windows, > Getting, "Unicode error" as shown in Windows1 screenshot attached. > Also ran a curl command to check SSL connectivity, seems to be failing, attached screenshot Windows2. From the error message at the end of Windows1.png, you have an invalid unicode character on line 30. Could it be a character with diacritics not encoded with UTF-8? Cheers, Richard > Do you have any pointers on these errors? Please let us know. > > Thanks & Regards, > Madhur > > ------------------------------------------------------------------ > > ?On 21/04/21, 4:47 PM, "Matt Caswell" wrote: > > Thanks Manoj. > > To be able to set up your worker, you must use version 2.6.0 or > higher. Older version do not support TLS-protected connections. > > Please see these instructions for installing the buildbot worker > software: > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7Ccf23c19e05b642051b0e08d904b71682%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637546006695636962%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=WicGMU2oEIjvbJIEAGDBTUAnbEc4s72LnVZXTxMyXlw%3D&reserved=0 > > When buildbot has been installed on the platform where the buildbot > worker is to be run, this is how a worker is created (for your PhotonOS > worker): > > $ buildbot-worker create-worker --use-tls BASEDIR \ > buildbot.openssl.org:9989 vmware-photonos40 nifs0Tweex_ > > And for your Windows server: > > $ buildbot-worker create-worker --use-tls BASEDIR \ > buildbot.openssl.org:9989 vmware-winserver2019 Efyin.Freg0 > > > where BASEDIR is determined by you. See further down for a few notes > on TLS. > > To run a buildbot worker, you do this: > > $ buildbot-worker start BASEDIR > > Apart from the software needed to run a buildbot worker, and the > utilities that are the normal part of the operating system, you also > need to ensure that the following components are available: > > - toolchains, i.e. C compiler, linker, make. If you have specified > toolchains in the worker request form, you need to ensure that all > of them are installed. > > - git > > Regarding TLS, it may be that the buildbot worker platform doesn't > have the appropriate certification verification roots set up. In that > case, you may need to apply the attached buildbot.tac patch, and store > the attached PEM files in a directory of your choice. Finish up by > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with > the path of directory where you stored the PEM files. > > Matt > > On 21/04/2021 00:56, Manoj Maskara wrote: > > Hi Tim & Richard, > > > > We have filled out the worker-request-form for 2 of our platforms, one unix type and other Windows. Also, the platforms, for your convenience am listing here: > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 (Platform type: Unix, x86_64, build+test, gcc) > > 2) Windows Server 2019 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > Please provide the credentials and instruction on setting up the buildbot worker. > > > > Thanks, > > Manoj > > > > > > -----Original Message----- > > From: fips-sponsors On Behalf Of Richard Levitte > > Sent: Monday, April 12, 2021 12:20 AM > > To: fips-sponsors at openssl.org > > Subject: [fips-sponsors] Buildbot workers > > > > Hi, > > > > We are finally ready to start getting buildbot worker requests. > > > > The way this will work is that we're asking you to answer a form with details for each worker you want to set up for us, such as what platform, what architecture, and where relevant, what toolchains are installed. > > > > The form is attached below, and include explanations for all the fields to fill in. Please send it to buildbot-admin at openssl.org. > > > > In response, you will receive an email with the name and password we assign your worker(s), and instructions how to set the worker up. > > > > [2 Photon1.png ] > > [3 Photon2.png ] > > [4 Windows1.png ] > > [5 Windows2.png ] > > [6 ] > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://mta.openssl.org/mailman/listinfo/buildbot-admin -- Richard Levitte levitte at openssl.org OpenSSL Project http://www.openssl.org/~levitte/ From levitte at openssl.org Mon May 3 09:03:24 2021 From: levitte at openssl.org (Richard Levitte) Date: Mon, 03 May 2021 11:03:24 +0200 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: <87zgxcmczy.wl-levitte@openssl.org> References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org> Message-ID: <87wnsgmboj.wl-levitte@openssl.org> I now noticed that the Photon 4 workers have connected, so I assume the 'optionsForClientTLS' is a thing of the past. Looking at one of the builds, https://fips.buildbot.openssl.org/#/builders/33/builds/1, it looks like git isn't installed on the worker... Cheers, Richard On Mon, 03 May 2021 10:34:57 +0200, Richard Levitte wrote: > > On Mon, 26 Apr 2021 20:25:34 +0200, > Madhur Walia wrote: > > > > Hi Matt, > > > > Thank you for the instructions. However, we are facing couple of issues while starting buildbot-worker, > > > > For both platforms, we pointed Certificate/SSL settings to a custom directory in buildbot.tac as per your recommendation. We also tried importing both certs, isrg-root-xi & lets-encrypt-r3 to trust store of OS but no luck. > > > > Photon, > > Getting error, " builtins.NameError: name 'optionsForClientTLS' is not defined" as shown in Photon1 screenshot attached. > > Also ran a curl command to check SSL connectivity, seems to be failing, attached screenshot Photon2. > > Please check your versions of the following packages: > > - buildbot (should be at least version 2.6.0) > - twisted (should be at least version 17.9.0 according to buildbot > 2.6.0 requirements) > > 'optionsForClientTLS' is a method that appeared in twisted version 14.0. > > > Windows, > > Getting, "Unicode error" as shown in Windows1 screenshot attached. > > Also ran a curl command to check SSL connectivity, seems to be failing, attached screenshot Windows2. > > From the error message at the end of Windows1.png, you have an invalid > unicode character on line 30. Could it be a character with diacritics > not encoded with UTF-8? > > Cheers, > Richard > > > Do you have any pointers on these errors? Please let us know. > > > > Thanks & Regards, > > Madhur > > > > ------------------------------------------------------------------ > > > > ?On 21/04/21, 4:47 PM, "Matt Caswell" wrote: > > > > Thanks Manoj. > > > > To be able to set up your worker, you must use version 2.6.0 or > > higher. Older version do not support TLS-protected connections. > > > > Please see these instructions for installing the buildbot worker > > software: > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7Ccf23c19e05b642051b0e08d904b71682%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637546006695636962%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=WicGMU2oEIjvbJIEAGDBTUAnbEc4s72LnVZXTxMyXlw%3D&reserved=0 > > > > When buildbot has been installed on the platform where the buildbot > > worker is to be run, this is how a worker is created (for your PhotonOS > > worker): > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > buildbot.openssl.org:9989 vmware-photonos40 nifs0Tweex_ > > > > And for your Windows server: > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > buildbot.openssl.org:9989 vmware-winserver2019 Efyin.Freg0 > > > > > > where BASEDIR is determined by you. See further down for a few notes > > on TLS. > > > > To run a buildbot worker, you do this: > > > > $ buildbot-worker start BASEDIR > > > > Apart from the software needed to run a buildbot worker, and the > > utilities that are the normal part of the operating system, you also > > need to ensure that the following components are available: > > > > - toolchains, i.e. C compiler, linker, make. If you have specified > > toolchains in the worker request form, you need to ensure that all > > of them are installed. > > > > - git > > > > Regarding TLS, it may be that the buildbot worker platform doesn't > > have the appropriate certification verification roots set up. In that > > case, you may need to apply the attached buildbot.tac patch, and store > > the attached PEM files in a directory of your choice. Finish up by > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with > > the path of directory where you stored the PEM files. > > > > Matt > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > Hi Tim & Richard, > > > > > > We have filled out the worker-request-form for 2 of our platforms, one unix type and other Windows. Also, the platforms, for your convenience am listing here: > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 (Platform type: Unix, x86_64, build+test, gcc) > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > Please provide the credentials and instruction on setting up the buildbot worker. > > > > > > Thanks, > > > Manoj > > > > > > > > > -----Original Message----- > > > From: fips-sponsors On Behalf Of Richard Levitte > > > Sent: Monday, April 12, 2021 12:20 AM > > > To: fips-sponsors at openssl.org > > > Subject: [fips-sponsors] Buildbot workers > > > > > > Hi, > > > > > > We are finally ready to start getting buildbot worker requests. > > > > > > The way this will work is that we're asking you to answer a form with details for each worker you want to set up for us, such as what platform, what architecture, and where relevant, what toolchains are installed. > > > > > > The form is attached below, and include explanations for all the fields to fill in. Please send it to buildbot-admin at openssl.org. > > > > > > In response, you will receive an email with the name and password we assign your worker(s), and instructions how to set the worker up. > > > > > > > [2 Photon1.png ] > > > > [3 Photon2.png ] > > > > [4 Windows1.png ] > > > > [5 Windows2.png ] > > > > [6 ] > > _______________________________________________ > > buildbot-admin mailing list > > buildbot-admin at openssl.org > > https://mta.openssl.org/mailman/listinfo/buildbot-admin > -- > Richard Levitte levitte at openssl.org > OpenSSL Project http://www.openssl.org/~levitte/ > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://mta.openssl.org/mailman/listinfo/buildbot-admin -- Richard Levitte levitte at openssl.org OpenSSL Project http://www.openssl.org/~levitte/ From waliam at vmware.com Mon May 3 09:06:59 2021 From: waliam at vmware.com (Madhur Walia) Date: Mon, 3 May 2021 09:06:59 +0000 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: <87wnsgmboj.wl-levitte@openssl.org> References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org>,<87wnsgmboj.wl-levitte@openssl.org> Message-ID: Hi Richard, Thank you for the help. We had only installed buildbot-worker on Photon4 and Windows 2019. After installing Buildbot (master) on Photon4, the worker could start. We are now working on installing git on Photon4 and then troubleshooting Windows 2019. I will keep you updated. Regards, Madhur From: Richard Levitte Date: Monday, 3 May 2021 at 2:33 PM To: Madhur Walia Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav , buildbot-admin at openssl.org Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers I now noticed that the Photon 4 workers have connected, so I assume the 'optionsForClientTLS' is a thing of the past. Looking at one of the builds, https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108009695%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=W5ZizgajStLZh0p1sbhmwbEIonCMSQdhuH0ZcEDHETc%3D&reserved=0, it looks like git isn't installed on the worker... Cheers, Richard On Mon, 03 May 2021 10:34:57 +0200, Richard Levitte wrote: > > On Mon, 26 Apr 2021 20:25:34 +0200, > Madhur Walia wrote: > > > > Hi Matt, > > > > Thank you for the instructions. However, we are facing couple of issues while starting buildbot-worker, > > > > For both platforms, we pointed Certificate/SSL settings to a custom directory in buildbot.tac as per your recommendation. We also tried importing both certs, isrg-root-xi & lets-encrypt-r3 to trust store of OS but no luck. > > > > Photon, > > Getting error, " builtins.NameError: name 'optionsForClientTLS' is not defined" as shown in Photon1 screenshot attached. > > Also ran a curl command to check SSL connectivity, seems to be failing, attached screenshot Photon2. > > Please check your versions of the following packages: > > - buildbot (should be at least version 2.6.0) > - twisted (should be at least version 17.9.0 according to buildbot > 2.6.0 requirements) > > 'optionsForClientTLS' is a method that appeared in twisted version 14.0. > > > Windows, > > Getting, "Unicode error" as shown in Windows1 screenshot attached. > > Also ran a curl command to check SSL connectivity, seems to be failing, attached screenshot Windows2. > > From the error message at the end of Windows1.png, you have an invalid > unicode character on line 30. Could it be a character with diacritics > not encoded with UTF-8? > > Cheers, > Richard > > > Do you have any pointers on these errors? Please let us know. > > > > Thanks & Regards, > > Madhur > > > > ------------------------------------------------------------------ > > > > ?On 21/04/21, 4:47 PM, "Matt Caswell" wrote: > > > > Thanks Manoj. > > > > To be able to set up your worker, you must use version 2.6.0 or > > higher. Older version do not support TLS-protected connections. > > > > Please see these instructions for installing the buildbot worker > > software: > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TcoREUxnTLQ5%2F28PqDL83I9d16%2BuhxCTZpbuiEqF0sM%3D&reserved=0 > > > > When buildbot has been installed on the platform where the buildbot > > worker is to be run, this is how a worker is created (for your PhotonOS > > worker): > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > buildbot.openssl.org:9989 vmware-photonos40 nifs0Tweex_ > > > > And for your Windows server: > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > buildbot.openssl.org:9989 vmware-winserver2019 Efyin.Freg0 > > > > > > where BASEDIR is determined by you. See further down for a few notes > > on TLS. > > > > To run a buildbot worker, you do this: > > > > $ buildbot-worker start BASEDIR > > > > Apart from the software needed to run a buildbot worker, and the > > utilities that are the normal part of the operating system, you also > > need to ensure that the following components are available: > > > > - toolchains, i.e. C compiler, linker, make. If you have specified > > toolchains in the worker request form, you need to ensure that all > > of them are installed. > > > > - git > > > > Regarding TLS, it may be that the buildbot worker platform doesn't > > have the appropriate certification verification roots set up. In that > > case, you may need to apply the attached buildbot.tac patch, and store > > the attached PEM files in a directory of your choice. Finish up by > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with > > the path of directory where you stored the PEM files. > > > > Matt > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > Hi Tim & Richard, > > > > > > We have filled out the worker-request-form for 2 of our platforms, one unix type and other Windows. Also, the platforms, for your convenience am listing here: > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 (Platform type: Unix, x86_64, build+test, gcc) > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > Please provide the credentials and instruction on setting up the buildbot worker. > > > > > > Thanks, > > > Manoj > > > > > > > > > -----Original Message----- > > > From: fips-sponsors On Behalf Of Richard Levitte > > > Sent: Monday, April 12, 2021 12:20 AM > > > To: fips-sponsors at openssl.org > > > Subject: [fips-sponsors] Buildbot workers > > > > > > Hi, > > > > > > We are finally ready to start getting buildbot worker requests. > > > > > > The way this will work is that we're asking you to answer a form with details for each worker you want to set up for us, such as what platform, what architecture, and where relevant, what toolchains are installed. > > > > > > The form is attached below, and include explanations for all the fields to fill in. Please send it to buildbot-admin at openssl.org. > > > > > > In response, you will receive an email with the name and password we assign your worker(s), and instructions how to set the worker up. > > > > > > > [2 Photon1.png ] > > > > [3 Photon2.png ] > > > > [4 Windows1.png ] > > > > [5 Windows2.png ] > > > > [6 ] > > _______________________________________________ > > buildbot-admin mailing list > > buildbot-admin at openssl.org > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Bxq8pym%2BcZFZJx2ldzclbifh9LBrQxRzYlMgVP9AjOA%3D&reserved=0 > -- > Richard Levitte levitte at openssl.org > OpenSSL Project https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qwVUH49lHuZBsNdculwt63fEiEPbIK%2BCXc61EmipXbA%3D&reserved=0 > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Bxq8pym%2BcZFZJx2ldzclbifh9LBrQxRzYlMgVP9AjOA%3D&reserved=0 -- Richard Levitte levitte at openssl.org OpenSSL Project https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qwVUH49lHuZBsNdculwt63fEiEPbIK%2BCXc61EmipXbA%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From waliam at vmware.com Mon May 3 14:48:58 2021 From: waliam at vmware.com (Madhur Walia) Date: Mon, 3 May 2021 14:48:58 +0000 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org>, <87wnsgmboj.wl-levitte@openssl.org>, Message-ID: Hi Richard, We have installed git on Photon, please let us know next steps. Installed buildbot and VS2017 on Windows 2019 as shown below but the connection seems to be dropping, Versions installed on Windows 2019, [Text Description automatically generated] Win2019: Connection Failing, going in a loop, [Graphical user interface, text Description automatically generated] Thanks & Regards, Madhur From: Madhur Walia Date: Monday, 3 May 2021 at 2:37 PM To: Richard Levitte Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav , buildbot-admin at openssl.org Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers Hi Richard, Thank you for the help. We had only installed buildbot-worker on Photon4 and Windows 2019. After installing Buildbot (master) on Photon4, the worker could start. We are now working on installing git on Photon4 and then troubleshooting Windows 2019. I will keep you updated. Regards, Madhur From: Richard Levitte Date: Monday, 3 May 2021 at 2:33 PM To: Madhur Walia Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav , buildbot-admin at openssl.org Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers I now noticed that the Photon 4 workers have connected, so I assume the 'optionsForClientTLS' is a thing of the past. Looking at one of the builds, https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108009695%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=W5ZizgajStLZh0p1sbhmwbEIonCMSQdhuH0ZcEDHETc%3D&reserved=0, it looks like git isn't installed on the worker... Cheers, Richard On Mon, 03 May 2021 10:34:57 +0200, Richard Levitte wrote: > > On Mon, 26 Apr 2021 20:25:34 +0200, > Madhur Walia wrote: > > > > Hi Matt, > > > > Thank you for the instructions. However, we are facing couple of issues while starting buildbot-worker, > > > > For both platforms, we pointed Certificate/SSL settings to a custom directory in buildbot.tac as per your recommendation. We also tried importing both certs, isrg-root-xi & lets-encrypt-r3 to trust store of OS but no luck. > > > > Photon, > > Getting error, " builtins.NameError: name 'optionsForClientTLS' is not defined" as shown in Photon1 screenshot attached. > > Also ran a curl command to check SSL connectivity, seems to be failing, attached screenshot Photon2. > > Please check your versions of the following packages: > > - buildbot (should be at least version 2.6.0) > - twisted (should be at least version 17.9.0 according to buildbot > 2.6.0 requirements) > > 'optionsForClientTLS' is a method that appeared in twisted version 14.0. > > > Windows, > > Getting, "Unicode error" as shown in Windows1 screenshot attached. > > Also ran a curl command to check SSL connectivity, seems to be failing, attached screenshot Windows2. > > From the error message at the end of Windows1.png, you have an invalid > unicode character on line 30. Could it be a character with diacritics > not encoded with UTF-8? > > Cheers, > Richard > > > Do you have any pointers on these errors? Please let us know. > > > > Thanks & Regards, > > Madhur > > > > ------------------------------------------------------------------ > > > > ?On 21/04/21, 4:47 PM, "Matt Caswell" wrote: > > > > Thanks Manoj. > > > > To be able to set up your worker, you must use version 2.6.0 or > > higher. Older version do not support TLS-protected connections. > > > > Please see these instructions for installing the buildbot worker > > software: > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TcoREUxnTLQ5%2F28PqDL83I9d16%2BuhxCTZpbuiEqF0sM%3D&reserved=0 > > > > When buildbot has been installed on the platform where the buildbot > > worker is to be run, this is how a worker is created (for your PhotonOS > > worker): > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > buildbot.openssl.org:9989 vmware-photonos40 nifs0Tweex_ > > > > And for your Windows server: > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > buildbot.openssl.org:9989 vmware-winserver2019 Efyin.Freg0 > > > > > > where BASEDIR is determined by you. See further down for a few notes > > on TLS. > > > > To run a buildbot worker, you do this: > > > > $ buildbot-worker start BASEDIR > > > > Apart from the software needed to run a buildbot worker, and the > > utilities that are the normal part of the operating system, you also > > need to ensure that the following components are available: > > > > - toolchains, i.e. C compiler, linker, make. If you have specified > > toolchains in the worker request form, you need to ensure that all > > of them are installed. > > > > - git > > > > Regarding TLS, it may be that the buildbot worker platform doesn't > > have the appropriate certification verification roots set up. In that > > case, you may need to apply the attached buildbot.tac patch, and store > > the attached PEM files in a directory of your choice. Finish up by > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with > > the path of directory where you stored the PEM files. > > > > Matt > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > Hi Tim & Richard, > > > > > > We have filled out the worker-request-form for 2 of our platforms, one unix type and other Windows. Also, the platforms, for your convenience am listing here: > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 (Platform type: Unix, x86_64, build+test, gcc) > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > Please provide the credentials and instruction on setting up the buildbot worker. > > > > > > Thanks, > > > Manoj > > > > > > > > > -----Original Message----- > > > From: fips-sponsors On Behalf Of Richard Levitte > > > Sent: Monday, April 12, 2021 12:20 AM > > > To: fips-sponsors at openssl.org > > > Subject: [fips-sponsors] Buildbot workers > > > > > > Hi, > > > > > > We are finally ready to start getting buildbot worker requests. > > > > > > The way this will work is that we're asking you to answer a form with details for each worker you want to set up for us, such as what platform, what architecture, and where relevant, what toolchains are installed. > > > > > > The form is attached below, and include explanations for all the fields to fill in. Please send it to buildbot-admin at openssl.org. > > > > > > In response, you will receive an email with the name and password we assign your worker(s), and instructions how to set the worker up. > > > > > > > [2 Photon1.png ] > > > > [3 Photon2.png ] > > > > [4 Windows1.png ] > > > > [5 Windows2.png ] > > > > [6 ] > > _______________________________________________ > > buildbot-admin mailing list > > buildbot-admin at openssl.org > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Bxq8pym%2BcZFZJx2ldzclbifh9LBrQxRzYlMgVP9AjOA%3D&reserved=0 > -- > Richard Levitte levitte at openssl.org > OpenSSL Project https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qwVUH49lHuZBsNdculwt63fEiEPbIK%2BCXc61EmipXbA%3D&reserved=0 > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Bxq8pym%2BcZFZJx2ldzclbifh9LBrQxRzYlMgVP9AjOA%3D&reserved=0 -- Richard Levitte levitte at openssl.org OpenSSL Project https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qwVUH49lHuZBsNdculwt63fEiEPbIK%2BCXc61EmipXbA%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 155785 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 413174 bytes Desc: image002.png URL: From levitte at openssl.org Tue May 4 07:20:21 2021 From: levitte at openssl.org (Richard Levitte) Date: Tue, 04 May 2021 09:20:21 +0200 Subject: [buildbot-admin] Oracle Build Bot Workers In-Reply-To: References: Message-ID: <87k0ofm0cq.wl-levitte@openssl.org> I have set up the solaris worker, the other two will need a conversation, which I'm taking separately. Thank you for offering workers to us! To be able to set up your worker, you must use version 2.6.0 or higher. Older version do not support TLS-protected connections. Please see these instructions for installing the buildbot worker software: http://docs.buildbot.net/latest/manual/installation/worker.html When buildbot has been installed on the platform where the buildbot worker is to be run, this is how a worker is created: $ buildbot-worker create-worker --use-tls BASEDIR \ buildbot.openssl.org:9989 Oracle-Solaris-Sparc-M8 ' -------------- next part -------------- A non-text attachment was scrubbed... Name: isrg-root-x1.pem Type: application/octet-stream Size: 1939 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: lets-encrypt-r3.pem Type: application/octet-stream Size: 1826 bytes Desc: not available URL: -------------- next part -------------- Cheers, Richard On Mon, 26 Apr 2021 22:31:47 +0200, Chris Brych wrote: > > > Hi Richard and Tim, > > Attached you will find some build bot configuration details as best we know. Oracle teams have > been trying to ramp up and learn a little about build bot so be patient if we are missing some > details. I think that for Solaris, it is pretty straight forward but for ILOM, the team still > have some questions. > > 1. Because ILOM is an embedded device that runs on ARM, the team builds on an X86 machine and > then tests within its ARM platform. Does this mean that they will require 2 build bot workers? ie > one to build and one to test? > > 2. It would be very convenient for Oracle if they will allow our arm worker to run in a qemu VM > rather than real arm hardware. Is this possible? > > 3. Although ILOM runs oracle linux, the "command line utilities [that] can be expected" are > severely limited (and most of those are busybox, not OL native--that means they work differently > and/or have limited functionality). Can you elaborate on which command line utilities that are > required? > > 4. "Necessary environment variables". We set dozens of them for ILOM builds. I don't know which > (if any) are required for building OpenSSL standalone. Are there any environment variables that > are necessary for building OpenSSL 3.0? > > Thanks. > > Cheers, > > Chris > > Oracle > Chris Brych | Senior Principal Security Analyst > Oracle Security Evaluations - Global Product Security > Ottawa, Ontario | Canada > > +1-905-267-9352 (O) | +1-613-867-1241 (M) > > Gree Oracle is committed to developing practices and products that help protect the environment > > > > > Details we need or want from you > ================================ > > * Worker tag [OPTIONAL]: ILOM_build > > * Worker platform type [MANDATORY]: unix > > (accepted values: 'unix', 'windows') > > * Worker platform identity [OPTIONAL]: oracle linux > > (examples: 'ubuntu', 'ios', 'android', 'win10') > > * Worker platform architecture [OPTIONAL]: x86_64 > > (examples: 'x86', 'x86_64', 'arm', 'ppc') > > * Worker Purpose [MANDATORY, more than one choice allowed]: build (x86_64) > > (accepted values: 'build+test', 'build', 'test') > > * Worker toolchains for building [RECOMMENDED, more than one choice allowed]: gcc > > (examples: 'default', 'gcc', 'clang', 'vs2017', 'vs2019') > > * Necessary environment variables [OPTIONAL]: > > * Necessary configuration target name [OPTIONAL]: linux-generic32 > > * Necessary configuration options [OPTIONAL]: -DL_ENDIAN -DOPENSSL_NO_COMP shared --prefix=/usr --openssldir=/conf/openssl no-zlib no-comp > > * Max number of concurrent builds [OPTIONAL]: > > > What can be expected next > ========================= > > For each form that we receive, we will assign you a full worker name and a > passphrase, and respond to you by email informing you of this and additional > information, such as basic instructions for creating and starting the worker, > what the buildbot status page is, and more. > > > About the details we ask from you > ================================= > > * Worker tag: Short mnemonic. > This will be included in the full name of the worker. If you're not > giving us one, we may make one for you. > > * Worker platform type: this is MANDATORY, because the buildbot master > needs that to determine what command line shell is used (/bin/sh is > assumed for 'unix', cmd.exe is assumed for 'windows') and what command > line utilities can be expected. > > * Worker platform identity: a finer grained identity token, like 'ubuntu', > 'ios', ... this is used to segregates between builds on these different > platforms. If this isn't present, the platform type ('unix' or 'windows') > are used for this segregation. > > * Worker platform architecture: just like the worker platform identity, > this is used to segregate between different builds where it may be > important. This is only necessary if OpenSSL has corresponding config > targets. > > * Worker purpose: What this worker should be used for. This can be used > to have different workers work together with different tasks, for > various reasons. The accepted values are: > > build+test This denotes a "do everything" worker, i.e. it will > get to do 'Configure', 'make' and 'make test'. > > build This denotes a worker that will only build, but not > test. In other words, only 'Configure' and 'make' > will be performed. > If there is any matching worker that's denoted > 'test', the programs and libraries created by this > 'build' worker will be shipped to the worker that is > assigned to perform the test. > > test This denotes a worker that will only test, but not > build. In other words, only 'make test' will be > performed. > > The separate 'build' and 'test' purposes can be used to have one worker > cross compile for some target architecture, and shipping the result to a > worker that is of that architecture and that will perform the tests. > > The separate 'build' and 'test' purposes can be also be used to separate > workers that are quick builders from others that don't build as quickly, > allowing quicker developer turnaround when something needs to be fixed. > > Matching 'build' and 'test' workers are found on the basis of the worker > tag, the platform type or platform identity and the platform architecture, > by forming strings as follows from the worker information, and simply > comparing strings: > > "{worker-tag}-{platform-id}-{platform-arch}" > > "{worker-tag}-{platform-type}-{platform-arch}" > > If no matching 'test' workers are found, then only the build will be > performed. > > NOTE: NOT CURRENTLY IMPLEMENTED! > 'test' workers are currently not implemented, so those works will > currently remain idle. However, we do work on making transfer of files > work smoothly, so they may start to do actual work at some point in the > near future. > > * Worked toolchains for building: This allows a worker to be used > for multiple known building configurations, and is specified as a > list of mnemonics. Multiple choices may be specified. If no > choice is given, 'default' is assumed. > > The current available choices are: > > - 'default' > > This uses whatever happens to be considered default by > OpenSSL's Configure script. > On Unix, that's normally the default C compiler 'cc' and 'make'. > On Windows, that's the MSVC compiler 'cl', 'link' and 'nmake'. > > This toolchain choice expects all the compiling and linking > tools to be set up correctly in the worker. $PATH or %PATH% > and other environment variables must be set up correctly when > the worker is started. > > - 'gcc' and 'clang' > > This uses specific compilers instead of the default 'cc', but > works otherwise like 'default'. > > - 'vs2017', 'vs2017c', vs2017e', 'vs2017p', 'vs2019', 'vs2019c', > 'vs2019e', 'vs2019p' > > These all cover different versions and editions of Microsoft > Visual Studio C, as follows: > > - 'vs2017', 'vs2017c' > > Microsoft Visual Studio 2017, Community edition > > - 'vs2017e' > > Microsoft Visual Studio 2017, Enterprise edition > > - 'vs2017p > > Microsoft Visual Studio 2017, Professional edition > > - 'vs2019', 'vs2019c' > > Microsoft Visual Studio 2019, Community edition > > - 'vs2019e' > > Microsoft Visual Studio 2019, Enterprise edition > > - 'vs2019p > > Microsoft Visual Studio 2019, Professional edition > > OpenSSL's buildbot setup adds extra support for these choices, > by calling the appropriate Visual Studio setup script for each > of them when building, assuming that the setup script is > installed in default places. > > More toolchain choices may be added over time, as the need arises. > > * Necessary environment variables: Environment variables that are > necessary to build properly on the target platform. > This should normally not be needed, but could be in some cases. An > example is Android, where it's necessary to specify the Android root > with ANDROID_NDK_ROOT, and to adjust the PATH accordingly (see > NOTES-ANDROID.md in the OpenSSL 3.0 source) > > * Necessary configuration target name: Explicit configuration target name. > This should normally not be needed, as OpenSSL's configuration script > should be able to detect the target platform automatically. This is > however not always possible, for example when cross compilation is > needed, or when OpenSSL's configuration script doesn't know how to > automatically detect the target platform. > > NOTE: The OpenSSL developers would appreciate if you could tell us how > to automatically detect the configuration target for your platform, if > OpenSSL's configuration script doesn't currently do that. > > * Necessary configuration options: Additional configuration options > necessary to correctly build OpenSSL for the target platform. > This should normally not be needed, but could be in some cases. An > example is Android, where it's necessary to specify the desired Android > API version number using the C macro __ANDROID_API__. > > * Max number of concurrent builds: A limitation for how many builds are > allowed to happen concurrently on this worker. This is suitable when > too many resources would otherwise be used. By default, there is no > limit. > Details we need or want from you > ================================ > > * Worker tag [OPTIONAL]: ILOM_test > > * Worker platform type [MANDATORY]: unix > > (accepted values: 'unix', 'windows') > > * Worker platform identity [OPTIONAL]: oracle linux > > (examples: 'ubuntu', 'ios', 'android', 'win10') > > * Worker platform architecture [OPTIONAL]: arm > > (examples: 'x86', 'x86_64', 'arm', 'ppc') > > * Worker Purpose [MANDATORY, more than one choice allowed]: test (arm) > > (accepted values: 'build+test', 'build', 'test') > > * Worker toolchains for building [RECOMMENDED, more than one choice allowed]: gcc > > (examples: 'default', 'gcc', 'clang', 'vs2017', 'vs2019') > > * Necessary environment variables [OPTIONAL]: > > * Necessary configuration target name [OPTIONAL]: linux-generic32 > > * Necessary configuration options [OPTIONAL]: -DL_ENDIAN -DOPENSSL_NO_COMP shared --prefix=/usr --openssldir=/conf/openssl no-zlib no-comp > > * Max number of concurrent builds [OPTIONAL]: > > > What can be expected next > ========================= > > For each form that we receive, we will assign you a full worker name and a > passphrase, and respond to you by email informing you of this and additional > information, such as basic instructions for creating and starting the worker, > what the buildbot status page is, and more. > > > About the details we ask from you > ================================= > > * Worker tag: Short mnemonic. > This will be included in the full name of the worker. If you're not > giving us one, we may make one for you. > > * Worker platform type: this is MANDATORY, because the buildbot master > needs that to determine what command line shell is used (/bin/sh is > assumed for 'unix', cmd.exe is assumed for 'windows') and what command > line utilities can be expected. > > * Worker platform identity: a finer grained identity token, like 'ubuntu', > 'ios', ... this is used to segregates between builds on these different > platforms. If this isn't present, the platform type ('unix' or 'windows') > are used for this segregation. > > * Worker platform architecture: just like the worker platform identity, > this is used to segregate between different builds where it may be > important. This is only necessary if OpenSSL has corresponding config > targets. > > * Worker purpose: What this worker should be used for. This can be used > to have different workers work together with different tasks, for > various reasons. The accepted values are: > > build+test This denotes a "do everything" worker, i.e. it will > get to do 'Configure', 'make' and 'make test'. > > build This denotes a worker that will only build, but not > test. In other words, only 'Configure' and 'make' > will be performed. > If there is any matching worker that's denoted > 'test', the programs and libraries created by this > 'build' worker will be shipped to the worker that is > assigned to perform the test. > > test This denotes a worker that will only test, but not > build. In other words, only 'make test' will be > performed. > > The separate 'build' and 'test' purposes can be used to have one worker > cross compile for some target architecture, and shipping the result to a > worker that is of that architecture and that will perform the tests. > > The separate 'build' and 'test' purposes can be also be used to separate > workers that are quick builders from others that don't build as quickly, > allowing quicker developer turnaround when something needs to be fixed. > > Matching 'build' and 'test' workers are found on the basis of the worker > tag, the platform type or platform identity and the platform architecture, > by forming strings as follows from the worker information, and simply > comparing strings: > > "{worker-tag}-{platform-id}-{platform-arch}" > > "{worker-tag}-{platform-type}-{platform-arch}" > > If no matching 'test' workers are found, then only the build will be > performed. > > NOTE: NOT CURRENTLY IMPLEMENTED! > 'test' workers are currently not implemented, so those works will > currently remain idle. However, we do work on making transfer of files > work smoothly, so they may start to do actual work at some point in the > near future. > > * Worked toolchains for building: This allows a worker to be used > for multiple known building configurations, and is specified as a > list of mnemonics. Multiple choices may be specified. If no > choice is given, 'default' is assumed. > > The current available choices are: > > - 'default' > > This uses whatever happens to be considered default by > OpenSSL's Configure script. > On Unix, that's normally the default C compiler 'cc' and 'make'. > On Windows, that's the MSVC compiler 'cl', 'link' and 'nmake'. > > This toolchain choice expects all the compiling and linking > tools to be set up correctly in the worker. $PATH or %PATH% > and other environment variables must be set up correctly when > the worker is started. > > - 'gcc' and 'clang' > > This uses specific compilers instead of the default 'cc', but > works otherwise like 'default'. > > - 'vs2017', 'vs2017c', vs2017e', 'vs2017p', 'vs2019', 'vs2019c', > 'vs2019e', 'vs2019p' > > These all cover different versions and editions of Microsoft > Visual Studio C, as follows: > > - 'vs2017', 'vs2017c' > > Microsoft Visual Studio 2017, Community edition > > - 'vs2017e' > > Microsoft Visual Studio 2017, Enterprise edition > > - 'vs2017p > > Microsoft Visual Studio 2017, Professional edition > > - 'vs2019', 'vs2019c' > > Microsoft Visual Studio 2019, Community edition > > - 'vs2019e' > > Microsoft Visual Studio 2019, Enterprise edition > > - 'vs2019p > > Microsoft Visual Studio 2019, Professional edition > > OpenSSL's buildbot setup adds extra support for these choices, > by calling the appropriate Visual Studio setup script for each > of them when building, assuming that the setup script is > installed in default places. > > More toolchain choices may be added over time, as the need arises. > > * Necessary environment variables: Environment variables that are > necessary to build properly on the target platform. > This should normally not be needed, but could be in some cases. An > example is Android, where it's necessary to specify the Android root > with ANDROID_NDK_ROOT, and to adjust the PATH accordingly (see > NOTES-ANDROID.md in the OpenSSL 3.0 source) > > * Necessary configuration target name: Explicit configuration target name. > This should normally not be needed, as OpenSSL's configuration script > should be able to detect the target platform automatically. This is > however not always possible, for example when cross compilation is > needed, or when OpenSSL's configuration script doesn't know how to > automatically detect the target platform. > > NOTE: The OpenSSL developers would appreciate if you could tell us how > to automatically detect the configuration target for your platform, if > OpenSSL's configuration script doesn't currently do that. > > * Necessary configuration options: Additional configuration options > necessary to correctly build OpenSSL for the target platform. > This should normally not be needed, but could be in some cases. An > example is Android, where it's necessary to specify the desired Android > API version number using the C macro __ANDROID_API__. > > * Max number of concurrent builds: A limitation for how many builds are > allowed to happen concurrently on this worker. This is suitable when > too many resources would otherwise be used. By default, there is no > limit. > Details we need or want from you > ================================ > > * Worker tag [OPTIONAL]: Oracle Solaris / SPARC M8 > > * Worker platform type [MANDATORY]: unix > > (accepted values: 'unix', 'windows') > > * Worker platform identity [OPTIONAL]: solaris11 > > (examples: 'ubuntu', 'ios', 'android', 'win10') > > * Worker platform architecture [OPTIONAL]: sparcv9 > > (examples: 'x86', 'x86_64', 'arm', 'ppc') > > * Worker Purpose [MANDATORY, more than one choice allowed]: build+test > > (accepted values: 'build+test', 'build', 'test') > > * Worker toolchains for building [RECOMMENDED, more than one choice allowed]: default (Oracle Developer Studio), gcc > > (examples: 'default', 'gcc', 'clang', 'vs2017', 'vs2019') > > * Necessary environment variables [OPTIONAL]: > > * Necessary configuration target name [OPTIONAL]: solaris64-sparcv9-cc, solaris64-sparcv9-gcc > > * Necessary configuration options [OPTIONAL]: > > * Max number of concurrent builds [OPTIONAL]: > > > What can be expected next > ========================= > > For each form that we receive, we will assign you a full worker name and a > passphrase, and respond to you by email informing you of this and additional > information, such as basic instructions for creating and starting the worker, > what the buildbot status page is, and more. > > > About the details we ask from you > ================================= > > * Worker tag: Short mnemonic. > This will be included in the full name of the worker. If you're not > giving us one, we may make one for you. > > * Worker platform type: this is MANDATORY, because the buildbot master > needs that to determine what command line shell is used (/bin/sh is > assumed for 'unix', cmd.exe is assumed for 'windows') and what command > line utilities can be expected. > > * Worker platform identity: a finer grained identity token, like 'ubuntu', > 'ios', ... this is used to segregates between builds on these different > platforms. If this isn't present, the platform type ('unix' or 'windows') > are used for this segregation. > > * Worker platform architecture: just like the worker platform identity, > this is used to segregate between different builds where it may be > important. This is only necessary if OpenSSL has corresponding config > targets. > > * Worker purpose: What this worker should be used for. This can be used > to have different workers work together with different tasks, for > various reasons. The accepted values are: > > build+test This denotes a "do everything" worker, i.e. it will > get to do 'Configure', 'make' and 'make test'. > > build This denotes a worker that will only build, but not > test. In other words, only 'Configure' and 'make' > will be performed. > If there is any matching worker that's denoted > 'test', the programs and libraries created by this > 'build' worker will be shipped to the worker that is > assigned to perform the test. > > test This denotes a worker that will only test, but not > build. In other words, only 'make test' will be > performed. > > The separate 'build' and 'test' purposes can be used to have one worker > cross compile for some target architecture, and shipping the result to a > worker that is of that architecture and that will perform the tests. > > The separate 'build' and 'test' purposes can be also be used to separate > workers that are quick builders from others that don't build as quickly, > allowing quicker developer turnaround when something needs to be fixed. > > Matching 'build' and 'test' workers are found on the basis of the worker > tag, the platform type or platform identity and the platform architecture, > by forming strings as follows from the worker information, and simply > comparing strings: > > "{worker-tag}-{platform-id}-{platform-arch}" > > "{worker-tag}-{platform-type}-{platform-arch}" > > If no matching 'test' workers are found, then only the build will be > performed. > > NOTE: NOT CURRENTLY IMPLEMENTED! > 'test' workers are currently not implemented, so those works will > currently remain idle. However, we do work on making transfer of files > work smoothly, so they may start to do actual work at some point in the > near future. > > * Worked toolchains for building: This allows a worker to be used > for multiple known building configurations, and is specified as a > list of mnemonics. Multiple choices may be specified. If no > choice is given, 'default' is assumed. > > The current available choices are: > > - 'default' > > This uses whatever happens to be considered default by > OpenSSL's Configure script. > On Unix, that's normally the default C compiler 'cc' and 'make'. > On Windows, that's the MSVC compiler 'cl', 'link' and 'nmake'. > > This toolchain choice expects all the compiling and linking > tools to be set up correctly in the worker. $PATH or %PATH% > and other environment variables must be set up correctly when > the worker is started. > > - 'gcc' and 'clang' > > This uses specific compilers instead of the default 'cc', but > works otherwise like 'default'. > > - 'vs2017', 'vs2017c', vs2017e', 'vs2017p', 'vs2019', 'vs2019c', > 'vs2019e', 'vs2019p' > > These all cover different versions and editions of Microsoft > Visual Studio C, as follows: > > - 'vs2017', 'vs2017c' > > Microsoft Visual Studio 2017, Community edition > > - 'vs2017e' > > Microsoft Visual Studio 2017, Enterprise edition > > - 'vs2017p > > Microsoft Visual Studio 2017, Professional edition > > - 'vs2019', 'vs2019c' > > Microsoft Visual Studio 2019, Community edition > > - 'vs2019e' > > Microsoft Visual Studio 2019, Enterprise edition > > - 'vs2019p > > Microsoft Visual Studio 2019, Professional edition > > OpenSSL's buildbot setup adds extra support for these choices, > by calling the appropriate Visual Studio setup script for each > of them when building, assuming that the setup script is > installed in default places. > > More toolchain choices may be added over time, as the need arises. > > * Necessary environment variables: Environment variables that are > necessary to build properly on the target platform. > This should normally not be needed, but could be in some cases. An > example is Android, where it's necessary to specify the Android root > with ANDROID_NDK_ROOT, and to adjust the PATH accordingly (see > NOTES-ANDROID.md in the OpenSSL 3.0 source) > > * Necessary configuration target name: Explicit configuration target name. > This should normally not be needed, as OpenSSL's configuration script > should be able to detect the target platform automatically. This is > however not always possible, for example when cross compilation is > needed, or when OpenSSL's configuration script doesn't know how to > automatically detect the target platform. > > NOTE: The OpenSSL developers would appreciate if you could tell us how > to automatically detect the configuration target for your platform, if > OpenSSL's configuration script doesn't currently do that. > > * Necessary configuration options: Additional configuration options > necessary to correctly build OpenSSL for the target platform. > This should normally not be needed, but could be in some cases. An > example is Android, where it's necessary to specify the desired Android > API version number using the C macro __ANDROID_API__. > > * Max number of concurrent builds: A limitation for how many builds are > allowed to happen concurrently on this worker. This is suitable when > too many resources would otherwise be used. By default, there is no > limit. > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://mta.openssl.org/mailman/listinfo/buildbot-admin -- Richard Levitte levitte at openssl.org OpenSSL Project http://www.openssl.org/~levitte/ From levitte at openssl.org Tue May 4 07:37:05 2021 From: levitte at openssl.org (Richard Levitte) Date: Tue, 04 May 2021 09:37:05 +0200 Subject: [buildbot-admin] Oracle Build Bot Workers In-Reply-To: References: Message-ID: <87im3zlzku.wl-levitte@openssl.org> Regarding ILOM, it seems pretty special and will need extra accomodation, which should mimic what you normally do when building and testing, as much as possible. For building for ILOM, I assume that you do some kind of cross platform build. When you do it manually, what are the commands to configure OpenSSL? What you have specified in ILOM-Build-worker-request-form.txt doesn't specify anything suggesting such a cross compilation. For testing on the ILOM device, exactly what do you do? The "normal" way of testing OpenSSL is to run the test suite, i.e. do "make test". For a separate test worker, that will require copying the appropriate files from the build worker (something that we should do for you), so the required command line utilities would be those that are used by the test suite (including perl)... such a setup would require installing the buildbot worker on the test device, and python along with it. If you run tests in a different manner, we need to be informed, and will have to see how we can accomodate (I'm pondering that one could specify an optional wrapper script written by that could be specified with the test worker, and that would be used for testing). Cheers, Richard On Mon, 26 Apr 2021 22:31:47 +0200, Chris Brych wrote: > > > Hi Richard and Tim, > > Attached you will find some build bot configuration details as best we know. Oracle teams have > been trying to ramp up and learn a little about build bot so be patient if we are missing some > details. I think that for Solaris, it is pretty straight forward but for ILOM, the team still > have some questions. > > 1. Because ILOM is an embedded device that runs on ARM, the team builds on an X86 machine and > then tests within its ARM platform. Does this mean that they will require 2 build bot workers? ie > one to build and one to test? > > 2. It would be very convenient for Oracle if they will allow our arm worker to run in a qemu VM > rather than real arm hardware. Is this possible? > > 3. Although ILOM runs oracle linux, the "command line utilities [that] can be expected" are > severely limited (and most of those are busybox, not OL native--that means they work differently > and/or have limited functionality). Can you elaborate on which command line utilities that are > required? > > 4. "Necessary environment variables". We set dozens of them for ILOM builds. I don't know which > (if any) are required for building OpenSSL standalone. Are there any environment variables that > are necessary for building OpenSSL 3.0? > > Thanks. > > Cheers, > > Chris > > Oracle > Chris Brych | Senior Principal Security Analyst > Oracle Security Evaluations - Global Product Security > Ottawa, Ontario | Canada > > +1-905-267-9352 (O) | +1-613-867-1241 (M) > > Gree Oracle is committed to developing practices and products that help protect the environment > > > > > Details we need or want from you > ================================ > > * Worker tag [OPTIONAL]: ILOM_build > > * Worker platform type [MANDATORY]: unix > > (accepted values: 'unix', 'windows') > > * Worker platform identity [OPTIONAL]: oracle linux > > (examples: 'ubuntu', 'ios', 'android', 'win10') > > * Worker platform architecture [OPTIONAL]: x86_64 > > (examples: 'x86', 'x86_64', 'arm', 'ppc') > > * Worker Purpose [MANDATORY, more than one choice allowed]: build (x86_64) > > (accepted values: 'build+test', 'build', 'test') > > * Worker toolchains for building [RECOMMENDED, more than one choice allowed]: gcc > > (examples: 'default', 'gcc', 'clang', 'vs2017', 'vs2019') > > * Necessary environment variables [OPTIONAL]: > > * Necessary configuration target name [OPTIONAL]: linux-generic32 > > * Necessary configuration options [OPTIONAL]: -DL_ENDIAN -DOPENSSL_NO_COMP shared --prefix=/usr --openssldir=/conf/openssl no-zlib no-comp > > * Max number of concurrent builds [OPTIONAL]: > > > What can be expected next > ========================= > > For each form that we receive, we will assign you a full worker name and a > passphrase, and respond to you by email informing you of this and additional > information, such as basic instructions for creating and starting the worker, > what the buildbot status page is, and more. > > > About the details we ask from you > ================================= > > * Worker tag: Short mnemonic. > This will be included in the full name of the worker. If you're not > giving us one, we may make one for you. > > * Worker platform type: this is MANDATORY, because the buildbot master > needs that to determine what command line shell is used (/bin/sh is > assumed for 'unix', cmd.exe is assumed for 'windows') and what command > line utilities can be expected. > > * Worker platform identity: a finer grained identity token, like 'ubuntu', > 'ios', ... this is used to segregates between builds on these different > platforms. If this isn't present, the platform type ('unix' or 'windows') > are used for this segregation. > > * Worker platform architecture: just like the worker platform identity, > this is used to segregate between different builds where it may be > important. This is only necessary if OpenSSL has corresponding config > targets. > > * Worker purpose: What this worker should be used for. This can be used > to have different workers work together with different tasks, for > various reasons. The accepted values are: > > build+test This denotes a "do everything" worker, i.e. it will > get to do 'Configure', 'make' and 'make test'. > > build This denotes a worker that will only build, but not > test. In other words, only 'Configure' and 'make' > will be performed. > If there is any matching worker that's denoted > 'test', the programs and libraries created by this > 'build' worker will be shipped to the worker that is > assigned to perform the test. > > test This denotes a worker that will only test, but not > build. In other words, only 'make test' will be > performed. > > The separate 'build' and 'test' purposes can be used to have one worker > cross compile for some target architecture, and shipping the result to a > worker that is of that architecture and that will perform the tests. > > The separate 'build' and 'test' purposes can be also be used to separate > workers that are quick builders from others that don't build as quickly, > allowing quicker developer turnaround when something needs to be fixed. > > Matching 'build' and 'test' workers are found on the basis of the worker > tag, the platform type or platform identity and the platform architecture, > by forming strings as follows from the worker information, and simply > comparing strings: > > "{worker-tag}-{platform-id}-{platform-arch}" > > "{worker-tag}-{platform-type}-{platform-arch}" > > If no matching 'test' workers are found, then only the build will be > performed. > > NOTE: NOT CURRENTLY IMPLEMENTED! > 'test' workers are currently not implemented, so those works will > currently remain idle. However, we do work on making transfer of files > work smoothly, so they may start to do actual work at some point in the > near future. > > * Worked toolchains for building: This allows a worker to be used > for multiple known building configurations, and is specified as a > list of mnemonics. Multiple choices may be specified. If no > choice is given, 'default' is assumed. > > The current available choices are: > > - 'default' > > This uses whatever happens to be considered default by > OpenSSL's Configure script. > On Unix, that's normally the default C compiler 'cc' and 'make'. > On Windows, that's the MSVC compiler 'cl', 'link' and 'nmake'. > > This toolchain choice expects all the compiling and linking > tools to be set up correctly in the worker. $PATH or %PATH% > and other environment variables must be set up correctly when > the worker is started. > > - 'gcc' and 'clang' > > This uses specific compilers instead of the default 'cc', but > works otherwise like 'default'. > > - 'vs2017', 'vs2017c', vs2017e', 'vs2017p', 'vs2019', 'vs2019c', > 'vs2019e', 'vs2019p' > > These all cover different versions and editions of Microsoft > Visual Studio C, as follows: > > - 'vs2017', 'vs2017c' > > Microsoft Visual Studio 2017, Community edition > > - 'vs2017e' > > Microsoft Visual Studio 2017, Enterprise edition > > - 'vs2017p > > Microsoft Visual Studio 2017, Professional edition > > - 'vs2019', 'vs2019c' > > Microsoft Visual Studio 2019, Community edition > > - 'vs2019e' > > Microsoft Visual Studio 2019, Enterprise edition > > - 'vs2019p > > Microsoft Visual Studio 2019, Professional edition > > OpenSSL's buildbot setup adds extra support for these choices, > by calling the appropriate Visual Studio setup script for each > of them when building, assuming that the setup script is > installed in default places. > > More toolchain choices may be added over time, as the need arises. > > * Necessary environment variables: Environment variables that are > necessary to build properly on the target platform. > This should normally not be needed, but could be in some cases. An > example is Android, where it's necessary to specify the Android root > with ANDROID_NDK_ROOT, and to adjust the PATH accordingly (see > NOTES-ANDROID.md in the OpenSSL 3.0 source) > > * Necessary configuration target name: Explicit configuration target name. > This should normally not be needed, as OpenSSL's configuration script > should be able to detect the target platform automatically. This is > however not always possible, for example when cross compilation is > needed, or when OpenSSL's configuration script doesn't know how to > automatically detect the target platform. > > NOTE: The OpenSSL developers would appreciate if you could tell us how > to automatically detect the configuration target for your platform, if > OpenSSL's configuration script doesn't currently do that. > > * Necessary configuration options: Additional configuration options > necessary to correctly build OpenSSL for the target platform. > This should normally not be needed, but could be in some cases. An > example is Android, where it's necessary to specify the desired Android > API version number using the C macro __ANDROID_API__. > > * Max number of concurrent builds: A limitation for how many builds are > allowed to happen concurrently on this worker. This is suitable when > too many resources would otherwise be used. By default, there is no > limit. > Details we need or want from you > ================================ > > * Worker tag [OPTIONAL]: ILOM_test > > * Worker platform type [MANDATORY]: unix > > (accepted values: 'unix', 'windows') > > * Worker platform identity [OPTIONAL]: oracle linux > > (examples: 'ubuntu', 'ios', 'android', 'win10') > > * Worker platform architecture [OPTIONAL]: arm > > (examples: 'x86', 'x86_64', 'arm', 'ppc') > > * Worker Purpose [MANDATORY, more than one choice allowed]: test (arm) > > (accepted values: 'build+test', 'build', 'test') > > * Worker toolchains for building [RECOMMENDED, more than one choice allowed]: gcc > > (examples: 'default', 'gcc', 'clang', 'vs2017', 'vs2019') > > * Necessary environment variables [OPTIONAL]: > > * Necessary configuration target name [OPTIONAL]: linux-generic32 > > * Necessary configuration options [OPTIONAL]: -DL_ENDIAN -DOPENSSL_NO_COMP shared --prefix=/usr --openssldir=/conf/openssl no-zlib no-comp > > * Max number of concurrent builds [OPTIONAL]: > > > What can be expected next > ========================= > > For each form that we receive, we will assign you a full worker name and a > passphrase, and respond to you by email informing you of this and additional > information, such as basic instructions for creating and starting the worker, > what the buildbot status page is, and more. > > > About the details we ask from you > ================================= > > * Worker tag: Short mnemonic. > This will be included in the full name of the worker. If you're not > giving us one, we may make one for you. > > * Worker platform type: this is MANDATORY, because the buildbot master > needs that to determine what command line shell is used (/bin/sh is > assumed for 'unix', cmd.exe is assumed for 'windows') and what command > line utilities can be expected. > > * Worker platform identity: a finer grained identity token, like 'ubuntu', > 'ios', ... this is used to segregates between builds on these different > platforms. If this isn't present, the platform type ('unix' or 'windows') > are used for this segregation. > > * Worker platform architecture: just like the worker platform identity, > this is used to segregate between different builds where it may be > important. This is only necessary if OpenSSL has corresponding config > targets. > > * Worker purpose: What this worker should be used for. This can be used > to have different workers work together with different tasks, for > various reasons. The accepted values are: > > build+test This denotes a "do everything" worker, i.e. it will > get to do 'Configure', 'make' and 'make test'. > > build This denotes a worker that will only build, but not > test. In other words, only 'Configure' and 'make' > will be performed. > If there is any matching worker that's denoted > 'test', the programs and libraries created by this > 'build' worker will be shipped to the worker that is > assigned to perform the test. > > test This denotes a worker that will only test, but not > build. In other words, only 'make test' will be > performed. > > The separate 'build' and 'test' purposes can be used to have one worker > cross compile for some target architecture, and shipping the result to a > worker that is of that architecture and that will perform the tests. > > The separate 'build' and 'test' purposes can be also be used to separate > workers that are quick builders from others that don't build as quickly, > allowing quicker developer turnaround when something needs to be fixed. > > Matching 'build' and 'test' workers are found on the basis of the worker > tag, the platform type or platform identity and the platform architecture, > by forming strings as follows from the worker information, and simply > comparing strings: > > "{worker-tag}-{platform-id}-{platform-arch}" > > "{worker-tag}-{platform-type}-{platform-arch}" > > If no matching 'test' workers are found, then only the build will be > performed. > > NOTE: NOT CURRENTLY IMPLEMENTED! > 'test' workers are currently not implemented, so those works will > currently remain idle. However, we do work on making transfer of files > work smoothly, so they may start to do actual work at some point in the > near future. > > * Worked toolchains for building: This allows a worker to be used > for multiple known building configurations, and is specified as a > list of mnemonics. Multiple choices may be specified. If no > choice is given, 'default' is assumed. > > The current available choices are: > > - 'default' > > This uses whatever happens to be considered default by > OpenSSL's Configure script. > On Unix, that's normally the default C compiler 'cc' and 'make'. > On Windows, that's the MSVC compiler 'cl', 'link' and 'nmake'. > > This toolchain choice expects all the compiling and linking > tools to be set up correctly in the worker. $PATH or %PATH% > and other environment variables must be set up correctly when > the worker is started. > > - 'gcc' and 'clang' > > This uses specific compilers instead of the default 'cc', but > works otherwise like 'default'. > > - 'vs2017', 'vs2017c', vs2017e', 'vs2017p', 'vs2019', 'vs2019c', > 'vs2019e', 'vs2019p' > > These all cover different versions and editions of Microsoft > Visual Studio C, as follows: > > - 'vs2017', 'vs2017c' > > Microsoft Visual Studio 2017, Community edition > > - 'vs2017e' > > Microsoft Visual Studio 2017, Enterprise edition > > - 'vs2017p > > Microsoft Visual Studio 2017, Professional edition > > - 'vs2019', 'vs2019c' > > Microsoft Visual Studio 2019, Community edition > > - 'vs2019e' > > Microsoft Visual Studio 2019, Enterprise edition > > - 'vs2019p > > Microsoft Visual Studio 2019, Professional edition > > OpenSSL's buildbot setup adds extra support for these choices, > by calling the appropriate Visual Studio setup script for each > of them when building, assuming that the setup script is > installed in default places. > > More toolchain choices may be added over time, as the need arises. > > * Necessary environment variables: Environment variables that are > necessary to build properly on the target platform. > This should normally not be needed, but could be in some cases. An > example is Android, where it's necessary to specify the Android root > with ANDROID_NDK_ROOT, and to adjust the PATH accordingly (see > NOTES-ANDROID.md in the OpenSSL 3.0 source) > > * Necessary configuration target name: Explicit configuration target name. > This should normally not be needed, as OpenSSL's configuration script > should be able to detect the target platform automatically. This is > however not always possible, for example when cross compilation is > needed, or when OpenSSL's configuration script doesn't know how to > automatically detect the target platform. > > NOTE: The OpenSSL developers would appreciate if you could tell us how > to automatically detect the configuration target for your platform, if > OpenSSL's configuration script doesn't currently do that. > > * Necessary configuration options: Additional configuration options > necessary to correctly build OpenSSL for the target platform. > This should normally not be needed, but could be in some cases. An > example is Android, where it's necessary to specify the desired Android > API version number using the C macro __ANDROID_API__. > > * Max number of concurrent builds: A limitation for how many builds are > allowed to happen concurrently on this worker. This is suitable when > too many resources would otherwise be used. By default, there is no > limit. > Details we need or want from you > ================================ > > * Worker tag [OPTIONAL]: Oracle Solaris / SPARC M8 > > * Worker platform type [MANDATORY]: unix > > (accepted values: 'unix', 'windows') > > * Worker platform identity [OPTIONAL]: solaris11 > > (examples: 'ubuntu', 'ios', 'android', 'win10') > > * Worker platform architecture [OPTIONAL]: sparcv9 > > (examples: 'x86', 'x86_64', 'arm', 'ppc') > > * Worker Purpose [MANDATORY, more than one choice allowed]: build+test > > (accepted values: 'build+test', 'build', 'test') > > * Worker toolchains for building [RECOMMENDED, more than one choice allowed]: default (Oracle Developer Studio), gcc > > (examples: 'default', 'gcc', 'clang', 'vs2017', 'vs2019') > > * Necessary environment variables [OPTIONAL]: > > * Necessary configuration target name [OPTIONAL]: solaris64-sparcv9-cc, solaris64-sparcv9-gcc > > * Necessary configuration options [OPTIONAL]: > > * Max number of concurrent builds [OPTIONAL]: > > > What can be expected next > ========================= > > For each form that we receive, we will assign you a full worker name and a > passphrase, and respond to you by email informing you of this and additional > information, such as basic instructions for creating and starting the worker, > what the buildbot status page is, and more. > > > About the details we ask from you > ================================= > > * Worker tag: Short mnemonic. > This will be included in the full name of the worker. If you're not > giving us one, we may make one for you. > > * Worker platform type: this is MANDATORY, because the buildbot master > needs that to determine what command line shell is used (/bin/sh is > assumed for 'unix', cmd.exe is assumed for 'windows') and what command > line utilities can be expected. > > * Worker platform identity: a finer grained identity token, like 'ubuntu', > 'ios', ... this is used to segregates between builds on these different > platforms. If this isn't present, the platform type ('unix' or 'windows') > are used for this segregation. > > * Worker platform architecture: just like the worker platform identity, > this is used to segregate between different builds where it may be > important. This is only necessary if OpenSSL has corresponding config > targets. > > * Worker purpose: What this worker should be used for. This can be used > to have different workers work together with different tasks, for > various reasons. The accepted values are: > > build+test This denotes a "do everything" worker, i.e. it will > get to do 'Configure', 'make' and 'make test'. > > build This denotes a worker that will only build, but not > test. In other words, only 'Configure' and 'make' > will be performed. > If there is any matching worker that's denoted > 'test', the programs and libraries created by this > 'build' worker will be shipped to the worker that is > assigned to perform the test. > > test This denotes a worker that will only test, but not > build. In other words, only 'make test' will be > performed. > > The separate 'build' and 'test' purposes can be used to have one worker > cross compile for some target architecture, and shipping the result to a > worker that is of that architecture and that will perform the tests. > > The separate 'build' and 'test' purposes can be also be used to separate > workers that are quick builders from others that don't build as quickly, > allowing quicker developer turnaround when something needs to be fixed. > > Matching 'build' and 'test' workers are found on the basis of the worker > tag, the platform type or platform identity and the platform architecture, > by forming strings as follows from the worker information, and simply > comparing strings: > > "{worker-tag}-{platform-id}-{platform-arch}" > > "{worker-tag}-{platform-type}-{platform-arch}" > > If no matching 'test' workers are found, then only the build will be > performed. > > NOTE: NOT CURRENTLY IMPLEMENTED! > 'test' workers are currently not implemented, so those works will > currently remain idle. However, we do work on making transfer of files > work smoothly, so they may start to do actual work at some point in the > near future. > > * Worked toolchains for building: This allows a worker to be used > for multiple known building configurations, and is specified as a > list of mnemonics. Multiple choices may be specified. If no > choice is given, 'default' is assumed. > > The current available choices are: > > - 'default' > > This uses whatever happens to be considered default by > OpenSSL's Configure script. > On Unix, that's normally the default C compiler 'cc' and 'make'. > On Windows, that's the MSVC compiler 'cl', 'link' and 'nmake'. > > This toolchain choice expects all the compiling and linking > tools to be set up correctly in the worker. $PATH or %PATH% > and other environment variables must be set up correctly when > the worker is started. > > - 'gcc' and 'clang' > > This uses specific compilers instead of the default 'cc', but > works otherwise like 'default'. > > - 'vs2017', 'vs2017c', vs2017e', 'vs2017p', 'vs2019', 'vs2019c', > 'vs2019e', 'vs2019p' > > These all cover different versions and editions of Microsoft > Visual Studio C, as follows: > > - 'vs2017', 'vs2017c' > > Microsoft Visual Studio 2017, Community edition > > - 'vs2017e' > > Microsoft Visual Studio 2017, Enterprise edition > > - 'vs2017p > > Microsoft Visual Studio 2017, Professional edition > > - 'vs2019', 'vs2019c' > > Microsoft Visual Studio 2019, Community edition > > - 'vs2019e' > > Microsoft Visual Studio 2019, Enterprise edition > > - 'vs2019p > > Microsoft Visual Studio 2019, Professional edition > > OpenSSL's buildbot setup adds extra support for these choices, > by calling the appropriate Visual Studio setup script for each > of them when building, assuming that the setup script is > installed in default places. > > More toolchain choices may be added over time, as the need arises. > > * Necessary environment variables: Environment variables that are > necessary to build properly on the target platform. > This should normally not be needed, but could be in some cases. An > example is Android, where it's necessary to specify the Android root > with ANDROID_NDK_ROOT, and to adjust the PATH accordingly (see > NOTES-ANDROID.md in the OpenSSL 3.0 source) > > * Necessary configuration target name: Explicit configuration target name. > This should normally not be needed, as OpenSSL's configuration script > should be able to detect the target platform automatically. This is > however not always possible, for example when cross compilation is > needed, or when OpenSSL's configuration script doesn't know how to > automatically detect the target platform. > > NOTE: The OpenSSL developers would appreciate if you could tell us how > to automatically detect the configuration target for your platform, if > OpenSSL's configuration script doesn't currently do that. > > * Necessary configuration options: Additional configuration options > necessary to correctly build OpenSSL for the target platform. > This should normally not be needed, but could be in some cases. An > example is Android, where it's necessary to specify the desired Android > API version number using the C macro __ANDROID_API__. > > * Max number of concurrent builds: A limitation for how many builds are > allowed to happen concurrently on this worker. This is suitable when > too many resources would otherwise be used. By default, there is no > limit. > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://mta.openssl.org/mailman/listinfo/buildbot-admin -- Richard Levitte levitte at openssl.org OpenSSL Project http://www.openssl.org/~levitte/ From waliam at vmware.com Wed May 5 10:11:46 2021 From: waliam at vmware.com (Madhur Walia) Date: Wed, 5 May 2021 10:11:46 +0000 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org>, <87wnsgmboj.wl-levitte@openssl.org>, , Message-ID: Hi Richard, Tim, Awaiting further updates. Please assist. Thanks & Regards, Madhur From: Madhur Walia Date: Monday, 3 May 2021 at 8:18 PM To: Richard Levitte Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav , buildbot-admin at openssl.org Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers Hi Richard, We have installed git on Photon, please let us know next steps. Installed buildbot and VS2017 on Windows 2019 as shown below but the connection seems to be dropping, Versions installed on Windows 2019, [Text Description automatically generated] Win2019: Connection Failing, going in a loop, [Graphical user interface, text Description automatically generated] Thanks & Regards, Madhur From: Madhur Walia Date: Monday, 3 May 2021 at 2:37 PM To: Richard Levitte Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav , buildbot-admin at openssl.org Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers Hi Richard, Thank you for the help. We had only installed buildbot-worker on Photon4 and Windows 2019. After installing Buildbot (master) on Photon4, the worker could start. We are now working on installing git on Photon4 and then troubleshooting Windows 2019. I will keep you updated. Regards, Madhur From: Richard Levitte Date: Monday, 3 May 2021 at 2:33 PM To: Madhur Walia Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav , buildbot-admin at openssl.org Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers I now noticed that the Photon 4 workers have connected, so I assume the 'optionsForClientTLS' is a thing of the past. Looking at one of the builds, https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108009695%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=W5ZizgajStLZh0p1sbhmwbEIonCMSQdhuH0ZcEDHETc%3D&reserved=0, it looks like git isn't installed on the worker... Cheers, Richard On Mon, 03 May 2021 10:34:57 +0200, Richard Levitte wrote: > > On Mon, 26 Apr 2021 20:25:34 +0200, > Madhur Walia wrote: > > > > Hi Matt, > > > > Thank you for the instructions. However, we are facing couple of issues while starting buildbot-worker, > > > > For both platforms, we pointed Certificate/SSL settings to a custom directory in buildbot.tac as per your recommendation. We also tried importing both certs, isrg-root-xi & lets-encrypt-r3 to trust store of OS but no luck. > > > > Photon, > > Getting error, " builtins.NameError: name 'optionsForClientTLS' is not defined" as shown in Photon1 screenshot attached. > > Also ran a curl command to check SSL connectivity, seems to be failing, attached screenshot Photon2. > > Please check your versions of the following packages: > > - buildbot (should be at least version 2.6.0) > - twisted (should be at least version 17.9.0 according to buildbot > 2.6.0 requirements) > > 'optionsForClientTLS' is a method that appeared in twisted version 14.0. > > > Windows, > > Getting, "Unicode error" as shown in Windows1 screenshot attached. > > Also ran a curl command to check SSL connectivity, seems to be failing, attached screenshot Windows2. > > From the error message at the end of Windows1.png, you have an invalid > unicode character on line 30. Could it be a character with diacritics > not encoded with UTF-8? > > Cheers, > Richard > > > Do you have any pointers on these errors? Please let us know. > > > > Thanks & Regards, > > Madhur > > > > ------------------------------------------------------------------ > > > > ?On 21/04/21, 4:47 PM, "Matt Caswell" wrote: > > > > Thanks Manoj. > > > > To be able to set up your worker, you must use version 2.6.0 or > > higher. Older version do not support TLS-protected connections. > > > > Please see these instructions for installing the buildbot worker > > software: > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TcoREUxnTLQ5%2F28PqDL83I9d16%2BuhxCTZpbuiEqF0sM%3D&reserved=0 > > > > When buildbot has been installed on the platform where the buildbot > > worker is to be run, this is how a worker is created (for your PhotonOS > > worker): > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > buildbot.openssl.org:9989 vmware-photonos40 nifs0Tweex_ > > > > And for your Windows server: > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > buildbot.openssl.org:9989 vmware-winserver2019 Efyin.Freg0 > > > > > > where BASEDIR is determined by you. See further down for a few notes > > on TLS. > > > > To run a buildbot worker, you do this: > > > > $ buildbot-worker start BASEDIR > > > > Apart from the software needed to run a buildbot worker, and the > > utilities that are the normal part of the operating system, you also > > need to ensure that the following components are available: > > > > - toolchains, i.e. C compiler, linker, make. If you have specified > > toolchains in the worker request form, you need to ensure that all > > of them are installed. > > > > - git > > > > Regarding TLS, it may be that the buildbot worker platform doesn't > > have the appropriate certification verification roots set up. In that > > case, you may need to apply the attached buildbot.tac patch, and store > > the attached PEM files in a directory of your choice. Finish up by > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with > > the path of directory where you stored the PEM files. > > > > Matt > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > Hi Tim & Richard, > > > > > > We have filled out the worker-request-form for 2 of our platforms, one unix type and other Windows. Also, the platforms, for your convenience am listing here: > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 (Platform type: Unix, x86_64, build+test, gcc) > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > Please provide the credentials and instruction on setting up the buildbot worker. > > > > > > Thanks, > > > Manoj > > > > > > > > > -----Original Message----- > > > From: fips-sponsors On Behalf Of Richard Levitte > > > Sent: Monday, April 12, 2021 12:20 AM > > > To: fips-sponsors at openssl.org > > > Subject: [fips-sponsors] Buildbot workers > > > > > > Hi, > > > > > > We are finally ready to start getting buildbot worker requests. > > > > > > The way this will work is that we're asking you to answer a form with details for each worker you want to set up for us, such as what platform, what architecture, and where relevant, what toolchains are installed. > > > > > > The form is attached below, and include explanations for all the fields to fill in. Please send it to buildbot-admin at openssl.org. > > > > > > In response, you will receive an email with the name and password we assign your worker(s), and instructions how to set the worker up. > > > > > > > [2 Photon1.png ] > > > > [3 Photon2.png ] > > > > [4 Windows1.png ] > > > > [5 Windows2.png ] > > > > [6 ] > > _______________________________________________ > > buildbot-admin mailing list > > buildbot-admin at openssl.org > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Bxq8pym%2BcZFZJx2ldzclbifh9LBrQxRzYlMgVP9AjOA%3D&reserved=0 > -- > Richard Levitte levitte at openssl.org > OpenSSL Project https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qwVUH49lHuZBsNdculwt63fEiEPbIK%2BCXc61EmipXbA%3D&reserved=0 > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Bxq8pym%2BcZFZJx2ldzclbifh9LBrQxRzYlMgVP9AjOA%3D&reserved=0 -- Richard Levitte levitte at openssl.org OpenSSL Project https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qwVUH49lHuZBsNdculwt63fEiEPbIK%2BCXc61EmipXbA%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 155786 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 413175 bytes Desc: image002.png URL: From levitte at openssl.org Wed May 5 15:07:49 2021 From: levitte at openssl.org (Richard Levitte) Date: Wed, 05 May 2021 17:07:49 +0200 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org> Message-ID: <87a6p9w75m.wl-levitte@openssl.org> As far as I can tell, The Photon 4 worker is good. The fact that "make test" currently fails isn't a problem with the worker as far as I can see... our development team will have to look at it. As for the Windows worker, it doesn't seem to connect. Have you verified that the two .pem files are in the directory that's specified in buildbot.tac? Cheers, Richard On Wed, 05 May 2021 12:11:46 +0200, Madhur Walia wrote: > > > Hi Richard, Tim, > > Awaiting further updates. Please assist. > > Thanks & Regards, > > Madhur > > From: Madhur Walia > Date: Monday, 3 May 2021 at 8:18 PM > To: Richard Levitte > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > , buildbot-admin at openssl.org > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > Hi Richard, > > We have installed git on Photon, please let us know next steps. > > Installed buildbot and VS2017 on Windows 2019 as shown below but the connection seems to be > dropping, > > Versions installed on Windows 2019, > > TextDescription automatically generated > > Win2019: Connection Failing, going in a loop, > > Graphical user interface, textDescription automatically generated > > Thanks & Regards, > > Madhur > > From: Madhur Walia > Date: Monday, 3 May 2021 at 2:37 PM > To: Richard Levitte > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > , buildbot-admin at openssl.org > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > Hi Richard, > > Thank you for the help. We had only installed buildbot-worker on Photon4 and Windows 2019. After > installing Buildbot (master) on Photon4, the worker could start. > > We are now working on installing git on Photon4 and then troubleshooting Windows 2019. I will keep > you updated. > > Regards, > > Madhur > > From: Richard Levitte > Date: Monday, 3 May 2021 at 2:33 PM > To: Madhur Walia > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > , buildbot-admin at openssl.org > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > I now noticed that the Photon 4 workers have connected, so I assume > the 'optionsForClientTLS' is a thing of the past. > > Looking at one of the builds, > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108009695%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=W5ZizgajStLZh0p1sbhmwbEIonCMSQdhuH0ZcEDHETc%3D&reserved=0 > , > it looks like git isn't installed on the worker... > > Cheers, > Richard > > On Mon, 03 May 2021 10:34:57 +0200, > Richard Levitte wrote: > > > > On Mon, 26 Apr 2021 20:25:34 +0200, > > Madhur Walia wrote: > > > > > > Hi Matt, > > > > > > Thank you for the instructions. However, we are facing couple of issues while starting > buildbot-worker, > > > > > > For both platforms, we pointed Certificate/SSL settings to a custom directory in buildbot.tac > as per your recommendation. We also tried importing both certs, isrg-root-xi & lets-encrypt-r3 to > trust store of OS but no luck. > > > > > > Photon, > > > Getting error, " builtins.NameError: name 'optionsForClientTLS' is not defined" as shown > in Photon1 screenshot attached. > > > Also ran a curl command to check SSL connectivity, seems to be failing, attached > screenshot Photon2. > > > > Please check your versions of the following packages: > > > > - buildbot (should be at least version 2.6.0) > > - twisted (should be at least version 17.9.0 according to buildbot > > 2.6.0 requirements) > > > > 'optionsForClientTLS' is a method that appeared in twisted version 14.0. > > > > > Windows, > > > Getting, "Unicode error" as shown in Windows1 screenshot attached. > > > Also ran a curl command to check SSL connectivity, seems to be failing, attached > screenshot Windows2. > > > > From the error message at the end of Windows1.png, you have an invalid > > unicode character on line 30. Could it be a character with diacritics > > not encoded with UTF-8? > > > > Cheers, > > Richard > > > > > Do you have any pointers on these errors? Please let us know. > > > > > > Thanks & Regards, > > > Madhur > > > > > > ------------------------------------------------------------------ > > > > > > On 21/04/21, 4:47 PM, "Matt Caswell" wrote: > > > > > > Thanks Manoj. > > > > > > To be able to set up your worker, you must use version 2.6.0 or > > > higher. Older version do not support TLS-protected connections. > > > > > > Please see these instructions for installing the buildbot worker > > > software: > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TcoREUxnTLQ5%2F28PqDL83I9d16%2BuhxCTZpbuiEqF0sM%3D&reserved=0 > > > > > > When buildbot has been installed on the platform where the buildbot > > > worker is to be run, this is how a worker is created (for your PhotonOS > > > worker): > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > buildbot.openssl.org:9989 vmware-photonos40 nifs0Tweex_ > > > > > > And for your Windows server: > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > buildbot.openssl.org:9989 vmware-winserver2019 Efyin.Freg0 > > > > > > > > > where BASEDIR is determined by you. See further down for a few notes > > > on TLS. > > > > > > To run a buildbot worker, you do this: > > > > > > $ buildbot-worker start BASEDIR > > > > > > Apart from the software needed to run a buildbot worker, and the > > > utilities that are the normal part of the operating system, you also > > > need to ensure that the following components are available: > > > > > > - toolchains, i.e. C compiler, linker, make. If you have specified > > > toolchains in the worker request form, you need to ensure that all > > > of them are installed. > > > > > > - git > > > > > > Regarding TLS, it may be that the buildbot worker platform doesn't > > > have the appropriate certification verification roots set up. In that > > > case, you may need to apply the attached buildbot.tac patch, and store > > > the attached PEM files in a directory of your choice. Finish up by > > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with > > > the path of directory where you stored the PEM files. > > > > > > Matt > > > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > > Hi Tim & Richard, > > > > > > > > We have filled out the worker-request-form for 2 of our platforms, one unix type and > other Windows. Also, the platforms, for your convenience am listing here: > > > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 > (Platform type: Unix, x86_64, build+test, gcc) > > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge > R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > > > Please provide the credentials and instruction on setting up the buildbot worker. > > > > > > > > Thanks, > > > > Manoj > > > > > > > > > > > > -----Original Message----- > > > > From: fips-sponsors On Behalf Of Richard Levitte > > > > Sent: Monday, April 12, 2021 12:20 AM > > > > To: fips-sponsors at openssl.org > > > > Subject: [fips-sponsors] Buildbot workers > > > > > > > > Hi, > > > > > > > > We are finally ready to start getting buildbot worker requests. > > > > > > > > The way this will work is that we're asking you to answer a form with details for each > worker you want to set up for us, such as what platform, what architecture, and where relevant, > what toolchains are installed. > > > > > > > > The form is attached below, and include explanations for all the fields to fill in. > Please send it to buildbot-admin at openssl.org. > > > > > > > > In response, you will receive an email with the name and password we assign your worker > (s), and instructions how to set the worker up. > > > > > > > > > > [2 Photon1.png ] > > > > > > [3 Photon2.png ] > > > > > > [4 Windows1.png ] > > > > > > [5 Windows2.png ] > > > > > > [6 ] > > > _______________________________________________ > > > buildbot-admin mailing list > > > buildbot-admin at openssl.org > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Bxq8pym%2BcZFZJx2ldzclbifh9LBrQxRzYlMgVP9AjOA%3D&reserved=0 > > -- > > Richard Levitte levitte at openssl.org > > OpenSSL Project > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qwVUH49lHuZBsNdculwt63fEiEPbIK%2BCXc61EmipXbA%3D&reserved=0 > > _______________________________________________ > > buildbot-admin mailing list > > buildbot-admin at openssl.org > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Bxq8pym%2BcZFZJx2ldzclbifh9LBrQxRzYlMgVP9AjOA%3D&reserved=0 > -- > Richard Levitte levitte at openssl.org > OpenSSL Project > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Cd53de2e984e54c66d0a408d90e125063%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637556294108019642%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qwVUH49lHuZBsNdculwt63fEiEPbIK%2BCXc61EmipXbA%3D&reserved=0 > > > > -- Richard Levitte levitte at openssl.org OpenSSL Project http://www.openssl.org/~levitte/ From waliam at vmware.com Thu May 6 16:34:49 2021 From: waliam at vmware.com (Madhur Walia) Date: Thu, 6 May 2021 16:34:49 +0000 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: <87a6p9w75m.wl-levitte@openssl.org> References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org>,<87a6p9w75m.wl-levitte@openssl.org> Message-ID: Thank you Richard. So, Photon 4.0 seems to be okay for now and next update would be from your development team. We captured a wireshark trace keeping default buildbot.tac and could see ?Unknown CA? error. We then pointed the trustroots/ ssl-root-dir to a custom path (to pem files), and encountered another error which points to failure in trusting CA certificate filepath. [Text Description automatically generated] We tried pointing trustroots directory to absolute certificate directory path but no luck. Other debugging steps involves, ? Running ?openssl s_client -state -debug -connect buildbot.openssl.org:9989? which gives Verification: OK if we point the -CAfile to Hashed CA pem file names/ location. ? Executing, a python code to verify against CA file path, which shows a successful CA trust in Wireshark, import os import requests r=requests.get('https://buildbot.openssl.org:9989',verify='C:/Certificates/a.pem') [Graphical user interface, text, application Description automatically generated] This either seems to be a platform, (Windows) specific issue or something related to twisted OR something very miniscule that @Sunil Kumar Yadav and I are unable to catch. I can schedule a call to discuss this in more depth keeping in mind we are almost near to completion of 3~4 weeks window. Please let me know, Sunil and I are based out of India, IST time zone. We can talk during IST evening, Your Morning. Thanks & Regards, Madhur From: Richard Levitte Date: Wednesday, 5 May 2021 at 8:37 PM To: Madhur Walia Cc: Richard Levitte , Manoj Maskara , Tim Hudson , Sunil Kumar Yadav , buildbot-admin at openssl.org Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers As far as I can tell, The Photon 4 worker is good. The fact that "make test" currently fails isn't a problem with the worker as far as I can see... our development team will have to look at it. As for the Windows worker, it doesn't seem to connect. Have you verified that the two .pem files are in the directory that's specified in buildbot.tac? Cheers, Richard On Wed, 05 May 2021 12:11:46 +0200, Madhur Walia wrote: > > > Hi Richard, Tim, > > Awaiting further updates. Please assist. > > Thanks & Regards, > > Madhur > > From: Madhur Walia > Date: Monday, 3 May 2021 at 8:18 PM > To: Richard Levitte > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > , buildbot-admin at openssl.org > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > Hi Richard, > > We have installed git on Photon, please let us know next steps. > > Installed buildbot and VS2017 on Windows 2019 as shown below but the connection seems to be > dropping, > > Versions installed on Windows 2019, > > TextDescription automatically generated > > Win2019: Connection Failing, going in a loop, > > Graphical user interface, textDescription automatically generated > > Thanks & Regards, > > Madhur > > From: Madhur Walia > Date: Monday, 3 May 2021 at 2:37 PM > To: Richard Levitte > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > , buildbot-admin at openssl.org > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > Hi Richard, > > Thank you for the help. We had only installed buildbot-worker on Photon4 and Windows 2019. After > installing Buildbot (master) on Photon4, the worker could start. > > We are now working on installing git on Photon4 and then troubleshooting Windows 2019. I will keep > you updated. > > Regards, > > Madhur > > From: Richard Levitte > Date: Monday, 3 May 2021 at 2:33 PM > To: Madhur Walia > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > , buildbot-admin at openssl.org > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > I now noticed that the Photon 4 workers have connected, so I assume > the 'optionsForClientTLS' is a thing of the past. > > Looking at one of the builds, > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773314526%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=bTWIbaGcnmKdXIdDEd5ECwUso%2BTp46PH0kGQy9K5RxE%3D&reserved=0 > , > it looks like git isn't installed on the worker... > > Cheers, > Richard > > On Mon, 03 May 2021 10:34:57 +0200, > Richard Levitte wrote: > > > > On Mon, 26 Apr 2021 20:25:34 +0200, > > Madhur Walia wrote: > > > > > > Hi Matt, > > > > > > Thank you for the instructions. However, we are facing couple of issues while starting > buildbot-worker, > > > > > > For both platforms, we pointed Certificate/SSL settings to a custom directory in buildbot.tac > as per your recommendation. We also tried importing both certs, isrg-root-xi & lets-encrypt-r3 to > trust store of OS but no luck. > > > > > > Photon, > > > Getting error, " builtins.NameError: name 'optionsForClientTLS' is not defined" as shown > in Photon1 screenshot attached. > > > Also ran a curl command to check SSL connectivity, seems to be failing, attached > screenshot Photon2. > > > > Please check your versions of the following packages: > > > > - buildbot (should be at least version 2.6.0) > > - twisted (should be at least version 17.9.0 according to buildbot > > 2.6.0 requirements) > > > > 'optionsForClientTLS' is a method that appeared in twisted version 14.0. > > > > > Windows, > > > Getting, "Unicode error" as shown in Windows1 screenshot attached. > > > Also ran a curl command to check SSL connectivity, seems to be failing, attached > screenshot Windows2. > > > > From the error message at the end of Windows1.png, you have an invalid > > unicode character on line 30. Could it be a character with diacritics > > not encoded with UTF-8? > > > > Cheers, > > Richard > > > > > Do you have any pointers on these errors? Please let us know. > > > > > > Thanks & Regards, > > > Madhur > > > > > > ------------------------------------------------------------------ > > > > > > On 21/04/21, 4:47 PM, "Matt Caswell" wrote: > > > > > > Thanks Manoj. > > > > > > To be able to set up your worker, you must use version 2.6.0 or > > > higher. Older version do not support TLS-protected connections. > > > > > > Please see these instructions for installing the buildbot worker > > > software: > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=aIqqCC7%2BGjXcO8FYrpITEz44kSoNZIhqC0mhcEUfdxA%3D&reserved=0 > > > > > > When buildbot has been installed on the platform where the buildbot > > > worker is to be run, this is how a worker is created (for your PhotonOS > > > worker): > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > buildbot.openssl.org:9989 vmware-photonos40 nifs0Tweex_ > > > > > > And for your Windows server: > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > buildbot.openssl.org:9989 vmware-winserver2019 Efyin.Freg0 > > > > > > > > > where BASEDIR is determined by you. See further down for a few notes > > > on TLS. > > > > > > To run a buildbot worker, you do this: > > > > > > $ buildbot-worker start BASEDIR > > > > > > Apart from the software needed to run a buildbot worker, and the > > > utilities that are the normal part of the operating system, you also > > > need to ensure that the following components are available: > > > > > > - toolchains, i.e. C compiler, linker, make. If you have specified > > > toolchains in the worker request form, you need to ensure that all > > > of them are installed. > > > > > > - git > > > > > > Regarding TLS, it may be that the buildbot worker platform doesn't > > > have the appropriate certification verification roots set up. In that > > > case, you may need to apply the attached buildbot.tac patch, and store > > > the attached PEM files in a directory of your choice. Finish up by > > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with > > > the path of directory where you stored the PEM files. > > > > > > Matt > > > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > > Hi Tim & Richard, > > > > > > > > We have filled out the worker-request-form for 2 of our platforms, one unix type and > other Windows. Also, the platforms, for your convenience am listing here: > > > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 > (Platform type: Unix, x86_64, build+test, gcc) > > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge > R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > > > Please provide the credentials and instruction on setting up the buildbot worker. > > > > > > > > Thanks, > > > > Manoj > > > > > > > > > > > > -----Original Message----- > > > > From: fips-sponsors On Behalf Of Richard Levitte > > > > Sent: Monday, April 12, 2021 12:20 AM > > > > To: fips-sponsors at openssl.org > > > > Subject: [fips-sponsors] Buildbot workers > > > > > > > > Hi, > > > > > > > > We are finally ready to start getting buildbot worker requests. > > > > > > > > The way this will work is that we're asking you to answer a form with details for each > worker you want to set up for us, such as what platform, what architecture, and where relevant, > what toolchains are installed. > > > > > > > > The form is attached below, and include explanations for all the fields to fill in. > Please send it to buildbot-admin at openssl.org. > > > > > > > > In response, you will receive an email with the name and password we assign your worker > (s), and instructions how to set the worker up. > > > > > > > > > > [2 Photon1.png ] > > > > > > [3 Photon2.png ] > > > > > > [4 Windows1.png ] > > > > > > [5 Windows2.png ] > > > > > > [6 ] > > > _______________________________________________ > > > buildbot-admin mailing list > > > buildbot-admin at openssl.org > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=w%2Fb33IBbvdzc0g9S6JI6gPrjj6P5X%2BKhbVzW9Yb%2FfhU%3D&reserved=0 > > -- > > Richard Levitte levitte at openssl.org > > OpenSSL Project > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vCqwTrH2UYa0g9%2Bm906P0FnvjoJVc3o%2B89%2BhYBC2x3A%3D&reserved=0 > > _______________________________________________ > > buildbot-admin mailing list > > buildbot-admin at openssl.org > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=w%2Fb33IBbvdzc0g9S6JI6gPrjj6P5X%2BKhbVzW9Yb%2FfhU%3D&reserved=0 > -- > Richard Levitte levitte at openssl.org > OpenSSL Project > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vCqwTrH2UYa0g9%2Bm906P0FnvjoJVc3o%2B89%2BhYBC2x3A%3D&reserved=0 > > > > -- Richard Levitte levitte at openssl.org OpenSSL Project https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vCqwTrH2UYa0g9%2Bm906P0FnvjoJVc3o%2B89%2BhYBC2x3A%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 2231737 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 553231 bytes Desc: image002.png URL: From waliam at vmware.com Fri May 7 07:51:22 2021 From: waliam at vmware.com (Madhur Walia) Date: Fri, 7 May 2021 07:51:22 +0000 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org>, <87a6p9w75m.wl-levitte@openssl.org>, Message-ID: Hi Richard, We are able to connect to Buildbot Master from Windows 2019 as well now. To our surprise, Buildbot-worker/ Python was searching for Certificate directory in base directory. After pointing ssl-root-dir to a directory hosted in base directory, it was able to connect. Please confirm the connection. Also, What are the next steps for Photon 4 and Windows 2019 now? Thank you for your inputs. Regards, Madhur From: Madhur Walia Date: Thursday, 6 May 2021 at 10:04 PM To: Richard Levitte , Sunil Kumar Yadav Cc: Richard Levitte , Manoj Maskara , Tim Hudson , buildbot-admin at openssl.org Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers Thank you Richard. So, Photon 4.0 seems to be okay for now and next update would be from your development team. We captured a wireshark trace keeping default buildbot.tac and could see ?Unknown CA? error. We then pointed the trustroots/ ssl-root-dir to a custom path (to pem files), and encountered another error which points to failure in trusting CA certificate filepath. [Text Description automatically generated] We tried pointing trustroots directory to absolute certificate directory path but no luck. Other debugging steps involves, ? Running ?openssl s_client -state -debug -connect buildbot.openssl.org:9989? which gives Verification: OK if we point the -CAfile to Hashed CA pem file names/ location. ? Executing, a python code to verify against CA file path, which shows a successful CA trust in Wireshark, import os import requests r=requests.get('https://buildbot.openssl.org:9989',verify='C:/Certificates/a.pem') [Graphical user interface, text, application Description automatically generated] This either seems to be a platform, (Windows) specific issue or something related to twisted OR something very miniscule that @Sunil Kumar Yadav and I are unable to catch. I can schedule a call to discuss this in more depth keeping in mind we are almost near to completion of 3~4 weeks window. Please let me know, Sunil and I are based out of India, IST time zone. We can talk during IST evening, Your Morning. Thanks & Regards, Madhur From: Richard Levitte Date: Wednesday, 5 May 2021 at 8:37 PM To: Madhur Walia Cc: Richard Levitte , Manoj Maskara , Tim Hudson , Sunil Kumar Yadav , buildbot-admin at openssl.org Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers As far as I can tell, The Photon 4 worker is good. The fact that "make test" currently fails isn't a problem with the worker as far as I can see... our development team will have to look at it. As for the Windows worker, it doesn't seem to connect. Have you verified that the two .pem files are in the directory that's specified in buildbot.tac? Cheers, Richard On Wed, 05 May 2021 12:11:46 +0200, Madhur Walia wrote: > > > Hi Richard, Tim, > > Awaiting further updates. Please assist. > > Thanks & Regards, > > Madhur > > From: Madhur Walia > Date: Monday, 3 May 2021 at 8:18 PM > To: Richard Levitte > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > , buildbot-admin at openssl.org > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > Hi Richard, > > We have installed git on Photon, please let us know next steps. > > Installed buildbot and VS2017 on Windows 2019 as shown below but the connection seems to be > dropping, > > Versions installed on Windows 2019, > > TextDescription automatically generated > > Win2019: Connection Failing, going in a loop, > > Graphical user interface, textDescription automatically generated > > Thanks & Regards, > > Madhur > > From: Madhur Walia > Date: Monday, 3 May 2021 at 2:37 PM > To: Richard Levitte > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > , buildbot-admin at openssl.org > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > Hi Richard, > > Thank you for the help. We had only installed buildbot-worker on Photon4 and Windows 2019. After > installing Buildbot (master) on Photon4, the worker could start. > > We are now working on installing git on Photon4 and then troubleshooting Windows 2019. I will keep > you updated. > > Regards, > > Madhur > > From: Richard Levitte > Date: Monday, 3 May 2021 at 2:33 PM > To: Madhur Walia > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > , buildbot-admin at openssl.org > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > I now noticed that the Photon 4 workers have connected, so I assume > the 'optionsForClientTLS' is a thing of the past. > > Looking at one of the builds, > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773314526%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=bTWIbaGcnmKdXIdDEd5ECwUso%2BTp46PH0kGQy9K5RxE%3D&reserved=0 > , > it looks like git isn't installed on the worker... > > Cheers, > Richard > > On Mon, 03 May 2021 10:34:57 +0200, > Richard Levitte wrote: > > > > On Mon, 26 Apr 2021 20:25:34 +0200, > > Madhur Walia wrote: > > > > > > Hi Matt, > > > > > > Thank you for the instructions. However, we are facing couple of issues while starting > buildbot-worker, > > > > > > For both platforms, we pointed Certificate/SSL settings to a custom directory in buildbot.tac > as per your recommendation. We also tried importing both certs, isrg-root-xi & lets-encrypt-r3 to > trust store of OS but no luck. > > > > > > Photon, > > > Getting error, " builtins.NameError: name 'optionsForClientTLS' is not defined" as shown > in Photon1 screenshot attached. > > > Also ran a curl command to check SSL connectivity, seems to be failing, attached > screenshot Photon2. > > > > Please check your versions of the following packages: > > > > - buildbot (should be at least version 2.6.0) > > - twisted (should be at least version 17.9.0 according to buildbot > > 2.6.0 requirements) > > > > 'optionsForClientTLS' is a method that appeared in twisted version 14.0. > > > > > Windows, > > > Getting, "Unicode error" as shown in Windows1 screenshot attached. > > > Also ran a curl command to check SSL connectivity, seems to be failing, attached > screenshot Windows2. > > > > From the error message at the end of Windows1.png, you have an invalid > > unicode character on line 30. Could it be a character with diacritics > > not encoded with UTF-8? > > > > Cheers, > > Richard > > > > > Do you have any pointers on these errors? Please let us know. > > > > > > Thanks & Regards, > > > Madhur > > > > > > ------------------------------------------------------------------ > > > > > > On 21/04/21, 4:47 PM, "Matt Caswell" wrote: > > > > > > Thanks Manoj. > > > > > > To be able to set up your worker, you must use version 2.6.0 or > > > higher. Older version do not support TLS-protected connections. > > > > > > Please see these instructions for installing the buildbot worker > > > software: > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=aIqqCC7%2BGjXcO8FYrpITEz44kSoNZIhqC0mhcEUfdxA%3D&reserved=0 > > > > > > When buildbot has been installed on the platform where the buildbot > > > worker is to be run, this is how a worker is created (for your PhotonOS > > > worker): > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > buildbot.openssl.org:9989 vmware-photonos40 nifs0Tweex_ > > > > > > And for your Windows server: > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > buildbot.openssl.org:9989 vmware-winserver2019 Efyin.Freg0 > > > > > > > > > where BASEDIR is determined by you. See further down for a few notes > > > on TLS. > > > > > > To run a buildbot worker, you do this: > > > > > > $ buildbot-worker start BASEDIR > > > > > > Apart from the software needed to run a buildbot worker, and the > > > utilities that are the normal part of the operating system, you also > > > need to ensure that the following components are available: > > > > > > - toolchains, i.e. C compiler, linker, make. If you have specified > > > toolchains in the worker request form, you need to ensure that all > > > of them are installed. > > > > > > - git > > > > > > Regarding TLS, it may be that the buildbot worker platform doesn't > > > have the appropriate certification verification roots set up. In that > > > case, you may need to apply the attached buildbot.tac patch, and store > > > the attached PEM files in a directory of your choice. Finish up by > > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with > > > the path of directory where you stored the PEM files. > > > > > > Matt > > > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > > Hi Tim & Richard, > > > > > > > > We have filled out the worker-request-form for 2 of our platforms, one unix type and > other Windows. Also, the platforms, for your convenience am listing here: > > > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 > (Platform type: Unix, x86_64, build+test, gcc) > > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge > R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > > > Please provide the credentials and instruction on setting up the buildbot worker. > > > > > > > > Thanks, > > > > Manoj > > > > > > > > > > > > -----Original Message----- > > > > From: fips-sponsors On Behalf Of Richard Levitte > > > > Sent: Monday, April 12, 2021 12:20 AM > > > > To: fips-sponsors at openssl.org > > > > Subject: [fips-sponsors] Buildbot workers > > > > > > > > Hi, > > > > > > > > We are finally ready to start getting buildbot worker requests. > > > > > > > > The way this will work is that we're asking you to answer a form with details for each > worker you want to set up for us, such as what platform, what architecture, and where relevant, > what toolchains are installed. > > > > > > > > The form is attached below, and include explanations for all the fields to fill in. > Please send it to buildbot-admin at openssl.org. > > > > > > > > In response, you will receive an email with the name and password we assign your worker > (s), and instructions how to set the worker up. > > > > > > > > > > [2 Photon1.png ] > > > > > > [3 Photon2.png ] > > > > > > [4 Windows1.png ] > > > > > > [5 Windows2.png ] > > > > > > [6 ] > > > _______________________________________________ > > > buildbot-admin mailing list > > > buildbot-admin at openssl.org > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=w%2Fb33IBbvdzc0g9S6JI6gPrjj6P5X%2BKhbVzW9Yb%2FfhU%3D&reserved=0 > > -- > > Richard Levitte levitte at openssl.org > > OpenSSL Project > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vCqwTrH2UYa0g9%2Bm906P0FnvjoJVc3o%2B89%2BhYBC2x3A%3D&reserved=0 > > _______________________________________________ > > buildbot-admin mailing list > > buildbot-admin at openssl.org > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=w%2Fb33IBbvdzc0g9S6JI6gPrjj6P5X%2BKhbVzW9Yb%2FfhU%3D&reserved=0 > -- > Richard Levitte levitte at openssl.org > OpenSSL Project > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vCqwTrH2UYa0g9%2Bm906P0FnvjoJVc3o%2B89%2BhYBC2x3A%3D&reserved=0 > > > > -- Richard Levitte levitte at openssl.org OpenSSL Project https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vCqwTrH2UYa0g9%2Bm906P0FnvjoJVc3o%2B89%2BhYBC2x3A%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 2231739 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 553233 bytes Desc: image002.png URL: From waliam at vmware.com Tue May 11 06:19:14 2021 From: waliam at vmware.com (Madhur Walia) Date: Tue, 11 May 2021 06:19:14 +0000 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org>, <87a6p9w75m.wl-levitte@openssl.org>, , Message-ID: Hi Richard, Tim, Gentle Reminder. Thanks & Regards, Madhur From: Madhur Walia Date: Friday, 7 May 2021 at 1:21 PM To: Richard Levitte , Sunil Kumar Yadav Cc: Manoj Maskara , Tim Hudson , buildbot-admin at openssl.org , Bishakha Banerjee Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers Hi Richard, We are able to connect to Buildbot Master from Windows 2019 as well now. To our surprise, Buildbot-worker/ Python was searching for Certificate directory in base directory. After pointing ssl-root-dir to a directory hosted in base directory, it was able to connect. Please confirm the connection. Also, What are the next steps for Photon 4 and Windows 2019 now? Thank you for your inputs. Regards, Madhur From: Madhur Walia Date: Thursday, 6 May 2021 at 10:04 PM To: Richard Levitte , Sunil Kumar Yadav Cc: Richard Levitte , Manoj Maskara , Tim Hudson , buildbot-admin at openssl.org Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers Thank you Richard. So, Photon 4.0 seems to be okay for now and next update would be from your development team. We captured a wireshark trace keeping default buildbot.tac and could see ?Unknown CA? error. We then pointed the trustroots/ ssl-root-dir to a custom path (to pem files), and encountered another error which points to failure in trusting CA certificate filepath. [Text Description automatically generated] We tried pointing trustroots directory to absolute certificate directory path but no luck. Other debugging steps involves, ? Running ?openssl s_client -state -debug -connect buildbot.openssl.org:9989? which gives Verification: OK if we point the -CAfile to Hashed CA pem file names/ location. ? Executing, a python code to verify against CA file path, which shows a successful CA trust in Wireshark, import os import requests r=requests.get('https://buildbot.openssl.org:9989',verify='C:/Certificates/a.pem') [Graphical user interface, text, application Description automatically generated] This either seems to be a platform, (Windows) specific issue or something related to twisted OR something very miniscule that @Sunil Kumar Yadav and I are unable to catch. I can schedule a call to discuss this in more depth keeping in mind we are almost near to completion of 3~4 weeks window. Please let me know, Sunil and I are based out of India, IST time zone. We can talk during IST evening, Your Morning. Thanks & Regards, Madhur From: Richard Levitte Date: Wednesday, 5 May 2021 at 8:37 PM To: Madhur Walia Cc: Richard Levitte , Manoj Maskara , Tim Hudson , Sunil Kumar Yadav , buildbot-admin at openssl.org Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers As far as I can tell, The Photon 4 worker is good. The fact that "make test" currently fails isn't a problem with the worker as far as I can see... our development team will have to look at it. As for the Windows worker, it doesn't seem to connect. Have you verified that the two .pem files are in the directory that's specified in buildbot.tac? Cheers, Richard On Wed, 05 May 2021 12:11:46 +0200, Madhur Walia wrote: > > > Hi Richard, Tim, > > Awaiting further updates. Please assist. > > Thanks & Regards, > > Madhur > > From: Madhur Walia > Date: Monday, 3 May 2021 at 8:18 PM > To: Richard Levitte > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > , buildbot-admin at openssl.org > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > Hi Richard, > > We have installed git on Photon, please let us know next steps. > > Installed buildbot and VS2017 on Windows 2019 as shown below but the connection seems to be > dropping, > > Versions installed on Windows 2019, > > TextDescription automatically generated > > Win2019: Connection Failing, going in a loop, > > Graphical user interface, textDescription automatically generated > > Thanks & Regards, > > Madhur > > From: Madhur Walia > Date: Monday, 3 May 2021 at 2:37 PM > To: Richard Levitte > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > , buildbot-admin at openssl.org > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > Hi Richard, > > Thank you for the help. We had only installed buildbot-worker on Photon4 and Windows 2019. After > installing Buildbot (master) on Photon4, the worker could start. > > We are now working on installing git on Photon4 and then troubleshooting Windows 2019. I will keep > you updated. > > Regards, > > Madhur > > From: Richard Levitte > Date: Monday, 3 May 2021 at 2:33 PM > To: Madhur Walia > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > , buildbot-admin at openssl.org > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > I now noticed that the Photon 4 workers have connected, so I assume > the 'optionsForClientTLS' is a thing of the past. > > Looking at one of the builds, > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773314526%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=bTWIbaGcnmKdXIdDEd5ECwUso%2BTp46PH0kGQy9K5RxE%3D&reserved=0 > , > it looks like git isn't installed on the worker... > > Cheers, > Richard > > On Mon, 03 May 2021 10:34:57 +0200, > Richard Levitte wrote: > > > > On Mon, 26 Apr 2021 20:25:34 +0200, > > Madhur Walia wrote: > > > > > > Hi Matt, > > > > > > Thank you for the instructions. However, we are facing couple of issues while starting > buildbot-worker, > > > > > > For both platforms, we pointed Certificate/SSL settings to a custom directory in buildbot.tac > as per your recommendation. We also tried importing both certs, isrg-root-xi & lets-encrypt-r3 to > trust store of OS but no luck. > > > > > > Photon, > > > Getting error, " builtins.NameError: name 'optionsForClientTLS' is not defined" as shown > in Photon1 screenshot attached. > > > Also ran a curl command to check SSL connectivity, seems to be failing, attached > screenshot Photon2. > > > > Please check your versions of the following packages: > > > > - buildbot (should be at least version 2.6.0) > > - twisted (should be at least version 17.9.0 according to buildbot > > 2.6.0 requirements) > > > > 'optionsForClientTLS' is a method that appeared in twisted version 14.0. > > > > > Windows, > > > Getting, "Unicode error" as shown in Windows1 screenshot attached. > > > Also ran a curl command to check SSL connectivity, seems to be failing, attached > screenshot Windows2. > > > > From the error message at the end of Windows1.png, you have an invalid > > unicode character on line 30. Could it be a character with diacritics > > not encoded with UTF-8? > > > > Cheers, > > Richard > > > > > Do you have any pointers on these errors? Please let us know. > > > > > > Thanks & Regards, > > > Madhur > > > > > > ------------------------------------------------------------------ > > > > > > On 21/04/21, 4:47 PM, "Matt Caswell" wrote: > > > > > > Thanks Manoj. > > > > > > To be able to set up your worker, you must use version 2.6.0 or > > > higher. Older version do not support TLS-protected connections. > > > > > > Please see these instructions for installing the buildbot worker > > > software: > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=aIqqCC7%2BGjXcO8FYrpITEz44kSoNZIhqC0mhcEUfdxA%3D&reserved=0 > > > > > > When buildbot has been installed on the platform where the buildbot > > > worker is to be run, this is how a worker is created (for your PhotonOS > > > worker): > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > buildbot.openssl.org:9989 vmware-photonos40 nifs0Tweex_ > > > > > > And for your Windows server: > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > buildbot.openssl.org:9989 vmware-winserver2019 Efyin.Freg0 > > > > > > > > > where BASEDIR is determined by you. See further down for a few notes > > > on TLS. > > > > > > To run a buildbot worker, you do this: > > > > > > $ buildbot-worker start BASEDIR > > > > > > Apart from the software needed to run a buildbot worker, and the > > > utilities that are the normal part of the operating system, you also > > > need to ensure that the following components are available: > > > > > > - toolchains, i.e. C compiler, linker, make. If you have specified > > > toolchains in the worker request form, you need to ensure that all > > > of them are installed. > > > > > > - git > > > > > > Regarding TLS, it may be that the buildbot worker platform doesn't > > > have the appropriate certification verification roots set up. In that > > > case, you may need to apply the attached buildbot.tac patch, and store > > > the attached PEM files in a directory of your choice. Finish up by > > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with > > > the path of directory where you stored the PEM files. > > > > > > Matt > > > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > > Hi Tim & Richard, > > > > > > > > We have filled out the worker-request-form for 2 of our platforms, one unix type and > other Windows. Also, the platforms, for your convenience am listing here: > > > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 > (Platform type: Unix, x86_64, build+test, gcc) > > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge > R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > > > Please provide the credentials and instruction on setting up the buildbot worker. > > > > > > > > Thanks, > > > > Manoj > > > > > > > > > > > > -----Original Message----- > > > > From: fips-sponsors On Behalf Of Richard Levitte > > > > Sent: Monday, April 12, 2021 12:20 AM > > > > To: fips-sponsors at openssl.org > > > > Subject: [fips-sponsors] Buildbot workers > > > > > > > > Hi, > > > > > > > > We are finally ready to start getting buildbot worker requests. > > > > > > > > The way this will work is that we're asking you to answer a form with details for each > worker you want to set up for us, such as what platform, what architecture, and where relevant, > what toolchains are installed. > > > > > > > > The form is attached below, and include explanations for all the fields to fill in. > Please send it to buildbot-admin at openssl.org. > > > > > > > > In response, you will receive an email with the name and password we assign your worker > (s), and instructions how to set the worker up. > > > > > > > > > > [2 Photon1.png ] > > > > > > [3 Photon2.png ] > > > > > > [4 Windows1.png ] > > > > > > [5 Windows2.png ] > > > > > > [6 ] > > > _______________________________________________ > > > buildbot-admin mailing list > > > buildbot-admin at openssl.org > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=w%2Fb33IBbvdzc0g9S6JI6gPrjj6P5X%2BKhbVzW9Yb%2FfhU%3D&reserved=0 > > -- > > Richard Levitte levitte at openssl.org > > OpenSSL Project > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vCqwTrH2UYa0g9%2Bm906P0FnvjoJVc3o%2B89%2BhYBC2x3A%3D&reserved=0 > > _______________________________________________ > > buildbot-admin mailing list > > buildbot-admin at openssl.org > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=w%2Fb33IBbvdzc0g9S6JI6gPrjj6P5X%2BKhbVzW9Yb%2FfhU%3D&reserved=0 > -- > Richard Levitte levitte at openssl.org > OpenSSL Project > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vCqwTrH2UYa0g9%2Bm906P0FnvjoJVc3o%2B89%2BhYBC2x3A%3D&reserved=0 > > > > -- Richard Levitte levitte at openssl.org OpenSSL Project https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vCqwTrH2UYa0g9%2Bm906P0FnvjoJVc3o%2B89%2BhYBC2x3A%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 2231740 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 553234 bytes Desc: image002.png URL: From levitte at openssl.org Wed May 12 08:38:09 2021 From: levitte at openssl.org (Richard Levitte) Date: Wed, 12 May 2021 10:38:09 +0200 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org> Message-ID: <87zgx0qrda.wl-levitte@openssl.org> The winserver2019 worker did show up once! At the time, you hadn't installed the python package pywin32, but when I went in looking, it looked like you had. However, the winserver2019 worker isn't showing up now, could it be that it needs to be restarted? Do note that when we SSH to the machine, we end up with a cmd.exe prompt. However, the images you've sent us suggest that you run from a Mingw64 prompt, and I do not know how to get there from cmd.exe, so it's will need instructions to do restarts for you. Cheers, Richard Right now, it looks like you need to get the winserver2019 worker started. I hope it's problem free at this point. On Fri, 07 May 2021 09:51:22 +0200, Madhur Walia wrote: > > Hi Richard, > > We are able to connect to Buildbot Master from Windows 2019 as well now. To our surprise, > Buildbot-worker/ Python was searching for Certificate directory in base directory. > > After pointing ssl-root-dir to a directory hosted in base directory, it was able to connect. > > Please confirm the connection. > > Also, What are the next steps for Photon 4 and Windows 2019 now? > > Thank you for your inputs. > > Regards, > > Madhur > > From: Madhur Walia > Date: Thursday, 6 May 2021 at 10:04 PM > To: Richard Levitte , Sunil Kumar Yadav > Cc: Richard Levitte , Manoj Maskara , Tim Hudson > , buildbot-admin at openssl.org > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > Thank you Richard. So, Photon 4.0 seems to be okay for now and next update would be from your > development team. > > We captured a wireshark trace keeping default buildbot.tac and could see ?Unknown CA? error. We > then pointed the trustroots/ ssl-root-dir to a custom path (to pem files), and encountered another > error which points to failure in trusting CA certificate filepath. > > TextDescription automatically generated > > We tried pointing trustroots directory to absolute certificate directory path but no luck. > > Other debugging steps involves, > > ? Running ?openssl s_client -state -debug -connect buildbot.openssl.org:9989? which gives > Verification: OK if we point the -CAfile to Hashed CA pem file names/ location. > > ? Executing, a python code to verify against CA file path, which shows a successful CA > trust in Wireshark, > > import os > > import requests > > r=requests.get('https://buildbot.openssl.org:9989',verify='C:/Certificates/a.pem') > > Graphical user interface, text, applicationDescription automatically generat > > This either seems to be a platform, (Windows) specific issue or something related to twisted OR > something very miniscule that @Sunil Kumar Yadav and I are unable to catch. > > I can schedule a call to discuss this in more depth keeping in mind we are almost near to > completion of 3~4 weeks window. > > Please let me know, Sunil and I are based out of India, IST time zone. We can talk during IST > evening, Your Morning. > > Thanks & Regards, > > Madhur > > From: Richard Levitte > Date: Wednesday, 5 May 2021 at 8:37 PM > To: Madhur Walia > Cc: Richard Levitte , Manoj Maskara , Tim Hudson > , Sunil Kumar Yadav , buildbot-admin at openssl.org > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > As far as I can tell, The Photon 4 worker is good. The fact that > "make test" currently fails isn't a problem with the worker as far as > I can see... our development team will have to look at it. > > As for the Windows worker, it doesn't seem to connect. Have you > verified that the two .pem files are in the directory that's specified > in buildbot.tac? > > Cheers, > Richard > > On Wed, 05 May 2021 12:11:46 +0200, > Madhur Walia wrote: > > > > > > Hi Richard, Tim, > > > > Awaiting further updates. Please assist. > > > > Thanks & Regards, > > > > Madhur > > > > From: Madhur Walia > > Date: Monday, 3 May 2021 at 8:18 PM > > To: Richard Levitte > > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > > , buildbot-admin at openssl.org > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > Hi Richard, > > > > We have installed git on Photon, please let us know next steps. > > > > Installed buildbot and VS2017 on Windows 2019 as shown below but the connection seems to be > > dropping, > > > > Versions installed on Windows 2019, > > > > TextDescription automatically generated > > > > Win2019: Connection Failing, going in a loop, > > > > Graphical user interface, textDescription automatically generated > > > > Thanks & Regards, > > > > Madhur > > > > From: Madhur Walia > > Date: Monday, 3 May 2021 at 2:37 PM > > To: Richard Levitte > > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > > , buildbot-admin at openssl.org > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > Hi Richard, > > > > Thank you for the help. We had only installed buildbot-worker on Photon4 and Windows 2019. After > > installing Buildbot (master) on Photon4, the worker could start. > > > > We are now working on installing git on Photon4 and then troubleshooting Windows 2019. I will > keep > > you updated. > > > > Regards, > > > > Madhur > > > > From: Richard Levitte > > Date: Monday, 3 May 2021 at 2:33 PM > > To: Madhur Walia > > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > > , buildbot-admin at openssl.org > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > I now noticed that the Photon 4 workers have connected, so I assume > > the 'optionsForClientTLS' is a thing of the past. > > > > Looking at one of the builds, > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773314526%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=bTWIbaGcnmKdXIdDEd5ECwUso%2BTp46PH0kGQy9K5RxE%3D&reserved=0 > > , > > it looks like git isn't installed on the worker... > > > > Cheers, > > Richard > > > > On Mon, 03 May 2021 10:34:57 +0200, > > Richard Levitte wrote: > > > > > > On Mon, 26 Apr 2021 20:25:34 +0200, > > > Madhur Walia wrote: > > > > > > > > Hi Matt, > > > > > > > > Thank you for the instructions. However, we are facing couple of issues while starting > > buildbot-worker, > > > > > > > > For both platforms, we pointed Certificate/SSL settings to a custom directory in > buildbot.tac > > as per your recommendation. We also tried importing both certs, isrg-root-xi & lets-encrypt-r3 > to > > trust store of OS but no luck. > > > > > > > > Photon, > > > > Getting error, " builtins.NameError: name 'optionsForClientTLS' is not defined" as > shown > > in Photon1 screenshot attached. > > > > Also ran a curl command to check SSL connectivity, seems to be failing, attached > > screenshot Photon2. > > > > > > Please check your versions of the following packages: > > > > > > - buildbot (should be at least version 2.6.0) > > > - twisted (should be at least version 17.9.0 according to buildbot > > > 2.6.0 requirements) > > > > > > 'optionsForClientTLS' is a method that appeared in twisted version 14.0. > > > > > > > Windows, > > > > Getting, "Unicode error" as shown in Windows1 screenshot attached. > > > > Also ran a curl command to check SSL connectivity, seems to be failing, attached > > screenshot Windows2. > > > > > > From the error message at the end of Windows1.png, you have an invalid > > > unicode character on line 30. Could it be a character with diacritics > > > not encoded with UTF-8? > > > > > > Cheers, > > > Richard > > > > > > > Do you have any pointers on these errors? Please let us know. > > > > > > > > Thanks & Regards, > > > > Madhur > > > > > > > > ------------------------------------------------------------------ > > > > > > > > On 21/04/21, 4:47 PM, "Matt Caswell" wrote: > > > > > > > > Thanks Manoj. > > > > > > > > To be able to set up your worker, you must use version 2.6.0 or > > > > higher. Older version do not support TLS-protected connections. > > > > > > > > Please see these instructions for installing the buildbot worker > > > > software: > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=aIqqCC7%2BGjXcO8FYrpITEz44kSoNZIhqC0mhcEUfdxA%3D&reserved=0 > > > > > > > > When buildbot has been installed on the platform where the buildbot > > > > worker is to be run, this is how a worker is created (for your PhotonOS > > > > worker): > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > buildbot.openssl.org:9989 vmware-photonos40 nifs0Tweex_ > > > > > > > > And for your Windows server: > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > buildbot.openssl.org:9989 vmware-winserver2019 Efyin.Freg0 > > > > > > > > > > > > where BASEDIR is determined by you. See further down for a few notes > > > > on TLS. > > > > > > > > To run a buildbot worker, you do this: > > > > > > > > $ buildbot-worker start BASEDIR > > > > > > > > Apart from the software needed to run a buildbot worker, and the > > > > utilities that are the normal part of the operating system, you also > > > > need to ensure that the following components are available: > > > > > > > > - toolchains, i.e. C compiler, linker, make. If you have specified > > > > toolchains in the worker request form, you need to ensure that all > > > > of them are installed. > > > > > > > > - git > > > > > > > > Regarding TLS, it may be that the buildbot worker platform doesn't > > > > have the appropriate certification verification roots set up. In that > > > > case, you may need to apply the attached buildbot.tac patch, and store > > > > the attached PEM files in a directory of your choice. Finish up by > > > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with > > > > the path of directory where you stored the PEM files. > > > > > > > > Matt > > > > > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > > > Hi Tim & Richard, > > > > > > > > > > We have filled out the worker-request-form for 2 of our platforms, one unix type and > > other Windows. Also, the platforms, for your convenience am listing here: > > > > > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 > > (Platform type: Unix, x86_64, build+test, gcc) > > > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge > > R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > > > > > Please provide the credentials and instruction on setting up the buildbot worker. > > > > > > > > > > Thanks, > > > > > Manoj > > > > > > > > > > > > > > > -----Original Message----- > > > > > From: fips-sponsors On Behalf Of Richard Levitte > > > > > Sent: Monday, April 12, 2021 12:20 AM > > > > > To: fips-sponsors at openssl.org > > > > > Subject: [fips-sponsors] Buildbot workers > > > > > > > > > > Hi, > > > > > > > > > > We are finally ready to start getting buildbot worker requests. > > > > > > > > > > The way this will work is that we're asking you to answer a form with details for each > > worker you want to set up for us, such as what platform, what architecture, and where relevant, > > what toolchains are installed. > > > > > > > > > > The form is attached below, and include explanations for all the fields to fill in. > > Please send it to buildbot-admin at openssl.org. > > > > > > > > > > In response, you will receive an email with the name and password we assign your > worker > > (s), and instructions how to set the worker up. > > > > > > > > > > > > > [2 Photon1.png ] > > > > > > > > [3 Photon2.png ] > > > > > > > > [4 Windows1.png ] > > > > > > > > [5 Windows2.png ] > > > > > > > > [6 ] > > > > _______________________________________________ > > > > buildbot-admin mailing list > > > > buildbot-admin at openssl.org > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=w%2Fb33IBbvdzc0g9S6JI6gPrjj6P5X%2BKhbVzW9Yb%2FfhU%3D&reserved=0 > > > -- > > > Richard Levitte levitte at openssl.org > > > OpenSSL Project > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vCqwTrH2UYa0g9%2Bm906P0FnvjoJVc3o%2B89%2BhYBC2x3A%3D&reserved=0 > > > _______________________________________________ > > > buildbot-admin mailing list > > > buildbot-admin at openssl.org > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=w%2Fb33IBbvdzc0g9S6JI6gPrjj6P5X%2BKhbVzW9Yb%2FfhU%3D&reserved=0 > > -- > > Richard Levitte levitte at openssl.org > > OpenSSL Project > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vCqwTrH2UYa0g9%2Bm906P0FnvjoJVc3o%2B89%2BhYBC2x3A%3D&reserved=0 > > > > > > > > > -- > Richard Levitte levitte at openssl.org > OpenSSL Project > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C7e3457eafdb547e1d0ae08d90fd78e2c%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637558240773324484%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vCqwTrH2UYa0g9%2Bm906P0FnvjoJVc3o%2B89%2BhYBC2x3A%3D&reserved=0 -- Richard Levitte levitte at openssl.org OpenSSL Project http://www.openssl.org/~levitte/ From waliam at vmware.com Wed May 12 11:41:22 2021 From: waliam at vmware.com (Madhur Walia) Date: Wed, 12 May 2021 11:41:22 +0000 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: <87zgx0qrda.wl-levitte@openssl.org> References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org>,<87zgx0qrda.wl-levitte@openssl.org> Message-ID: Hi Richard, We restarted buildbot-worker in Windows 2019 and it seems to be connecting now. We could see files under Base Directory as shown below. We could see couple of errors related to absence of Perl and cmake in build Master Dashboard. So, we have installed them as well. [Table Description automatically generated] Yes, when you SSH, you will be connected to cmd.exe. One of the screenshots we shared had PowerShell utility but you should be able to run the commands through cmd.exe as well. We are using the same. Please let us know if you face any issues. Thanks & Regards, Madhur From: Richard Levitte Date: Wednesday, 12 May 2021 at 2:08 PM To: Madhur Walia Cc: Richard Levitte , Sunil Kumar Yadav , Manoj Maskara , Tim Hudson , buildbot-admin at openssl.org , Bishakha Banerjee Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers The winserver2019 worker did show up once! At the time, you hadn't installed the python package pywin32, but when I went in looking, it looked like you had. However, the winserver2019 worker isn't showing up now, could it be that it needs to be restarted? Do note that when we SSH to the machine, we end up with a cmd.exe prompt. However, the images you've sent us suggest that you run from a Mingw64 prompt, and I do not know how to get there from cmd.exe, so it's will need instructions to do restarts for you. Cheers, Richard Right now, it looks like you need to get the winserver2019 worker started. I hope it's problem free at this point. On Fri, 07 May 2021 09:51:22 +0200, Madhur Walia wrote: > > Hi Richard, > > We are able to connect to Buildbot Master from Windows 2019 as well now. To our surprise, > Buildbot-worker/ Python was searching for Certificate directory in base directory. > > After pointing ssl-root-dir to a directory hosted in base directory, it was able to connect. > > Please confirm the connection. > > Also, What are the next steps for Photon 4 and Windows 2019 now? > > Thank you for your inputs. > > Regards, > > Madhur > > From: Madhur Walia > Date: Thursday, 6 May 2021 at 10:04 PM > To: Richard Levitte , Sunil Kumar Yadav > Cc: Richard Levitte , Manoj Maskara , Tim Hudson > , buildbot-admin at openssl.org > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > Thank you Richard. So, Photon 4.0 seems to be okay for now and next update would be from your > development team. > > We captured a wireshark trace keeping default buildbot.tac and could see ?Unknown CA? error. We > then pointed the trustroots/ ssl-root-dir to a custom path (to pem files), and encountered another > error which points to failure in trusting CA certificate filepath. > > TextDescription automatically generated > > We tried pointing trustroots directory to absolute certificate directory path but no luck. > > Other debugging steps involves, > > ? Running ?openssl s_client -state -debug -connect buildbot.openssl.org:9989? which gives > Verification: OK if we point the -CAfile to Hashed CA pem file names/ location. > > ? Executing, a python code to verify against CA file path, which shows a successful CA > trust in Wireshark, > > import os > > import requests > > r=requests.get('https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=l2%2FDPVWSKTnB1%2B18yyDzAOEZbjjFCIP%2BfdFdEwcX9wo%3D&reserved=0',verify='C:/Certificates/a.pem') > > Graphical user interface, text, applicationDescription automatically generat > > This either seems to be a platform, (Windows) specific issue or something related to twisted OR > something very miniscule that @Sunil Kumar Yadav and I are unable to catch. > > I can schedule a call to discuss this in more depth keeping in mind we are almost near to > completion of 3~4 weeks window. > > Please let me know, Sunil and I are based out of India, IST time zone. We can talk during IST > evening, Your Morning. > > Thanks & Regards, > > Madhur > > From: Richard Levitte > Date: Wednesday, 5 May 2021 at 8:37 PM > To: Madhur Walia > Cc: Richard Levitte , Manoj Maskara , Tim Hudson > , Sunil Kumar Yadav , buildbot-admin at openssl.org > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > As far as I can tell, The Photon 4 worker is good. The fact that > "make test" currently fails isn't a problem with the worker as far as > I can see... our development team will have to look at it. > > As for the Windows worker, it doesn't seem to connect. Have you > verified that the two .pem files are in the directory that's specified > in buildbot.tac? > > Cheers, > Richard > > On Wed, 05 May 2021 12:11:46 +0200, > Madhur Walia wrote: > > > > > > Hi Richard, Tim, > > > > Awaiting further updates. Please assist. > > > > Thanks & Regards, > > > > Madhur > > > > From: Madhur Walia > > Date: Monday, 3 May 2021 at 8:18 PM > > To: Richard Levitte > > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > > , buildbot-admin at openssl.org > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > Hi Richard, > > > > We have installed git on Photon, please let us know next steps. > > > > Installed buildbot and VS2017 on Windows 2019 as shown below but the connection seems to be > > dropping, > > > > Versions installed on Windows 2019, > > > > TextDescription automatically generated > > > > Win2019: Connection Failing, going in a loop, > > > > Graphical user interface, textDescription automatically generated > > > > Thanks & Regards, > > > > Madhur > > > > From: Madhur Walia > > Date: Monday, 3 May 2021 at 2:37 PM > > To: Richard Levitte > > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > > , buildbot-admin at openssl.org > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > Hi Richard, > > > > Thank you for the help. We had only installed buildbot-worker on Photon4 and Windows 2019. After > > installing Buildbot (master) on Photon4, the worker could start. > > > > We are now working on installing git on Photon4 and then troubleshooting Windows 2019. I will > keep > > you updated. > > > > Regards, > > > > Madhur > > > > From: Richard Levitte > > Date: Monday, 3 May 2021 at 2:33 PM > > To: Madhur Walia > > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > > , buildbot-admin at openssl.org > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > I now noticed that the Photon 4 workers have connected, so I assume > > the 'optionsForClientTLS' is a thing of the past. > > > > Looking at one of the builds, > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TI%2BLbZSdaiW9wzttTf6W6Ee13y9nqGkYEppKBl2r4js%3D&reserved=0 > > , > > it looks like git isn't installed on the worker... > > > > Cheers, > > Richard > > > > On Mon, 03 May 2021 10:34:57 +0200, > > Richard Levitte wrote: > > > > > > On Mon, 26 Apr 2021 20:25:34 +0200, > > > Madhur Walia wrote: > > > > > > > > Hi Matt, > > > > > > > > Thank you for the instructions. However, we are facing couple of issues while starting > > buildbot-worker, > > > > > > > > For both platforms, we pointed Certificate/SSL settings to a custom directory in > buildbot.tac > > as per your recommendation. We also tried importing both certs, isrg-root-xi & lets-encrypt-r3 > to > > trust store of OS but no luck. > > > > > > > > Photon, > > > > Getting error, " builtins.NameError: name 'optionsForClientTLS' is not defined" as > shown > > in Photon1 screenshot attached. > > > > Also ran a curl command to check SSL connectivity, seems to be failing, attached > > screenshot Photon2. > > > > > > Please check your versions of the following packages: > > > > > > - buildbot (should be at least version 2.6.0) > > > - twisted (should be at least version 17.9.0 according to buildbot > > > 2.6.0 requirements) > > > > > > 'optionsForClientTLS' is a method that appeared in twisted version 14.0. > > > > > > > Windows, > > > > Getting, "Unicode error" as shown in Windows1 screenshot attached. > > > > Also ran a curl command to check SSL connectivity, seems to be failing, attached > > screenshot Windows2. > > > > > > From the error message at the end of Windows1.png, you have an invalid > > > unicode character on line 30. Could it be a character with diacritics > > > not encoded with UTF-8? > > > > > > Cheers, > > > Richard > > > > > > > Do you have any pointers on these errors? Please let us know. > > > > > > > > Thanks & Regards, > > > > Madhur > > > > > > > > ------------------------------------------------------------------ > > > > > > > > On 21/04/21, 4:47 PM, "Matt Caswell" wrote: > > > > > > > > Thanks Manoj. > > > > > > > > To be able to set up your worker, you must use version 2.6.0 or > > > > higher. Older version do not support TLS-protected connections. > > > > > > > > Please see these instructions for installing the buildbot worker > > > > software: > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zYGoKToLms7AP%2Fefcpd9EdleLdDrnX3lotBLVxPjY3M%3D&reserved=0 > > > > > > > > When buildbot has been installed on the platform where the buildbot > > > > worker is to be run, this is how a worker is created (for your PhotonOS > > > > worker): > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > buildbot.openssl.org:9989 vmware-photonos40 nifs0Tweex_ > > > > > > > > And for your Windows server: > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > buildbot.openssl.org:9989 vmware-winserver2019 Efyin.Freg0 > > > > > > > > > > > > where BASEDIR is determined by you. See further down for a few notes > > > > on TLS. > > > > > > > > To run a buildbot worker, you do this: > > > > > > > > $ buildbot-worker start BASEDIR > > > > > > > > Apart from the software needed to run a buildbot worker, and the > > > > utilities that are the normal part of the operating system, you also > > > > need to ensure that the following components are available: > > > > > > > > - toolchains, i.e. C compiler, linker, make. If you have specified > > > > toolchains in the worker request form, you need to ensure that all > > > > of them are installed. > > > > > > > > - git > > > > > > > > Regarding TLS, it may be that the buildbot worker platform doesn't > > > > have the appropriate certification verification roots set up. In that > > > > case, you may need to apply the attached buildbot.tac patch, and store > > > > the attached PEM files in a directory of your choice. Finish up by > > > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with > > > > the path of directory where you stored the PEM files. > > > > > > > > Matt > > > > > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > > > Hi Tim & Richard, > > > > > > > > > > We have filled out the worker-request-form for 2 of our platforms, one unix type and > > other Windows. Also, the platforms, for your convenience am listing here: > > > > > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 > > (Platform type: Unix, x86_64, build+test, gcc) > > > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge > > R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > > > > > Please provide the credentials and instruction on setting up the buildbot worker. > > > > > > > > > > Thanks, > > > > > Manoj > > > > > > > > > > > > > > > -----Original Message----- > > > > > From: fips-sponsors On Behalf Of Richard Levitte > > > > > Sent: Monday, April 12, 2021 12:20 AM > > > > > To: fips-sponsors at openssl.org > > > > > Subject: [fips-sponsors] Buildbot workers > > > > > > > > > > Hi, > > > > > > > > > > We are finally ready to start getting buildbot worker requests. > > > > > > > > > > The way this will work is that we're asking you to answer a form with details for each > > worker you want to set up for us, such as what platform, what architecture, and where relevant, > > what toolchains are installed. > > > > > > > > > > The form is attached below, and include explanations for all the fields to fill in. > > Please send it to buildbot-admin at openssl.org. > > > > > > > > > > In response, you will receive an email with the name and password we assign your > worker > > (s), and instructions how to set the worker up. > > > > > > > > > > > > > [2 Photon1.png ] > > > > > > > > [3 Photon2.png ] > > > > > > > > [4 Windows1.png ] > > > > > > > > [5 Windows2.png ] > > > > > > > > [6 ] > > > > _______________________________________________ > > > > buildbot-admin mailing list > > > > buildbot-admin at openssl.org > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6L9gkXe7BuoEq5B0C61BQqp%2BIbKhpQkN3SIIUlC56Vc%3D&reserved=0 > > > -- > > > Richard Levitte levitte at openssl.org > > > OpenSSL Project > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=2tBYFB4HeNnmlOlbCtY3foxltY%2FjAkxw08luxL5rWr0%3D&reserved=0 > > > _______________________________________________ > > > buildbot-admin mailing list > > > buildbot-admin at openssl.org > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Xg1zAuJT5GFZ2v29FvL9ouQrcfnpqoA1Zb8H69sQG%2BM%3D&reserved=0 > > -- > > Richard Levitte levitte at openssl.org > > OpenSSL Project > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > > > > > > > > > -- > Richard Levitte levitte at openssl.org > OpenSSL Project > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 -- Richard Levitte levitte at openssl.org OpenSSL Project https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 873902 bytes Desc: image001.png URL: From tjh at openssl.org Thu May 13 01:41:41 2021 From: tjh at openssl.org (Tim Hudson) Date: Thu, 13 May 2021 11:41:41 +1000 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org> <87zgx0qrda.wl-levitte@openssl.org> Message-ID: You can see the current issue is that nmake isn't in the path. See https://fips.buildbot.openssl.org/#/builders/31/builds/3 You need to have that setup for the buildbot worker to actually work. i.e. logged in as the user in windows running cmd you need to have it so that "nmake" is accessible and operating correctly. Have you completed that step? There are multiple ways to set that up - and the approach I took was to run the vcvars64.bat setup script from Microsoft and then dump the environment and include setting a matching environment in buildbot.tac. You can of course copy all the environment variables into the users environment. eng at DESKTOP-75K0EME C:\buildbot\tjh-win10-1-tls>type make-env.py *import osfor k, v in os.environ.items(): print('os.environ[\''+str(k)+'\']=\''+str(v).replace('\\','\\\\')+'\'')* I run that script (in a window that has had vcvars64.bat run) and changed into the buildbot worker directory (where buildbot.tac exists) python make-env.py > env.py And I modified buildbot.tac to have: *def include(filename): if os.path.exists(filename): execfile(filename)include('env.py')* That is how I setup a windows based worker configuration - the one you see at https://fips.buildbot.openssl.org/#/workers/6 Tim. On Wed, May 12, 2021 at 9:41 PM Madhur Walia wrote: > Hi Richard, > > > > We restarted buildbot-worker in Windows 2019 and it seems to be connecting > now. We could see files under Base Directory as shown below. > > > > We could see couple of errors related to absence of Perl and cmake in > build Master Dashboard. So, we have installed them as well. > > > > [image: Table Description automatically generated] > > > > Yes, when you SSH, you will be connected to cmd.exe. One of the > screenshots we shared had PowerShell utility but you should be able to run > the commands through cmd.exe as well. We are using the same. > > > > Please let us know if you face any issues. > > > > Thanks & Regards, > > Madhur > > > > *From: *Richard Levitte > *Date: *Wednesday, 12 May 2021 at 2:08 PM > *To: *Madhur Walia > *Cc: *Richard Levitte , Sunil Kumar Yadav < > ysunilkumar at vmware.com>, Manoj Maskara , Tim Hudson < > tjh at openssl.org>, buildbot-admin at openssl.org , > Bishakha Banerjee > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > The winserver2019 worker did show up once! At the time, you hadn't > installed the python package pywin32, but when I went in looking, it > looked like you had. However, the winserver2019 worker isn't showing > up now, could it be that it needs to be restarted? > > Do note that when we SSH to the machine, we end up with a cmd.exe > prompt. However, the images you've sent us suggest that you run from > a Mingw64 prompt, and I do not know how to get there from cmd.exe, so > it's will need instructions to do restarts for you. > > Cheers, > Richard > > Right now, it looks like you need to get the winserver2019 worker > started. I hope it's problem free at this point. > > On Fri, 07 May 2021 09:51:22 +0200, > Madhur Walia wrote: > > > > Hi Richard, > > > > We are able to connect to Buildbot Master from Windows 2019 as well now. > To our surprise, > > Buildbot-worker/ Python was searching for Certificate directory in base > directory. > > > > After pointing ssl-root-dir to a directory hosted in base directory, it > was able to connect. > > > > Please confirm the connection. > > > > Also, What are the next steps for Photon 4 and Windows 2019 now? > > > > Thank you for your inputs. > > > > Regards, > > > > Madhur > > > > From: Madhur Walia > > Date: Thursday, 6 May 2021 at 10:04 PM > > To: Richard Levitte , Sunil Kumar Yadav < > ysunilkumar at vmware.com> > > Cc: Richard Levitte , Manoj Maskara < > mmaskara at vmware.com>, Tim Hudson > > , buildbot-admin at openssl.org < > buildbot-admin at openssl.org> > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > Thank you Richard. So, Photon 4.0 seems to be okay for now and next > update would be from your > > development team. > > > > We captured a wireshark trace keeping default buildbot.tac and could see > ?Unknown CA? error. We > > then pointed the trustroots/ ssl-root-dir to a custom path (to pem > files), and encountered another > > error which points to failure in trusting CA certificate filepath. > > > > TextDescription automatically > generated > > > > We tried pointing trustroots directory to absolute certificate directory > path but no luck. > > > > Other debugging steps involves, > > > > ? Running ?openssl s_client -state -debug -connect > buildbot.openssl.org:9989? which gives > > Verification: OK if we point the -CAfile to Hashed CA pem file names/ > location. > > > > ? Executing, a python code to verify against CA file path, which > shows a successful CA > > trust in Wireshark, > > > > import os > > > > import requests > > > > r=requests.get(' > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=l2%2FDPVWSKTnB1%2B18yyDzAOEZbjjFCIP%2BfdFdEwcX9wo%3D&reserved=0',verify='C:/Certificates/a.pem > ') > > > > Graphical user interface, text, applicationDescription automatically > generat > > > > This either seems to be a platform, (Windows) specific issue or > something related to twisted OR > > something very miniscule that @Sunil Kumar Yadav and I are unable to > catch. > > > > I can schedule a call to discuss this in more depth keeping in mind we > are almost near to > > completion of 3~4 weeks window. > > > > Please let me know, Sunil and I are based out of India, IST time zone. > We can talk during IST > > evening, Your Morning. > > > > Thanks & Regards, > > > > Madhur > > > > From: Richard Levitte > > Date: Wednesday, 5 May 2021 at 8:37 PM > > To: Madhur Walia > > Cc: Richard Levitte , Manoj Maskara < > mmaskara at vmware.com>, Tim Hudson > > , Sunil Kumar Yadav , > buildbot-admin at openssl.org > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > As far as I can tell, The Photon 4 worker is good. The fact that > > "make test" currently fails isn't a problem with the worker as far as > > I can see... our development team will have to look at it. > > > > As for the Windows worker, it doesn't seem to connect. Have you > > verified that the two .pem files are in the directory that's specified > > in buildbot.tac? > > > > Cheers, > > Richard > > > > On Wed, 05 May 2021 12:11:46 +0200, > > Madhur Walia wrote: > > > > > > > > > Hi Richard, Tim, > > > > > > Awaiting further updates. Please assist. > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > From: Madhur Walia > > > Date: Monday, 3 May 2021 at 8:18 PM > > > To: Richard Levitte > > > Cc: Manoj Maskara , Tim Hudson , > Sunil Kumar Yadav > > > , buildbot-admin at openssl.org < > buildbot-admin at openssl.org> > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > Hi Richard, > > > > > > We have installed git on Photon, please let us know next steps. > > > > > > Installed buildbot and VS2017 on Windows 2019 as shown below but the > connection seems to be > > > dropping, > > > > > > Versions installed on Windows 2019, > > > > > > TextDescription automatically generated > > > > > > Win2019: Connection Failing, going in a loop, > > > > > > Graphical user interface, textDescription automatically generated > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > From: Madhur Walia > > > Date: Monday, 3 May 2021 at 2:37 PM > > > To: Richard Levitte > > > Cc: Manoj Maskara , Tim Hudson , > Sunil Kumar Yadav > > > , buildbot-admin at openssl.org < > buildbot-admin at openssl.org> > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > Hi Richard, > > > > > > Thank you for the help. We had only installed buildbot-worker on > Photon4 and Windows 2019. After > > > installing Buildbot (master) on Photon4, the worker could start. > > > > > > We are now working on installing git on Photon4 and then > troubleshooting Windows 2019. I will > > keep > > > you updated. > > > > > > Regards, > > > > > > Madhur > > > > > > From: Richard Levitte > > > Date: Monday, 3 May 2021 at 2:33 PM > > > To: Madhur Walia > > > Cc: Manoj Maskara , Tim Hudson , > Sunil Kumar Yadav > > > , buildbot-admin at openssl.org < > buildbot-admin at openssl.org> > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > I now noticed that the Photon 4 workers have connected, so I assume > > > the 'optionsForClientTLS' is a thing of the past. > > > > > > Looking at one of the builds, > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TI%2BLbZSdaiW9wzttTf6W6Ee13y9nqGkYEppKBl2r4js%3D&reserved=0 > > > , > > > it looks like git isn't installed on the worker... > > > > > > Cheers, > > > Richard > > > > > > On Mon, 03 May 2021 10:34:57 +0200, > > > Richard Levitte wrote: > > > > > > > > On Mon, 26 Apr 2021 20:25:34 +0200, > > > > Madhur Walia wrote: > > > > > > > > > > Hi Matt, > > > > > > > > > > Thank you for the instructions. However, we are facing couple of > issues while starting > > > buildbot-worker, > > > > > > > > > > For both platforms, we pointed Certificate/SSL settings to a > custom directory in > > buildbot.tac > > > as per your recommendation. We also tried importing both certs, > isrg-root-xi & lets-encrypt-r3 > > to > > > trust store of OS but no luck. > > > > > > > > > > Photon, > > > > > Getting error, " builtins.NameError: name > 'optionsForClientTLS' is not defined" as > > shown > > > in Photon1 screenshot attached. > > > > > Also ran a curl command to check SSL connectivity, seems to > be failing, attached > > > screenshot Photon2. > > > > > > > > Please check your versions of the following packages: > > > > > > > > - buildbot (should be at least version 2.6.0) > > > > - twisted (should be at least version 17.9.0 according to buildbot > > > > 2.6.0 requirements) > > > > > > > > 'optionsForClientTLS' is a method that appeared in twisted version > 14.0. > > > > > > > > > Windows, > > > > > Getting, "Unicode error" as shown in Windows1 screenshot > attached. > > > > > Also ran a curl command to check SSL connectivity, seems to > be failing, attached > > > screenshot Windows2. > > > > > > > > From the error message at the end of Windows1.png, you have an > invalid > > > > unicode character on line 30. Could it be a character with > diacritics > > > > not encoded with UTF-8? > > > > > > > > Cheers, > > > > Richard > > > > > > > > > Do you have any pointers on these errors? Please let us know. > > > > > > > > > > Thanks & Regards, > > > > > Madhur > > > > > > > > > > ------------------------------------------------------------------ > > > > > > > > > > On 21/04/21, 4:47 PM, "Matt Caswell" wrote: > > > > > > > > > > Thanks Manoj. > > > > > > > > > > To be able to set up your worker, you must use version 2.6.0 or > > > > > higher. Older version do not support TLS-protected > connections. > > > > > > > > > > Please see these instructions for installing the buildbot > worker > > > > > software: > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zYGoKToLms7AP%2Fefcpd9EdleLdDrnX3lotBLVxPjY3M%3D&reserved=0 > > > > > > > > > > When buildbot has been installed on the platform where the > buildbot > > > > > worker is to be run, this is how a worker is created (for your > PhotonOS > > > > > worker): > > > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > buildbot.openssl.org:9989 vmware-photonos40 > nifs0Tweex_ > > > > > > > > > > And for your Windows server: > > > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > buildbot.openssl.org:9989 vmware-winserver2019 > Efyin.Freg0 > > > > > > > > > > > > > > > where BASEDIR is determined by you. See further down for a > few notes > > > > > on TLS. > > > > > > > > > > To run a buildbot worker, you do this: > > > > > > > > > > $ buildbot-worker start BASEDIR > > > > > > > > > > Apart from the software needed to run a buildbot worker, and > the > > > > > utilities that are the normal part of the operating system, > you also > > > > > need to ensure that the following components are available: > > > > > > > > > > - toolchains, i.e. C compiler, linker, make. If you have > specified > > > > > toolchains in the worker request form, you need to ensure > that all > > > > > of them are installed. > > > > > > > > > > - git > > > > > > > > > > Regarding TLS, it may be that the buildbot worker platform > doesn't > > > > > have the appropriate certification verification roots set up. > In that > > > > > case, you may need to apply the attached buildbot.tac patch, > and store > > > > > the attached PEM files in a directory of your choice. Finish > up by > > > > > find the string '/PATH/TO/ssl-roots-dir' and replace its > contents with > > > > > the path of directory where you stored the PEM files. > > > > > > > > > > Matt > > > > > > > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > > > > Hi Tim & Richard, > > > > > > > > > > > > We have filled out the worker-request-form for 2 of our > platforms, one unix type and > > > other Windows. Also, the platforms, for your convenience am listing > here: > > > > > > > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon Gold > 6230R on Dell PowerEdge R740 > > > (Platform type: Unix, x86_64, build+test, gcc) > > > > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel Xeon > Gold 6230R on Dell PowerEdge > > > R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > > > > > > > Please provide the credentials and instruction on setting up > the buildbot worker. > > > > > > > > > > > > Thanks, > > > > > > Manoj > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: fips-sponsors On > Behalf Of Richard Levitte > > > > > > Sent: Monday, April 12, 2021 12:20 AM > > > > > > To: fips-sponsors at openssl.org > > > > > > Subject: [fips-sponsors] Buildbot workers > > > > > > > > > > > > Hi, > > > > > > > > > > > > We are finally ready to start getting buildbot worker > requests. > > > > > > > > > > > > The way this will work is that we're asking you to answer a > form with details for each > > > worker you want to set up for us, such as what platform, what > architecture, and where relevant, > > > what toolchains are installed. > > > > > > > > > > > > The form is attached below, and include explanations for all > the fields to fill in. > > > Please send it to buildbot-admin at openssl.org. > > > > > > > > > > > > In response, you will receive an email with the name and > password we assign your > > worker > > > (s), and instructions how to set the worker up. > > > > > > > > > > > > > > > > [2 Photon1.png ] > > > > > > > > > > [3 Photon2.png ] > > > > > > > > > > [4 Windows1.png ] > > > > > > > > > > [5 Windows2.png ] > > > > > > > > > > [6 ] > > > > > _______________________________________________ > > > > > buildbot-admin mailing list > > > > > buildbot-admin at openssl.org > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6L9gkXe7BuoEq5B0C61BQqp%2BIbKhpQkN3SIIUlC56Vc%3D&reserved=0 > > > > -- > > > > Richard Levitte levitte at openssl.org > > > > OpenSSL Project > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=2tBYFB4HeNnmlOlbCtY3foxltY%2FjAkxw08luxL5rWr0%3D&reserved=0 > > > > _______________________________________________ > > > > buildbot-admin mailing list > > > > buildbot-admin at openssl.org > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Xg1zAuJT5GFZ2v29FvL9ouQrcfnpqoA1Zb8H69sQG%2BM%3D&reserved=0 > > > -- > > > Richard Levitte levitte at openssl.org > > > OpenSSL Project > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > > > > > > > > > > > > > > -- > > Richard Levitte levitte at openssl.org > > OpenSSL Project > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > -- > Richard Levitte levitte at openssl.org > OpenSSL Project > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 873902 bytes Desc: not available URL: From levitte at openssl.org Thu May 13 05:54:08 2021 From: levitte at openssl.org (Richard Levitte) Date: Thu, 13 May 2021 07:54:08 +0200 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org> <87zgx0qrda.wl-levitte@openssl.org> Message-ID: <87wns3qiv3.wl-levitte@openssl.org> [ NOTE: Tim and buildbot-admin only ] I was actually surprised by this, as I've had no issues running Configure without any extra arguments on Windows, without having CL in the path. ... it turns out, though, that my Strawberry installation, which I set up a looooong time ago, includes gcc.exe, so Configure finds that and is all happy that it found *a* compiler, even though it's not the one actually used. Oy... So ok, lesson learned, we need to wrap the 'perl Configure' run with the wrapper script I use for all the nmake runs. AND OpenSSL::config needs to learn about CL. Cheers, Richard ( today is a holyday, so I won't do much more than this for the day ) On Thu, 13 May 2021 03:41:41 +0200, Tim Hudson wrote: > > You can see the current issue is that nmake isn't in the path. > See?https://fips.buildbot.openssl.org/#/builders/31/builds/3 > > You need to have that setup for the buildbot worker to actually work. > i.e. logged in as the user in windows running cmd you need to have it so that "nmake" is > accessible and operating correctly. > > Have you completed that step? > > There are multiple ways to set that up - and the approach I took was to run the vcvars64.bat setup > script from Microsoft and then dump the environment and include setting a matching environment in > buildbot.tac. > You can of course copy all the environment variables into the users environment. > > eng at DESKTOP-75K0EME C:\buildbot\tjh-win10-1-tls>type make-env.py > import os > for k, v in os.environ.items(): > ? ? ? ? print('os.environ[\''+str(k)+'\']=\''+str(v).replace('\\','\\\\')+'\'') > > I run that script (in a window that has had vcvars64.bat run) and changed into the buildbot worker > directory (where buildbot.tac exists) > > python make-env.py > env.py > > And I modified buildbot.tac to have: > > def include(filename): > ? ? if os.path.exists(filename): > ? ? ? ? execfile(filename) > > include('env.py') > > That is how I setup a windows based worker configuration - the one you see at? > https://fips.buildbot.openssl.org/#/workers/6 > > Tim. > > On Wed, May 12, 2021 at 9:41 PM Madhur Walia wrote: > > Hi Richard, > > ? > > We restarted buildbot-worker in Windows 2019 and it seems to be connecting now. We could see > files under Base Directory as shown below. > > ? > > We could see couple of errors related to absence of Perl and cmake in build Master Dashboard. > So, we have installed them as well. > > ? > > TableDescription automatically generated > > ? > > Yes, when you SSH, you will be connected to cmd.exe. One of the screenshots we shared had > PowerShell utility but you should be able to run the commands through cmd.exe as well. We are > using the same. > > ? > > Please let us know if you face any issues. > > ? > > Thanks & Regards, > > Madhur > > ? > > From: Richard Levitte > Date: Wednesday, 12 May 2021 at 2:08 PM > To: Madhur Walia > Cc: Richard Levitte , Sunil Kumar Yadav , Manoj > Maskara , Tim Hudson , buildbot-admin at openssl.org < > buildbot-admin at openssl.org>, Bishakha Banerjee > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > The winserver2019 worker did show up once!? At the time, you hadn't > installed the python package pywin32, but when I went in looking, it > looked like you had.? However, the winserver2019 worker isn't showing > up now, could it be that it needs to be restarted? > > Do note that when we SSH to the machine, we end up with a cmd.exe > prompt.? However, the images you've sent us suggest that you run from > a Mingw64 prompt, and I do not know how to get there from cmd.exe, so > it's will need instructions to do restarts for you. > > Cheers, > Richard > > Right now, it looks like you need to get the winserver2019 worker > started.? I hope it's problem free at this point. > > On Fri, 07 May 2021 09:51:22 +0200, > Madhur Walia wrote: > > > > Hi Richard, > > > > We are able to connect to Buildbot Master from Windows 2019 as well now. To our surprise, > > Buildbot-worker/ Python was searching for Certificate directory in base directory. > > > > After pointing ssl-root-dir to a directory hosted in base directory, it was able to connect. > > > > Please confirm the connection. > > > > Also, What are the next steps for Photon 4 and Windows 2019 now? > > > > Thank you for your inputs. > > > > Regards, > > > > Madhur > > > > From: Madhur Walia > > Date: Thursday, 6 May 2021 at 10:04 PM > > To: Richard Levitte , Sunil Kumar Yadav > > Cc: Richard Levitte , Manoj Maskara , Tim Hudson > > , buildbot-admin at openssl.org > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > Thank you Richard. So, Photon 4.0 seems to be okay for now and next update would be from > your > > development team. > > > > We captured a wireshark trace keeping default buildbot.tac and could see ?Unknown CA? > error.? We > > then pointed the trustroots/ ssl-root-dir to a custom path (to pem files), and encountered > another > > error which points to failure in trusting CA certificate filepath. > > > > TextDescription automatically generated????????????????????????????????????? > > > > We tried pointing trustroots directory to absolute certificate directory path but no luck. > > > > Other debugging steps involves, > > > > ????????? Running ?openssl s_client -state -debug -connect buildbot.openssl.org:9989? which > gives > > Verification: OK if we point the -CAfile to Hashed CA pem file names/ location. > > > > ????????? Executing, a python code to verify against CA file path, which shows a successful > CA > > trust in Wireshark, > > > > import os > > > > import requests > > > > r=requests.get(' > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=l2%2FDPVWSKTnB1%2B18yyDzAOEZbjjFCIP%2BfdFdEwcX9wo%3D&reserved=0',verify='C:/Certificates/a.pem > ') > > > > Graphical user interface, text, applicationDescription automatically generat > > > > This either seems to be a platform, (Windows) specific issue or something related to twisted > OR > > something very miniscule that @Sunil Kumar Yadav and I are unable to catch. > > > > I can schedule a call to discuss this in more depth keeping in mind we are almost near to > > completion of 3~4 weeks window. > > > > Please let me know, Sunil and I are based out of India, IST time zone.? We can talk during > IST > > evening, Your Morning. > > > > Thanks & Regards, > > > > Madhur > > > > From: Richard Levitte > > Date: Wednesday, 5 May 2021 at 8:37 PM > > To: Madhur Walia > > Cc: Richard Levitte , Manoj Maskara , Tim Hudson > > , Sunil Kumar Yadav , buildbot-admin at openssl.org > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > As far as I can tell, The Photon 4 worker is good.? The fact that > > "make test" currently fails isn't a problem with the worker as far as > > I can see...? our development team will have to look at it. > > > > As for the Windows worker, it doesn't seem to connect.? Have you > > verified that the two .pem files are in the directory that's specified > > in buildbot.tac? > > > > Cheers, > > Richard > > > > On Wed, 05 May 2021 12:11:46 +0200, > > Madhur Walia wrote: > > > > > > > > > Hi Richard, Tim, > > > > > > Awaiting further updates. Please assist. > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > From: Madhur Walia > > > Date: Monday, 3 May 2021 at 8:18 PM > > > To: Richard Levitte > > > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > > > , buildbot-admin at openssl.org > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > Hi Richard, > > > > > > We have installed git on Photon, please let us know next steps. > > > > > > Installed buildbot and VS2017 on Windows 2019 as shown below but the connection seems to > be > > > dropping, > > > > > > Versions installed on Windows 2019, > > > > > > TextDescription automatically generated????????? > > > > > > Win2019: Connection Failing, going in a loop, > > > > > > Graphical user interface, textDescription automatically generated????? > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > From: Madhur Walia > > > Date: Monday, 3 May 2021 at 2:37 PM > > > To: Richard Levitte > > > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > > > , buildbot-admin at openssl.org > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > Hi Richard, > > > > > > Thank you for the help. We had only installed buildbot-worker on Photon4 and Windows 2019. > After > > > installing Buildbot (master) on Photon4, the worker could start. > > > > > > We are now working on installing git on Photon4 and then troubleshooting Windows 2019. I > will > > keep > > > you updated. > > > > > > Regards, > > > > > > Madhur > > > > > > From: Richard Levitte > > > Date: Monday, 3 May 2021 at 2:33 PM > > > To: Madhur Walia > > > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > > > , buildbot-admin at openssl.org > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > I now noticed that the Photon 4 workers have connected, so I assume > > > the 'optionsForClientTLS' is a thing of the past. > > > > > > Looking at one of the builds, > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TI%2BLbZSdaiW9wzttTf6W6Ee13y9nqGkYEppKBl2r4js%3D&reserved=0 > > > , > > > it looks like git isn't installed on the worker... > > > > > > Cheers, > > > Richard > > > > > > On Mon, 03 May 2021 10:34:57 +0200, > > > Richard Levitte wrote: > > > > > > > > On Mon, 26 Apr 2021 20:25:34 +0200, > > > > Madhur Walia wrote: > > > > > > > > > > Hi Matt, > > > > > > > > > > Thank you for the instructions. However, we are facing couple of issues while starting > > > buildbot-worker, > > > > > > > > > > For both platforms, we pointed Certificate/SSL settings to a custom directory in > > buildbot.tac > > > as per your recommendation.? We also tried importing both certs, isrg-root-xi & > lets-encrypt-r3 > > to > > > trust store of OS but no luck. > > > > > > > > > > Photon, > > > > >????? Getting error, " builtins.NameError: name 'optionsForClientTLS' is not defined" > as > > shown > > > in Photon1 screenshot attached. > > > > >????? Also ran a curl command to check SSL connectivity, seems to be failing, attached > > > screenshot Photon2. > > > > > > > > Please check your versions of the following packages: > > > > > > > > - buildbot (should be at least version 2.6.0) > > > > - twisted (should be at least version 17.9.0 according to buildbot > > > >?? 2.6.0 requirements) > > > > > > > > 'optionsForClientTLS' is a method that appeared in twisted version 14.0. > > > > > > > > > Windows, > > > > >????? Getting, "Unicode error" as shown in Windows1 screenshot attached. > > > > >????? Also ran a curl command to check SSL connectivity, seems to be failing, attached > > > screenshot Windows2. > > > > > > > > From the error message at the end of Windows1.png, you have an invalid > > > > unicode character on line 30.? Could it be a character with diacritics > > > > not encoded with UTF-8? > > > > > > > > Cheers, > > > > Richard > > > > > > > > > Do you have any pointers on these errors? Please let us know. > > > > > > > > > > Thanks & Regards, > > > > > Madhur > > > > > > > > > > ------------------------------------------------------------------ > > > > > > > > > > On 21/04/21, 4:47 PM, "Matt Caswell" wrote: > > > > > > > > > >???? Thanks Manoj. > > > > > > > > > >???? To be able to set up your worker, you must use version 2.6.0 or > > > > >???? higher.? Older version do not support TLS-protected connections. > > > > > > > > > >???? Please see these instructions for installing the buildbot worker > > > > >???? software: > > > > > > > > > >???????? > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zYGoKToLms7AP%2Fefcpd9EdleLdDrnX3lotBLVxPjY3M%3D&reserved=0 > > > > > > > > > >???? When buildbot has been installed on the platform where the buildbot > > > > >???? worker is to be run, this is how a worker is created (for your PhotonOS > > > > >???? worker): > > > > > > > > > >????????? $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > >????????????? buildbot.openssl.org:9989 vmware-photonos40 nifs0Tweex_ > > > > > > > > > >???? And for your Windows server: > > > > > > > > > >????????? $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > >????????????? buildbot.openssl.org:9989 vmware-winserver2019 Efyin.Freg0 > > > > > > > > > > > > > > >???? where BASEDIR is determined by you.? See further down for a few notes > > > > >???? on TLS. > > > > > > > > > >???? To run a buildbot worker, you do this: > > > > > > > > > >????????? $ buildbot-worker start BASEDIR > > > > > > > > > >???? Apart from the software needed to run a buildbot worker, and the > > > > >???? utilities that are the normal part of the operating system, you also > > > > >???? need to ensure that the following components are available: > > > > > > > > > >???? -?? toolchains, i.e. C compiler, linker, make.? If you have specified > > > > >????????? toolchains in the worker request form, you need to ensure that all > > > > >????????? of them are installed. > > > > > > > > > >???? -?? git > > > > > > > > > >???? Regarding TLS, it may be that the buildbot worker platform doesn't > > > > >???? have the appropriate certification verification roots set up.? In that > > > > >???? case, you may need to apply the attached buildbot.tac patch, and store > > > > >???? the attached PEM files in a directory of your choice.? Finish up by > > > > >???? find the string '/PATH/TO/ssl-roots-dir' and replace its contents with > > > > >???? the path of directory where you stored the PEM files. > > > > > > > > > >???? Matt > > > > > > > > > >???? On 21/04/2021 00:56, Manoj Maskara wrote: > > > > >???? > Hi Tim & Richard, > > > > >???? > > > > > >???? > We have filled out the worker-request-form for 2 of our platforms, one unix type > and > > > other Windows. Also, the platforms, for your convenience am listing here: > > > > >???? > > > > > >???? > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge > R740 > > > (Platform type: Unix, x86_64, build+test, gcc) > > > > >???? > 2) Windows Server 2019 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell > PowerEdge > > > R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > >???? > > > > > >???? > Please provide the credentials and instruction on setting up the buildbot > worker. > > > > >???? > > > > > >???? > Thanks, > > > > >???? > Manoj > > > > >???? > > > > > >???? > > > > > >???? > -----Original Message----- > > > > >???? > From: fips-sponsors On Behalf Of Richard > Levitte > > > > >???? > Sent: Monday, April 12, 2021 12:20 AM > > > > >???? > To: fips-sponsors at openssl.org > > > > >???? > Subject: [fips-sponsors] Buildbot workers > > > > >???? > > > > > >???? > Hi, > > > > >???? > > > > > >???? > We are finally ready to start getting buildbot worker requests. > > > > >???? > > > > > >???? > The way this will work is that we're asking you to answer a form with details > for each > > > worker you want to set up for us, such as what platform, what architecture, and where > relevant, > > > what toolchains are installed. > > > > >???? > > > > > >???? > The form is attached below, and include explanations for all the fields to fill > in. > > > Please send it to buildbot-admin at openssl.org. > > > > >???? > > > > > >???? > In response, you will receive an email with the name and password we assign your > > worker > > > (s), and instructions how to set the worker up. > > > > >???? > > > > > > > > > > > [2 Photon1.png ] > > > > > > > > > > [3 Photon2.png ] > > > > > > > > > > [4 Windows1.png ] > > > > > > > > > > [5 Windows2.png ] > > > > > > > > > > [6? ] > > > > > _______________________________________________ > > > > > buildbot-admin mailing list > > > > > buildbot-admin at openssl.org > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6L9gkXe7BuoEq5B0C61BQqp%2BIbKhpQkN3SIIUlC56Vc%3D&reserved=0 > > > > -- > > > > Richard Levitte???????? levitte at openssl.org > > > > OpenSSL Project??????? > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=2tBYFB4HeNnmlOlbCtY3foxltY%2FjAkxw08luxL5rWr0%3D&reserved=0 > > > > _______________________________________________ > > > > buildbot-admin mailing list > > > > buildbot-admin at openssl.org > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Xg1zAuJT5GFZ2v29FvL9ouQrcfnpqoA1Zb8H69sQG%2BM%3D&reserved=0 > > > -- > > > Richard Levitte???????? levitte at openssl.org > > > OpenSSL Project??????? > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > > > > > > > > > > > > > > -- > > Richard Levitte???????? levitte at openssl.org > > OpenSSL Project???????? > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > -- > Richard Levitte???????? levitte at openssl.org > OpenSSL Project???????? > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > > > [2 image001.png ] -- Richard Levitte levitte at openssl.org OpenSSL Project http://www.openssl.org/~levitte/ From tjh at openssl.org Thu May 13 06:00:24 2021 From: tjh at openssl.org (Tim Hudson) Date: Thu, 13 May 2021 16:00:24 +1000 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: <87wns3qiv3.wl-levitte@openssl.org> References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org> <87zgx0qrda.wl-levitte@openssl.org> <87wns3qiv3.wl-levitte@openssl.org> Message-ID: I did tell you this at the time - that the environment needed to be configured to be useful and that it wasn't "normal" in a windows environment to have all that fluff in your system environment. I also suspected you had not done a "pure" windows setup ... in that I'm even using the microsoft ssh server. And I also did tell you what I did in the end as I'm not going to place a pile of junk in the user account when I need to be able to switch between compiler versions and targets :-) Tim. On Thu, May 13, 2021 at 3:54 PM Richard Levitte wrote: > [ NOTE: Tim and buildbot-admin only ] > > I was actually surprised by this, as I've had no issues running > Configure without any extra arguments on Windows, without having CL in > the path. > > ... it turns out, though, that my Strawberry installation, which I > set up a looooong time ago, includes gcc.exe, so Configure finds that > and is all happy that it found *a* compiler, even though it's not the > one actually used. > > Oy... > > So ok, lesson learned, we need to wrap the 'perl Configure' run with > the wrapper script I use for all the nmake runs. AND OpenSSL::config > needs to learn about CL. > > Cheers, > Richard ( today is a holyday, so I won't do much more than this for > the day ) > > On Thu, 13 May 2021 03:41:41 +0200, > Tim Hudson wrote: > > > > You can see the current issue is that nmake isn't in the path. > > See https://fips.buildbot.openssl.org/#/builders/31/builds/3 > > > > You need to have that setup for the buildbot worker to actually work. > > i.e. logged in as the user in windows running cmd you need to have it so > that "nmake" is > > accessible and operating correctly. > > > > Have you completed that step? > > > > There are multiple ways to set that up - and the approach I took was to > run the vcvars64.bat setup > > script from Microsoft and then dump the environment and include setting > a matching environment in > > buildbot.tac. > > You can of course copy all the environment variables into the users > environment. > > > > eng at DESKTOP-75K0EME C:\buildbot\tjh-win10-1-tls>type make-env.py > > import os > > for k, v in os.environ.items(): > > > print('os.environ[\''+str(k)+'\']=\''+str(v).replace('\\','\\\\')+'\'') > > > > I run that script (in a window that has had vcvars64.bat run) and > changed into the buildbot worker > > directory (where buildbot.tac exists) > > > > python make-env.py > env.py > > > > And I modified buildbot.tac to have: > > > > def include(filename): > > if os.path.exists(filename): > > execfile(filename) > > > > include('env.py') > > > > That is how I setup a windows based worker configuration - the one you > see at > > https://fips.buildbot.openssl.org/#/workers/6 > > > > Tim. > > > > On Wed, May 12, 2021 at 9:41 PM Madhur Walia wrote: > > > > Hi Richard, > > > > > > > > We restarted buildbot-worker in Windows 2019 and it seems to be > connecting now. We could see > > files under Base Directory as shown below. > > > > > > > > We could see couple of errors related to absence of Perl and cmake > in build Master Dashboard. > > So, we have installed them as well. > > > > > > > > TableDescription automatically generated > > > > > > > > Yes, when you SSH, you will be connected to cmd.exe. One of the > screenshots we shared had > > PowerShell utility but you should be able to run the commands > through cmd.exe as well. We are > > using the same. > > > > > > > > Please let us know if you face any issues. > > > > > > > > Thanks & Regards, > > > > Madhur > > > > > > > > From: Richard Levitte > > Date: Wednesday, 12 May 2021 at 2:08 PM > > To: Madhur Walia > > Cc: Richard Levitte , Sunil Kumar Yadav < > ysunilkumar at vmware.com>, Manoj > > Maskara , Tim Hudson , > buildbot-admin at openssl.org < > > buildbot-admin at openssl.org>, Bishakha Banerjee > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > The winserver2019 worker did show up once! At the time, you hadn't > > installed the python package pywin32, but when I went in looking, it > > looked like you had. However, the winserver2019 worker isn't showing > > up now, could it be that it needs to be restarted? > > > > Do note that when we SSH to the machine, we end up with a cmd.exe > > prompt. However, the images you've sent us suggest that you run from > > a Mingw64 prompt, and I do not know how to get there from cmd.exe, so > > it's will need instructions to do restarts for you. > > > > Cheers, > > Richard > > > > Right now, it looks like you need to get the winserver2019 worker > > started. I hope it's problem free at this point. > > > > On Fri, 07 May 2021 09:51:22 +0200, > > Madhur Walia wrote: > > > > > > Hi Richard, > > > > > > We are able to connect to Buildbot Master from Windows 2019 as > well now. To our surprise, > > > Buildbot-worker/ Python was searching for Certificate directory in > base directory. > > > > > > After pointing ssl-root-dir to a directory hosted in base > directory, it was able to connect. > > > > > > Please confirm the connection. > > > > > > Also, What are the next steps for Photon 4 and Windows 2019 now? > > > > > > Thank you for your inputs. > > > > > > Regards, > > > > > > Madhur > > > > > > From: Madhur Walia > > > Date: Thursday, 6 May 2021 at 10:04 PM > > > To: Richard Levitte , Sunil Kumar Yadav < > ysunilkumar at vmware.com> > > > Cc: Richard Levitte , Manoj Maskara < > mmaskara at vmware.com>, Tim Hudson > > > , buildbot-admin at openssl.org < > buildbot-admin at openssl.org> > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > Thank you Richard. So, Photon 4.0 seems to be okay for now and > next update would be from > > your > > > development team. > > > > > > We captured a wireshark trace keeping default buildbot.tac and > could see ?Unknown CA? > > error. We > > > then pointed the trustroots/ ssl-root-dir to a custom path (to pem > files), and encountered > > another > > > error which points to failure in trusting CA certificate filepath. > > > > > > TextDescription automatically > generated > > > > > > We tried pointing trustroots directory to absolute certificate > directory path but no luck. > > > > > > Other debugging steps involves, > > > > > > ? Running ?openssl s_client -state -debug -connect > buildbot.openssl.org:9989? which > > gives > > > Verification: OK if we point the -CAfile to Hashed CA pem file > names/ location. > > > > > > ? Executing, a python code to verify against CA file path, > which shows a successful > > CA > > > trust in Wireshark, > > > > > > import os > > > > > > import requests > > > > > > r=requests.get(' > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=l2%2FDPVWSKTnB1%2B18yyDzAOEZbjjFCIP%2BfdFdEwcX9wo%3D&reserved=0 > ',verify='C:/Certificates/a.pem > > ') > > > > > > Graphical user interface, text, applicationDescription > automatically generat > > > > > > This either seems to be a platform, (Windows) specific issue or > something related to twisted > > OR > > > something very miniscule that @Sunil Kumar Yadav and I are unable > to catch. > > > > > > I can schedule a call to discuss this in more depth keeping in > mind we are almost near to > > > completion of 3~4 weeks window. > > > > > > Please let me know, Sunil and I are based out of India, IST time > zone. We can talk during > > IST > > > evening, Your Morning. > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > From: Richard Levitte > > > Date: Wednesday, 5 May 2021 at 8:37 PM > > > To: Madhur Walia > > > Cc: Richard Levitte , Manoj Maskara < > mmaskara at vmware.com>, Tim Hudson > > > , Sunil Kumar Yadav , > buildbot-admin at openssl.org > > > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > As far as I can tell, The Photon 4 worker is good. The fact that > > > "make test" currently fails isn't a problem with the worker as far > as > > > I can see... our development team will have to look at it. > > > > > > As for the Windows worker, it doesn't seem to connect. Have you > > > verified that the two .pem files are in the directory that's > specified > > > in buildbot.tac? > > > > > > Cheers, > > > Richard > > > > > > On Wed, 05 May 2021 12:11:46 +0200, > > > Madhur Walia wrote: > > > > > > > > > > > > Hi Richard, Tim, > > > > > > > > Awaiting further updates. Please assist. > > > > > > > > Thanks & Regards, > > > > > > > > Madhur > > > > > > > > From: Madhur Walia > > > > Date: Monday, 3 May 2021 at 8:18 PM > > > > To: Richard Levitte > > > > Cc: Manoj Maskara , Tim Hudson < > tjh at openssl.org>, Sunil Kumar Yadav > > > > , buildbot-admin at openssl.org < > buildbot-admin at openssl.org> > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > Hi Richard, > > > > > > > > We have installed git on Photon, please let us know next steps. > > > > > > > > Installed buildbot and VS2017 on Windows 2019 as shown below but > the connection seems to > > be > > > > dropping, > > > > > > > > Versions installed on Windows 2019, > > > > > > > > TextDescription automatically generated > > > > > > > > Win2019: Connection Failing, going in a loop, > > > > > > > > Graphical user interface, textDescription automatically > generated > > > > > > > > Thanks & Regards, > > > > > > > > Madhur > > > > > > > > From: Madhur Walia > > > > Date: Monday, 3 May 2021 at 2:37 PM > > > > To: Richard Levitte > > > > Cc: Manoj Maskara , Tim Hudson < > tjh at openssl.org>, Sunil Kumar Yadav > > > > , buildbot-admin at openssl.org < > buildbot-admin at openssl.org> > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > Hi Richard, > > > > > > > > Thank you for the help. We had only installed buildbot-worker on > Photon4 and Windows 2019. > > After > > > > installing Buildbot (master) on Photon4, the worker could start. > > > > > > > > We are now working on installing git on Photon4 and then > troubleshooting Windows 2019. I > > will > > > keep > > > > you updated. > > > > > > > > Regards, > > > > > > > > Madhur > > > > > > > > From: Richard Levitte > > > > Date: Monday, 3 May 2021 at 2:33 PM > > > > To: Madhur Walia > > > > Cc: Manoj Maskara , Tim Hudson < > tjh at openssl.org>, Sunil Kumar Yadav > > > > , buildbot-admin at openssl.org < > buildbot-admin at openssl.org> > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > I now noticed that the Photon 4 workers have connected, so I > assume > > > > the 'optionsForClientTLS' is a thing of the past. > > > > > > > > Looking at one of the builds, > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TI%2BLbZSdaiW9wzttTf6W6Ee13y9nqGkYEppKBl2r4js%3D&reserved=0 > > > > , > > > > it looks like git isn't installed on the worker... > > > > > > > > Cheers, > > > > Richard > > > > > > > > On Mon, 03 May 2021 10:34:57 +0200, > > > > Richard Levitte wrote: > > > > > > > > > > On Mon, 26 Apr 2021 20:25:34 +0200, > > > > > Madhur Walia wrote: > > > > > > > > > > > > Hi Matt, > > > > > > > > > > > > Thank you for the instructions. However, we are facing > couple of issues while starting > > > > buildbot-worker, > > > > > > > > > > > > For both platforms, we pointed Certificate/SSL settings to a > custom directory in > > > buildbot.tac > > > > as per your recommendation. We also tried importing both certs, > isrg-root-xi & > > lets-encrypt-r3 > > > to > > > > trust store of OS but no luck. > > > > > > > > > > > > Photon, > > > > > > Getting error, " builtins.NameError: name > 'optionsForClientTLS' is not defined" > > as > > > shown > > > > in Photon1 screenshot attached. > > > > > > Also ran a curl command to check SSL connectivity, > seems to be failing, attached > > > > screenshot Photon2. > > > > > > > > > > Please check your versions of the following packages: > > > > > > > > > > - buildbot (should be at least version 2.6.0) > > > > > - twisted (should be at least version 17.9.0 according to > buildbot > > > > > 2.6.0 requirements) > > > > > > > > > > 'optionsForClientTLS' is a method that appeared in twisted > version 14.0. > > > > > > > > > > > Windows, > > > > > > Getting, "Unicode error" as shown in Windows1 > screenshot attached. > > > > > > Also ran a curl command to check SSL connectivity, > seems to be failing, attached > > > > screenshot Windows2. > > > > > > > > > > From the error message at the end of Windows1.png, you have an > invalid > > > > > unicode character on line 30. Could it be a character with > diacritics > > > > > not encoded with UTF-8? > > > > > > > > > > Cheers, > > > > > Richard > > > > > > > > > > > Do you have any pointers on these errors? Please let us know. > > > > > > > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > > > > > > > > ------------------------------------------------------------------ > > > > > > > > > > > > On 21/04/21, 4:47 PM, "Matt Caswell" > wrote: > > > > > > > > > > > > Thanks Manoj. > > > > > > > > > > > > To be able to set up your worker, you must use version > 2.6.0 or > > > > > > higher. Older version do not support TLS-protected > connections. > > > > > > > > > > > > Please see these instructions for installing the > buildbot worker > > > > > > software: > > > > > > > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zYGoKToLms7AP%2Fefcpd9EdleLdDrnX3lotBLVxPjY3M%3D&reserved=0 > > > > > > > > > > > > When buildbot has been installed on the platform where > the buildbot > > > > > > worker is to be run, this is how a worker is created > (for your PhotonOS > > > > > > worker): > > > > > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > > buildbot.openssl.org:9989 vmware-photonos40 > nifs0Tweex_ > > > > > > > > > > > > And for your Windows server: > > > > > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > > buildbot.openssl.org:9989 vmware-winserver2019 > Efyin.Freg0 > > > > > > > > > > > > > > > > > > where BASEDIR is determined by you. See further down > for a few notes > > > > > > on TLS. > > > > > > > > > > > > To run a buildbot worker, you do this: > > > > > > > > > > > > $ buildbot-worker start BASEDIR > > > > > > > > > > > > Apart from the software needed to run a buildbot worker, > and the > > > > > > utilities that are the normal part of the operating > system, you also > > > > > > need to ensure that the following components are > available: > > > > > > > > > > > > - toolchains, i.e. C compiler, linker, make. If you > have specified > > > > > > toolchains in the worker request form, you need to > ensure that all > > > > > > of them are installed. > > > > > > > > > > > > - git > > > > > > > > > > > > Regarding TLS, it may be that the buildbot worker > platform doesn't > > > > > > have the appropriate certification verification roots > set up. In that > > > > > > case, you may need to apply the attached buildbot.tac > patch, and store > > > > > > the attached PEM files in a directory of your choice. > Finish up by > > > > > > find the string '/PATH/TO/ssl-roots-dir' and replace its > contents with > > > > > > the path of directory where you stored the PEM files. > > > > > > > > > > > > Matt > > > > > > > > > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > > > > > Hi Tim & Richard, > > > > > > > > > > > > > > We have filled out the worker-request-form for 2 of > our platforms, one unix type > > and > > > > other Windows. Also, the platforms, for your convenience am > listing here: > > > > > > > > > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon > Gold 6230R on Dell PowerEdge > > R740 > > > > (Platform type: Unix, x86_64, build+test, gcc) > > > > > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel > Xeon Gold 6230R on Dell > > PowerEdge > > > > R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > > > > > > > > > Please provide the credentials and instruction on > setting up the buildbot > > worker. > > > > > > > > > > > > > > Thanks, > > > > > > > Manoj > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: fips-sponsors > On Behalf Of Richard > > Levitte > > > > > > > Sent: Monday, April 12, 2021 12:20 AM > > > > > > > To: fips-sponsors at openssl.org > > > > > > > Subject: [fips-sponsors] Buildbot workers > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > We are finally ready to start getting buildbot worker > requests. > > > > > > > > > > > > > > The way this will work is that we're asking you to > answer a form with details > > for each > > > > worker you want to set up for us, such as what platform, what > architecture, and where > > relevant, > > > > what toolchains are installed. > > > > > > > > > > > > > > The form is attached below, and include explanations > for all the fields to fill > > in. > > > > Please send it to buildbot-admin at openssl.org. > > > > > > > > > > > > > > In response, you will receive an email with the name > and password we assign your > > > worker > > > > (s), and instructions how to set the worker up. > > > > > > > > > > > > > > > > > > > [2 Photon1.png ] > > > > > > > > > > > > [3 Photon2.png ] > > > > > > > > > > > > [4 Windows1.png ] > > > > > > > > > > > > [5 Windows2.png ] > > > > > > > > > > > > [6 ] > > > > > > _______________________________________________ > > > > > > buildbot-admin mailing list > > > > > > buildbot-admin at openssl.org > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6L9gkXe7BuoEq5B0C61BQqp%2BIbKhpQkN3SIIUlC56Vc%3D&reserved=0 > > > > > -- > > > > > Richard Levitte levitte at openssl.org > > > > > OpenSSL Project > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=2tBYFB4HeNnmlOlbCtY3foxltY%2FjAkxw08luxL5rWr0%3D&reserved=0 > > > > > _______________________________________________ > > > > > buildbot-admin mailing list > > > > > buildbot-admin at openssl.org > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Xg1zAuJT5GFZ2v29FvL9ouQrcfnpqoA1Zb8H69sQG%2BM%3D&reserved=0 > > > > -- > > > > Richard Levitte levitte at openssl.org > > > > OpenSSL Project > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > > > > > > > > > > > > > > > > > > > -- > > > Richard Levitte levitte at openssl.org > > > OpenSSL Project > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > > -- > > Richard Levitte levitte at openssl.org > > OpenSSL Project > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > > > > > > [2 image001.png ] > -- > Richard Levitte levitte at openssl.org > OpenSSL Project http://www.openssl.org/~levitte/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From levitte at openssl.org Thu May 13 06:27:34 2021 From: levitte at openssl.org (Richard Levitte) Date: Thu, 13 May 2021 08:27:34 +0200 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org> <87zgx0qrda.wl-levitte@openssl.org> <87wns3qiv3.wl-levitte@openssl.org> Message-ID: <87v97nqhbd.wl-levitte@openssl.org> I know what you told me. I also know that we discussed it in terms of toolchains, and ended up making a wrapper script that takes care of the MSVC setup. If you look at your own builds, you will see that there is a wrapper script used, called 'wrap.cmd'. So strictly speaking, the env.py setup that you have should no longer be necessary. However, doing so currently requires that the available toolchains are declared in the worker request form that we get. The thing I hadn't quite caught on to, though, was that OpenSSL's Configure can't determine the config target to use based on what compiler it has available, for the moment. So what I did just now was to modify the MSVC toolchain setups to use the correct VC-WINxx config target for the desired architecture to build for. With that, I suspect that VMware's stuff will work better. Cheers, Richard On Thu, 13 May 2021 08:00:24 +0200, Tim Hudson wrote: > > I did tell you this at the time - that the environment needed to be configured to be useful and > that it wasn't "normal" in a windows environment to have all that fluff in your system > environment. > I also suspected you had not done a "pure" windows setup ... in that I'm even using the microsoft > ssh server. > > And I also did tell you what I did in the end as I'm not going to place a pile of junk in the user > account when I need to be able to switch between compiler versions and targets :-) > > Tim. > > On Thu, May 13, 2021 at 3:54 PM Richard Levitte wrote: > > [ NOTE: Tim and buildbot-admin only ] > > I was actually surprised by this, as I've had no issues running > Configure without any extra arguments on Windows, without having CL in > the path. > > ...? it turns out, though, that my Strawberry installation, which I > set up a looooong time ago, includes gcc.exe, so Configure finds that > and is all happy that it found *a* compiler, even though it's not the > one actually used. > > Oy... > > So ok, lesson learned, we need to wrap the 'perl Configure' run with > the wrapper script I use for all the nmake runs.? AND OpenSSL::config > needs to learn about CL. > > Cheers, > Richard ( today is a holyday, so I won't do much more than this for > ? ? ? ? ? the day ) > > On Thu, 13 May 2021 03:41:41 +0200, > Tim Hudson wrote: > > > > You can see the current issue is that nmake isn't in the path. > > See?https://fips.buildbot.openssl.org/#/builders/31/builds/3 > > > > You need to have that setup for the buildbot worker to actually work. > > i.e. logged in as the user in windows running cmd you need to have it so that "nmake" is > > accessible and operating correctly. > > > > Have you completed that step? > > > > There are multiple ways to set that up - and the approach I took was to run the vcvars64.bat > setup > > script from Microsoft and then dump the environment and include setting a matching > environment in > > buildbot.tac. > > You can of course copy all the environment variables into the users environment. > > > > eng at DESKTOP-75K0EME C:\buildbot\tjh-win10-1-tls>type make-env.py > > import os > > for k, v in os.environ.items(): > > ? ? ? ? print('os.environ[\''+str(k)+'\']=\''+str(v).replace('\\','\\\\')+'\'') > > > > I run that script (in a window that has had vcvars64.bat run) and changed into the buildbot > worker > > directory (where buildbot.tac exists) > > > > python make-env.py > env.py > > > > And I modified buildbot.tac to have: > > > > def include(filename): > > ? ? if os.path.exists(filename): > > ? ? ? ? execfile(filename) > > > > include('env.py') > > > > That is how I setup a windows based worker configuration - the one you see at? > > https://fips.buildbot.openssl.org/#/workers/6 > > > > Tim. > > > > On Wed, May 12, 2021 at 9:41 PM Madhur Walia wrote: > > > >? ? ?Hi Richard, > >? ? > >? ? ?? > >? ? > >? ? ?We restarted buildbot-worker in Windows 2019 and it seems to be connecting now. We could > see > >? ? ?files under Base Directory as shown below. > >? ? > >? ? ?? > >? ? > >? ? ?We could see couple of errors related to absence of Perl and cmake in build Master > Dashboard. > >? ? ?So, we have installed them as well. > >? ? > >? ? ?? > > > >? ? ?TableDescription automatically generated? ? ? ? ? ? > >? ? > >? ? ?? > >? ? > >? ? ?Yes, when you SSH, you will be connected to cmd.exe. One of the screenshots we shared > had > >? ? ?PowerShell utility but you should be able to run the commands through cmd.exe as well. > We are > >? ? ?using the same. > >? ? > >? ? ?? > >? ? > >? ? ?Please let us know if you face any issues. > >? ? > >? ? ?? > >? ? > >? ? ?Thanks & Regards, > >? ? > >? ? ?Madhur > >? ? > >? ? ?? > >? ? > >? ? ?From: Richard Levitte > >? ? ?Date: Wednesday, 12 May 2021 at 2:08 PM > >? ? ?To: Madhur Walia > >? ? ?Cc: Richard Levitte , Sunil Kumar Yadav , > Manoj > >? ? ?Maskara , Tim Hudson , buildbot-admin at openssl.org > < > >? ? ?buildbot-admin at openssl.org>, Bishakha Banerjee > >? ? ?Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > >? ? > >? ? ?The winserver2019 worker did show up once!? At the time, you hadn't > >? ? ?installed the python package pywin32, but when I went in looking, it > >? ? ?looked like you had.? However, the winserver2019 worker isn't showing > >? ? ?up now, could it be that it needs to be restarted? > >? ? > >? ? ?Do note that when we SSH to the machine, we end up with a cmd.exe > >? ? ?prompt.? However, the images you've sent us suggest that you run from > >? ? ?a Mingw64 prompt, and I do not know how to get there from cmd.exe, so > >? ? ?it's will need instructions to do restarts for you. > >? ? > >? ? ?Cheers, > >? ? ?Richard > >? ? > >? ? ?Right now, it looks like you need to get the winserver2019 worker > >? ? ?started.? I hope it's problem free at this point. > >? ? > >? ? ?On Fri, 07 May 2021 09:51:22 +0200, > >? ? ?Madhur Walia wrote: > >? ? ?> > >? ? ?> Hi Richard, > >? ? ?> > >? ? ?> We are able to connect to Buildbot Master from Windows 2019 as well now. To our > surprise, > >? ? ?> Buildbot-worker/ Python was searching for Certificate directory in base directory. > >? ? ?> > >? ? ?> After pointing ssl-root-dir to a directory hosted in base directory, it was able to > connect. > >? ? ?> > >? ? ?> Please confirm the connection. > >? ? ?> > >? ? ?> Also, What are the next steps for Photon 4 and Windows 2019 now? > >? ? ?> > >? ? ?> Thank you for your inputs. > >? ? ?> > >? ? ?> Regards, > >? ? ?> > >? ? ?> Madhur > >? ? ?> > >? ? ?> From: Madhur Walia > >? ? ?> Date: Thursday, 6 May 2021 at 10:04 PM > >? ? ?> To: Richard Levitte , Sunil Kumar Yadav > >? ? ?> Cc: Richard Levitte , Manoj Maskara , Tim > Hudson > >? ? ?> , buildbot-admin at openssl.org > >? ? ?> Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > >? ? ?> > >? ? ?> Thank you Richard. So, Photon 4.0 seems to be okay for now and next update would be > from > >? ? ?your > >? ? ?> development team. > >? ? ?> > >? ? ?> We captured a wireshark trace keeping default buildbot.tac and could see ?Unknown CA? > >? ? ?error.? We > >? ? ?> then pointed the trustroots/ ssl-root-dir to a custom path (to pem files), and > encountered > >? ? ?another > >? ? ?> error which points to failure in trusting CA certificate filepath. > >? ? ?> > >? ? ?> TextDescription automatically generated????????????????????????????????????? > >? ? ?> > >? ? ?> We tried pointing trustroots directory to absolute certificate directory path but no > luck. > >? ? ?> > >? ? ?> Other debugging steps involves, > >? ? ?> > >? ? ?> ????????? Running ?openssl s_client -state -debug -connect buildbot.openssl.org:9989? > which > >? ? ?gives > >? ? ?> Verification: OK if we point the -CAfile to Hashed CA pem file names/ location. > >? ? ?> > >? ? ?> ????????? Executing, a python code to verify against CA file path, which shows a > successful > >? ? ?CA > >? ? ?> trust in Wireshark, > >? ? ?> > >? ? ?> import os > >? ? ?> > >? ? ?> import requests > >? ? ?> > >? ? ?> r=requests.get(' > >? ? ? > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=l2%2FDPVWSKTnB1%2B18yyDzAOEZbjjFCIP%2BfdFdEwcX9wo%3D&reserved=0 > ',verify='C:/Certificates/a.pem > >? ? ?') > >? ? ?> > >? ? ?> Graphical user interface, text, applicationDescription automatically generat > >? ? ?> > >? ? ?> This either seems to be a platform, (Windows) specific issue or something related to > twisted > >? ? ?OR > >? ? ?> something very miniscule that @Sunil Kumar Yadav and I are unable to catch. > >? ? ?> > >? ? ?> I can schedule a call to discuss this in more depth keeping in mind we are almost near > to > >? ? ?> completion of 3~4 weeks window. > >? ? ?> > >? ? ?> Please let me know, Sunil and I are based out of India, IST time zone.? We can talk > during > >? ? ?IST > >? ? ?> evening, Your Morning. > >? ? ?> > >? ? ?> Thanks & Regards, > >? ? ?> > >? ? ?> Madhur > >? ? ?> > >? ? ?> From: Richard Levitte > >? ? ?> Date: Wednesday, 5 May 2021 at 8:37 PM > >? ? ?> To: Madhur Walia > >? ? ?> Cc: Richard Levitte , Manoj Maskara , Tim > Hudson > >? ? ?> , Sunil Kumar Yadav , > buildbot-admin at openssl.org > >? ? ?> > >? ? ?> Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > >? ? ?> > >? ? ?> As far as I can tell, The Photon 4 worker is good.? The fact that > >? ? ?> "make test" currently fails isn't a problem with the worker as far as > >? ? ?> I can see...? our development team will have to look at it. > >? ? ?> > >? ? ?> As for the Windows worker, it doesn't seem to connect.? Have you > >? ? ?> verified that the two .pem files are in the directory that's specified > >? ? ?> in buildbot.tac? > >? ? ?> > >? ? ?> Cheers, > >? ? ?> Richard > >? ? ?> > >? ? ?> On Wed, 05 May 2021 12:11:46 +0200, > >? ? ?> Madhur Walia wrote: > >? ? ?> > > >? ? ?> > > >? ? ?> > Hi Richard, Tim, > >? ? ?> > > >? ? ?> > Awaiting further updates. Please assist. > >? ? ?> > > >? ? ?> > Thanks & Regards, > >? ? ?> > > >? ? ?> > Madhur > >? ? ?> > > >? ? ?> > From: Madhur Walia > >? ? ?> > Date: Monday, 3 May 2021 at 8:18 PM > >? ? ?> > To: Richard Levitte > >? ? ?> > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar > Yadav > >? ? ?> > , buildbot-admin at openssl.org > >? ? ?> > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > >? ? ?> > > >? ? ?> > Hi Richard, > >? ? ?> > > >? ? ?> > We have installed git on Photon, please let us know next steps. > >? ? ?> > > >? ? ?> > Installed buildbot and VS2017 on Windows 2019 as shown below but the connection > seems to > >? ? ?be > >? ? ?> > dropping, > >? ? ?> > > >? ? ?> > Versions installed on Windows 2019, > >? ? ?> > > >? ? ?> > TextDescription automatically generated????????? > >? ? ?> > > >? ? ?> > Win2019: Connection Failing, going in a loop, > >? ? ?> > > >? ? ?> > Graphical user interface, textDescription automatically generated????? > >? ? ?> > > >? ? ?> > Thanks & Regards, > >? ? ?> > > >? ? ?> > Madhur > >? ? ?> > > >? ? ?> > From: Madhur Walia > >? ? ?> > Date: Monday, 3 May 2021 at 2:37 PM > >? ? ?> > To: Richard Levitte > >? ? ?> > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar > Yadav > >? ? ?> > , buildbot-admin at openssl.org > >? ? ?> > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > >? ? ?> > > >? ? ?> > Hi Richard, > >? ? ?> > > >? ? ?> > Thank you for the help. We had only installed buildbot-worker on Photon4 and Windows > 2019. > >? ? ?After > >? ? ?> > installing Buildbot (master) on Photon4, the worker could start. > >? ? ?> > > >? ? ?> > We are now working on installing git on Photon4 and then troubleshooting Windows > 2019. I > >? ? ?will > >? ? ?> keep > >? ? ?> > you updated. > >? ? ?> > > >? ? ?> > Regards, > >? ? ?> > > >? ? ?> > Madhur > >? ? ?> > > >? ? ?> > From: Richard Levitte > >? ? ?> > Date: Monday, 3 May 2021 at 2:33 PM > >? ? ?> > To: Madhur Walia > >? ? ?> > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar > Yadav > >? ? ?> > , buildbot-admin at openssl.org > >? ? ?> > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > >? ? ?> > > >? ? ?> > I now noticed that the Photon 4 workers have connected, so I assume > >? ? ?> > the 'optionsForClientTLS' is a thing of the past. > >? ? ?> > > >? ? ?> > Looking at one of the builds, > >? ? ?> > > >? ? ?> > >? ? ? > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TI%2BLbZSdaiW9wzttTf6W6Ee13y9nqGkYEppKBl2r4js%3D&reserved=0 > >? ? ?> > , > >? ? ?> > it looks like git isn't installed on the worker... > >? ? ?> > > >? ? ?> > Cheers, > >? ? ?> > Richard > >? ? ?> > > >? ? ?> > On Mon, 03 May 2021 10:34:57 +0200, > >? ? ?> > Richard Levitte wrote: > >? ? ?> > > > >? ? ?> > > On Mon, 26 Apr 2021 20:25:34 +0200, > >? ? ?> > > Madhur Walia wrote: > >? ? ?> > > > > >? ? ?> > > > Hi Matt, > >? ? ?> > > > > >? ? ?> > > > Thank you for the instructions. However, we are facing couple of issues while > starting > >? ? ?> > buildbot-worker, > >? ? ?> > > > > >? ? ?> > > > For both platforms, we pointed Certificate/SSL settings to a custom directory in > >? ? ?> buildbot.tac > >? ? ?> > as per your recommendation.? We also tried importing both certs, isrg-root-xi & > >? ? ?lets-encrypt-r3 > >? ? ?> to > >? ? ?> > trust store of OS but no luck. > >? ? ?> > > > > >? ? ?> > > > Photon, > >? ? ?> > > >????? Getting error, " builtins.NameError: name 'optionsForClientTLS' is not > defined" > >? ? ?as > >? ? ?> shown > >? ? ?> > in Photon1 screenshot attached. > >? ? ?> > > >????? Also ran a curl command to check SSL connectivity, seems to be failing, > attached > >? ? ?> > screenshot Photon2. > >? ? ?> > > > >? ? ?> > > Please check your versions of the following packages: > >? ? ?> > > > >? ? ?> > > - buildbot (should be at least version 2.6.0) > >? ? ?> > > - twisted (should be at least version 17.9.0 according to buildbot > >? ? ?> > >?? 2.6.0 requirements) > >? ? ?> > > > >? ? ?> > > 'optionsForClientTLS' is a method that appeared in twisted version 14.0. > >? ? ?> > > > >? ? ?> > > > Windows, > >? ? ?> > > >????? Getting, "Unicode error" as shown in Windows1 screenshot attached. > >? ? ?> > > >????? Also ran a curl command to check SSL connectivity, seems to be failing, > attached > >? ? ?> > screenshot Windows2. > >? ? ?> > > > >? ? ?> > > From the error message at the end of Windows1.png, you have an invalid > >? ? ?> > > unicode character on line 30.? Could it be a character with diacritics > >? ? ?> > > not encoded with UTF-8? > >? ? ?> > > > >? ? ?> > > Cheers, > >? ? ?> > > Richard > >? ? ?> > > > >? ? ?> > > > Do you have any pointers on these errors? Please let us know. > >? ? ?> > > > > >? ? ?> > > > Thanks & Regards, > >? ? ?> > > > Madhur > >? ? ?> > > > > >? ? ?> > > > ------------------------------------------------------------------ > >? ? ?> > > > > >? ? ?> > > > On 21/04/21, 4:47 PM, "Matt Caswell" wrote: > >? ? ?> > > > > >? ? ?> > > >???? Thanks Manoj. > >? ? ?> > > > > >? ? ?> > > >???? To be able to set up your worker, you must use version 2.6.0 or > >? ? ?> > > >???? higher.? Older version do not support TLS-protected connections. > >? ? ?> > > > > >? ? ?> > > >???? Please see these instructions for installing the buildbot worker > >? ? ?> > > >???? software: > >? ? ?> > > > > >? ? ?> > > >???????? > >? ? ?> > > >? ? ?> > >? ? ? > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zYGoKToLms7AP%2Fefcpd9EdleLdDrnX3lotBLVxPjY3M%3D&reserved=0 > >? ? ?> > > > > >? ? ?> > > >???? When buildbot has been installed on the platform where the buildbot > >? ? ?> > > >???? worker is to be run, this is how a worker is created (for your PhotonOS > >? ? ?> > > >???? worker): > >? ? ?> > > > > >? ? ?> > > >????????? $ buildbot-worker create-worker --use-tls BASEDIR \ > >? ? ?> > > >????????????? buildbot.openssl.org:9989 vmware-photonos40 nifs0Tweex_ > >? ? ?> > > > > >? ? ?> > > >???? And for your Windows server: > >? ? ?> > > > > >? ? ?> > > >????????? $ buildbot-worker create-worker --use-tls BASEDIR \ > >? ? ?> > > >????????????? buildbot.openssl.org:9989 vmware-winserver2019 Efyin.Freg0 > >? ? ?> > > > > >? ? ?> > > > > >? ? ?> > > >???? where BASEDIR is determined by you.? See further down for a few notes > >? ? ?> > > >???? on TLS. > >? ? ?> > > > > >? ? ?> > > >???? To run a buildbot worker, you do this: > >? ? ?> > > > > >? ? ?> > > >????????? $ buildbot-worker start BASEDIR > >? ? ?> > > > > >? ? ?> > > >???? Apart from the software needed to run a buildbot worker, and the > >? ? ?> > > >???? utilities that are the normal part of the operating system, you also > >? ? ?> > > >???? need to ensure that the following components are available: > >? ? ?> > > > > >? ? ?> > > >???? -?? toolchains, i.e. C compiler, linker, make.? If you have specified > >? ? ?> > > >????????? toolchains in the worker request form, you need to ensure that all > >? ? ?> > > >????????? of them are installed. > >? ? ?> > > > > >? ? ?> > > >???? -?? git > >? ? ?> > > > > >? ? ?> > > >???? Regarding TLS, it may be that the buildbot worker platform doesn't > >? ? ?> > > >???? have the appropriate certification verification roots set up.? In that > >? ? ?> > > >???? case, you may need to apply the attached buildbot.tac patch, and store > >? ? ?> > > >???? the attached PEM files in a directory of your choice.? Finish up by > >? ? ?> > > >???? find the string '/PATH/TO/ssl-roots-dir' and replace its contents with > >? ? ?> > > >???? the path of directory where you stored the PEM files. > >? ? ?> > > > > >? ? ?> > > >???? Matt > >? ? ?> > > > > >? ? ?> > > >???? On 21/04/2021 00:56, Manoj Maskara wrote: > >? ? ?> > > >???? > Hi Tim & Richard, > >? ? ?> > > >???? > > >? ? ?> > > >???? > We have filled out the worker-request-form for 2 of our platforms, one > unix type > >? ? ?and > >? ? ?> > other Windows. Also, the platforms, for your convenience am listing here: > >? ? ?> > > >???? > > >? ? ?> > > >???? > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell > PowerEdge > >? ? ?R740 > >? ? ?> > (Platform type: Unix, x86_64, build+test, gcc) > >? ? ?> > > >???? > 2) Windows Server 2019 running on ESXi 7.0 on Intel Xeon Gold 6230R on > Dell > >? ? ?PowerEdge > >? ? ?> > R740 (Platform type: Windows, x86_64, build+test, vs2017) > >? ? ?> > > >???? > > >? ? ?> > > >???? > Please provide the credentials and instruction on setting up the buildbot > >? ? ?worker. > >? ? ?> > > >???? > > >? ? ?> > > >???? > Thanks, > >? ? ?> > > >???? > Manoj > >? ? ?> > > >???? > > >? ? ?> > > >???? > > >? ? ?> > > >???? > -----Original Message----- > >? ? ?> > > >???? > From: fips-sponsors On Behalf Of > Richard > >? ? ?Levitte > >? ? ?> > > >???? > Sent: Monday, April 12, 2021 12:20 AM > >? ? ?> > > >???? > To: fips-sponsors at openssl.org > >? ? ?> > > >???? > Subject: [fips-sponsors] Buildbot workers > >? ? ?> > > >???? > > >? ? ?> > > >???? > Hi, > >? ? ?> > > >???? > > >? ? ?> > > >???? > We are finally ready to start getting buildbot worker requests. > >? ? ?> > > >???? > > >? ? ?> > > >???? > The way this will work is that we're asking you to answer a form with > details > >? ? ?for each > >? ? ?> > worker you want to set up for us, such as what platform, what architecture, and > where > >? ? ?relevant, > >? ? ?> > what toolchains are installed. > >? ? ?> > > >???? > > >? ? ?> > > >???? > The form is attached below, and include explanations for all the fields to > fill > >? ? ?in. > >? ? ?> > Please send it to buildbot-admin at openssl.org. > >? ? ?> > > >???? > > >? ? ?> > > >???? > In response, you will receive an email with the name and password we > assign your > >? ? ?> worker > >? ? ?> > (s), and instructions how to set the worker up. > >? ? ?> > > >???? > > >? ? ?> > > > > >? ? ?> > > > [2 Photon1.png ] > >? ? ?> > > > > >? ? ?> > > > [3 Photon2.png ] > >? ? ?> > > > > >? ? ?> > > > [4 Windows1.png ] > >? ? ?> > > > > >? ? ?> > > > [5 Windows2.png ] > >? ? ?> > > > > >? ? ?> > > > [6? ] > >? ? ?> > > > _______________________________________________ > >? ? ?> > > > buildbot-admin mailing list > >? ? ?> > > > buildbot-admin at openssl.org > >? ? ?> > > > > >? ? ?> > > >? ? ?> > >? ? ? > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6L9gkXe7BuoEq5B0C61BQqp%2BIbKhpQkN3SIIUlC56Vc%3D&reserved=0 > >? ? ?> > > -- > >? ? ?> > > Richard Levitte???????? levitte at openssl.org > >? ? ?> > > OpenSSL Project??????? > >? ? ?> > > >? ? ?> > >? ? ? > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=2tBYFB4HeNnmlOlbCtY3foxltY%2FjAkxw08luxL5rWr0%3D&reserved=0 > >? ? ?> > > _______________________________________________ > >? ? ?> > > buildbot-admin mailing list > >? ? ?> > > buildbot-admin at openssl.org > >? ? ?> > > > >? ? ?> > > >? ? ?> > >? ? ? > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Xg1zAuJT5GFZ2v29FvL9ouQrcfnpqoA1Zb8H69sQG%2BM%3D&reserved=0 > >? ? ?> > -- > >? ? ?> > Richard Levitte???????? levitte at openssl.org > >? ? ?> > OpenSSL Project??????? > >? ? ?> > > >? ? ?> > >? ? ? > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > >? ? ?> > > >? ? ?> > > >? ? ?> > > >? ? ?> > > >? ? ?> -- > >? ? ?> Richard Levitte???????? levitte at openssl.org > >? ? ?> OpenSSL Project???????? > >? ? ?> > >? ? ? > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > >? ? ?-- > >? ? ?Richard Levitte???????? levitte at openssl.org > >? ? ?OpenSSL Project???????? > >? ? ? > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > > > > > > [2 image001.png ] > -- > Richard Levitte? ? ? ? ?levitte at openssl.org > OpenSSL Project? ? ? ? ?http://www.openssl.org/~levitte/ > > -- Richard Levitte levitte at openssl.org OpenSSL Project http://www.openssl.org/~levitte/ From levitte at openssl.org Thu May 13 06:43:28 2021 From: levitte at openssl.org (Richard Levitte) Date: Thu, 13 May 2021 08:43:28 +0200 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org> Message-ID: <87tun7qgkv.wl-levitte@openssl.org> Hi, I've done some modifications in our buildbot configuration that should allow your buildbot worker to run more smoothly. So I tried a restart of the worker from the SSH account, and sure, it seems to work: cd Desktop\Test_buildbot buildbot-worker start . However, it seems that something's missing, because now, the buildbot log shows that 'git' is not available, see https://fips.buildbot.openssl.org/#/builders/31/builds/5/steps/1/logs/stdio So it seems that you're setting up %PATH% for running the buildbot worker, a script of some sort maybe? Cheers, Richard On Wed, 12 May 2021 13:41:22 +0200, Madhur Walia wrote: > > Hi Richard, > > We restarted buildbot-worker in Windows 2019 and it seems to be connecting now. We could see files > under Base Directory as shown below. > > We could see couple of errors related to absence of Perl and cmake in build Master Dashboard. So, > we have installed them as well. > > TableDescription automatically generated > > Yes, when you SSH, you will be connected to cmd.exe. One of the screenshots we shared had > PowerShell utility but you should be able to run the commands through cmd.exe as well. We are > using the same. > > Please let us know if you face any issues. > > Thanks & Regards, > > Madhur > > From: Richard Levitte > Date: Wednesday, 12 May 2021 at 2:08 PM > To: Madhur Walia > Cc: Richard Levitte , Sunil Kumar Yadav , Manoj > Maskara , Tim Hudson , buildbot-admin at openssl.org > , Bishakha Banerjee > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > The winserver2019 worker did show up once! At the time, you hadn't > installed the python package pywin32, but when I went in looking, it > looked like you had. However, the winserver2019 worker isn't showing > up now, could it be that it needs to be restarted? > > Do note that when we SSH to the machine, we end up with a cmd.exe > prompt. However, the images you've sent us suggest that you run from > a Mingw64 prompt, and I do not know how to get there from cmd.exe, so > it's will need instructions to do restarts for you. > > Cheers, > Richard > > Right now, it looks like you need to get the winserver2019 worker > started. I hope it's problem free at this point. > > On Fri, 07 May 2021 09:51:22 +0200, > Madhur Walia wrote: > > > > Hi Richard, > > > > We are able to connect to Buildbot Master from Windows 2019 as well now. To our surprise, > > Buildbot-worker/ Python was searching for Certificate directory in base directory. > > > > After pointing ssl-root-dir to a directory hosted in base directory, it was able to connect. > > > > Please confirm the connection. > > > > Also, What are the next steps for Photon 4 and Windows 2019 now? > > > > Thank you for your inputs. > > > > Regards, > > > > Madhur > > > > From: Madhur Walia > > Date: Thursday, 6 May 2021 at 10:04 PM > > To: Richard Levitte , Sunil Kumar Yadav > > Cc: Richard Levitte , Manoj Maskara , Tim Hudson > > , buildbot-admin at openssl.org > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > Thank you Richard. So, Photon 4.0 seems to be okay for now and next update would be from your > > development team. > > > > We captured a wireshark trace keeping default buildbot.tac and could see ?Unknown CA? error. We > > then pointed the trustroots/ ssl-root-dir to a custom path (to pem files), and encountered > another > > error which points to failure in trusting CA certificate filepath. > > > > TextDescription automatically generated > > > > We tried pointing trustroots directory to absolute certificate directory path but no luck. > > > > Other debugging steps involves, > > > > ? Running ?openssl s_client -state -debug -connect buildbot.openssl.org:9989? which > gives > > Verification: OK if we point the -CAfile to Hashed CA pem file names/ location. > > > > ? Executing, a python code to verify against CA file path, which shows a successful CA > > trust in Wireshark, > > > > import os > > > > import requests > > > > r=requests.get(' > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=l2%2FDPVWSKTnB1%2B18yyDzAOEZbjjFCIP%2BfdFdEwcX9wo%3D&reserved=0 > ',verify='C:/Certificates/a.pem') > > > > Graphical user interface, text, applicationDescription automatically generat > > > > This either seems to be a platform, (Windows) specific issue or something related to twisted OR > > something very miniscule that @Sunil Kumar Yadav and I are unable to catch. > > > > I can schedule a call to discuss this in more depth keeping in mind we are almost near to > > completion of 3~4 weeks window. > > > > Please let me know, Sunil and I are based out of India, IST time zone. We can talk during IST > > evening, Your Morning. > > > > Thanks & Regards, > > > > Madhur > > > > From: Richard Levitte > > Date: Wednesday, 5 May 2021 at 8:37 PM > > To: Madhur Walia > > Cc: Richard Levitte , Manoj Maskara , Tim Hudson > > , Sunil Kumar Yadav , buildbot-admin at openssl.org > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > As far as I can tell, The Photon 4 worker is good. The fact that > > "make test" currently fails isn't a problem with the worker as far as > > I can see... our development team will have to look at it. > > > > As for the Windows worker, it doesn't seem to connect. Have you > > verified that the two .pem files are in the directory that's specified > > in buildbot.tac? > > > > Cheers, > > Richard > > > > On Wed, 05 May 2021 12:11:46 +0200, > > Madhur Walia wrote: > > > > > > > > > Hi Richard, Tim, > > > > > > Awaiting further updates. Please assist. > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > From: Madhur Walia > > > Date: Monday, 3 May 2021 at 8:18 PM > > > To: Richard Levitte > > > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > > > , buildbot-admin at openssl.org > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > Hi Richard, > > > > > > We have installed git on Photon, please let us know next steps. > > > > > > Installed buildbot and VS2017 on Windows 2019 as shown below but the connection seems to be > > > dropping, > > > > > > Versions installed on Windows 2019, > > > > > > TextDescription automatically generated > > > > > > Win2019: Connection Failing, going in a loop, > > > > > > Graphical user interface, textDescription automatically generated > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > From: Madhur Walia > > > Date: Monday, 3 May 2021 at 2:37 PM > > > To: Richard Levitte > > > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > > > , buildbot-admin at openssl.org > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > Hi Richard, > > > > > > Thank you for the help. We had only installed buildbot-worker on Photon4 and Windows 2019. > After > > > installing Buildbot (master) on Photon4, the worker could start. > > > > > > We are now working on installing git on Photon4 and then troubleshooting Windows 2019. I will > > keep > > > you updated. > > > > > > Regards, > > > > > > Madhur > > > > > > From: Richard Levitte > > > Date: Monday, 3 May 2021 at 2:33 PM > > > To: Madhur Walia > > > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > > > , buildbot-admin at openssl.org > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > I now noticed that the Photon 4 workers have connected, so I assume > > > the 'optionsForClientTLS' is a thing of the past. > > > > > > Looking at one of the builds, > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TI%2BLbZSdaiW9wzttTf6W6Ee13y9nqGkYEppKBl2r4js%3D&reserved=0 > > > , > > > it looks like git isn't installed on the worker... > > > > > > Cheers, > > > Richard > > > > > > On Mon, 03 May 2021 10:34:57 +0200, > > > Richard Levitte wrote: > > > > > > > > On Mon, 26 Apr 2021 20:25:34 +0200, > > > > Madhur Walia wrote: > > > > > > > > > > Hi Matt, > > > > > > > > > > Thank you for the instructions. However, we are facing couple of issues while starting > > > buildbot-worker, > > > > > > > > > > For both platforms, we pointed Certificate/SSL settings to a custom directory in > > buildbot.tac > > > as per your recommendation. We also tried importing both certs, isrg-root-xi & > lets-encrypt-r3 > > to > > > trust store of OS but no luck. > > > > > > > > > > Photon, > > > > > Getting error, " builtins.NameError: name 'optionsForClientTLS' is not defined" as > > shown > > > in Photon1 screenshot attached. > > > > > Also ran a curl command to check SSL connectivity, seems to be failing, attached > > > screenshot Photon2. > > > > > > > > Please check your versions of the following packages: > > > > > > > > - buildbot (should be at least version 2.6.0) > > > > - twisted (should be at least version 17.9.0 according to buildbot > > > > 2.6.0 requirements) > > > > > > > > 'optionsForClientTLS' is a method that appeared in twisted version 14.0. > > > > > > > > > Windows, > > > > > Getting, "Unicode error" as shown in Windows1 screenshot attached. > > > > > Also ran a curl command to check SSL connectivity, seems to be failing, attached > > > screenshot Windows2. > > > > > > > > From the error message at the end of Windows1.png, you have an invalid > > > > unicode character on line 30. Could it be a character with diacritics > > > > not encoded with UTF-8? > > > > > > > > Cheers, > > > > Richard > > > > > > > > > Do you have any pointers on these errors? Please let us know. > > > > > > > > > > Thanks & Regards, > > > > > Madhur > > > > > > > > > > ------------------------------------------------------------------ > > > > > > > > > > On 21/04/21, 4:47 PM, "Matt Caswell" wrote: > > > > > > > > > > Thanks Manoj. > > > > > > > > > > To be able to set up your worker, you must use version 2.6.0 or > > > > > higher. Older version do not support TLS-protected connections. > > > > > > > > > > Please see these instructions for installing the buildbot worker > > > > > software: > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zYGoKToLms7AP%2Fefcpd9EdleLdDrnX3lotBLVxPjY3M%3D&reserved=0 > > > > > > > > > > When buildbot has been installed on the platform where the buildbot > > > > > worker is to be run, this is how a worker is created (for your PhotonOS > > > > > worker): > > > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > buildbot.openssl.org:9989 vmware-photonos40 nifs0Tweex_ > > > > > > > > > > And for your Windows server: > > > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > buildbot.openssl.org:9989 vmware-winserver2019 Efyin.Freg0 > > > > > > > > > > > > > > > where BASEDIR is determined by you. See further down for a few notes > > > > > on TLS. > > > > > > > > > > To run a buildbot worker, you do this: > > > > > > > > > > $ buildbot-worker start BASEDIR > > > > > > > > > > Apart from the software needed to run a buildbot worker, and the > > > > > utilities that are the normal part of the operating system, you also > > > > > need to ensure that the following components are available: > > > > > > > > > > - toolchains, i.e. C compiler, linker, make. If you have specified > > > > > toolchains in the worker request form, you need to ensure that all > > > > > of them are installed. > > > > > > > > > > - git > > > > > > > > > > Regarding TLS, it may be that the buildbot worker platform doesn't > > > > > have the appropriate certification verification roots set up. In that > > > > > case, you may need to apply the attached buildbot.tac patch, and store > > > > > the attached PEM files in a directory of your choice. Finish up by > > > > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with > > > > > the path of directory where you stored the PEM files. > > > > > > > > > > Matt > > > > > > > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > > > > Hi Tim & Richard, > > > > > > > > > > > > We have filled out the worker-request-form for 2 of our platforms, one unix type and > > > other Windows. Also, the platforms, for your convenience am listing here: > > > > > > > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 > > > (Platform type: Unix, x86_64, build+test, gcc) > > > > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell > PowerEdge > > > R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > > > > > > > Please provide the credentials and instruction on setting up the buildbot worker. > > > > > > > > > > > > Thanks, > > > > > > Manoj > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: fips-sponsors On Behalf Of Richard Levitte > > > > > > Sent: Monday, April 12, 2021 12:20 AM > > > > > > To: fips-sponsors at openssl.org > > > > > > Subject: [fips-sponsors] Buildbot workers > > > > > > > > > > > > Hi, > > > > > > > > > > > > We are finally ready to start getting buildbot worker requests. > > > > > > > > > > > > The way this will work is that we're asking you to answer a form with details for > each > > > worker you want to set up for us, such as what platform, what architecture, and where > relevant, > > > what toolchains are installed. > > > > > > > > > > > > The form is attached below, and include explanations for all the fields to fill in. > > > Please send it to buildbot-admin at openssl.org. > > > > > > > > > > > > In response, you will receive an email with the name and password we assign your > > worker > > > (s), and instructions how to set the worker up. > > > > > > > > > > > > > > > > [2 Photon1.png ] > > > > > > > > > > [3 Photon2.png ] > > > > > > > > > > [4 Windows1.png ] > > > > > > > > > > [5 Windows2.png ] > > > > > > > > > > [6 ] > > > > > _______________________________________________ > > > > > buildbot-admin mailing list > > > > > buildbot-admin at openssl.org > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6L9gkXe7BuoEq5B0C61BQqp%2BIbKhpQkN3SIIUlC56Vc%3D&reserved=0 > > > > -- > > > > Richard Levitte levitte at openssl.org > > > > OpenSSL Project > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=2tBYFB4HeNnmlOlbCtY3foxltY%2FjAkxw08luxL5rWr0%3D&reserved=0 > > > > _______________________________________________ > > > > buildbot-admin mailing list > > > > buildbot-admin at openssl.org > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Xg1zAuJT5GFZ2v29FvL9ouQrcfnpqoA1Zb8H69sQG%2BM%3D&reserved=0 > > > -- > > > Richard Levitte levitte at openssl.org > > > OpenSSL Project > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > > > > > > > > > > > > > > -- > > Richard Levitte levitte at openssl.org > > OpenSSL Project > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > -- > Richard Levitte levitte at openssl.org > OpenSSL Project > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > > > [2 image001.png ] -- Richard Levitte levitte at openssl.org OpenSSL Project http://www.openssl.org/~levitte/ From waliam at vmware.com Thu May 13 11:41:43 2021 From: waliam at vmware.com (Madhur Walia) Date: Thu, 13 May 2021 11:41:43 +0000 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: <87tun7qgkv.wl-levitte@openssl.org> References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org>,<87tun7qgkv.wl-levitte@openssl.org> Message-ID: Hi Richard, Not sure why you git stopped working but we have declared the path under environment variable once again and it?s seems to be working now, https://fips.buildbot.openssl.org/#/builders/31/builds/13 Thanks & Regards, Madhur From: Richard Levitte Date: Thursday, 13 May 2021 at 12:13 PM To: Madhur Walia Cc: Richard Levitte , Sunil Kumar Yadav , Manoj Maskara , Tim Hudson , buildbot-admin at openssl.org , Bishakha Banerjee Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers Hi, I've done some modifications in our buildbot configuration that should allow your buildbot worker to run more smoothly. So I tried a restart of the worker from the SSH account, and sure, it seems to work: cd Desktop\Test_buildbot buildbot-worker start . However, it seems that something's missing, because now, the buildbot log shows that 'git' is not available, see https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F5%2Fsteps%2F1%2Flogs%2Fstdio&data=04%7C01%7Cwaliam%40vmware.com%7C1ceacd7244174bc1205808d915da6cf8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564850167341372%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=KpoWimBMrfSDFeJ2sPBUjNS170sJAM7PyjwH99ltkEo%3D&reserved=0 So it seems that you're setting up %PATH% for running the buildbot worker, a script of some sort maybe? Cheers, Richard On Wed, 12 May 2021 13:41:22 +0200, Madhur Walia wrote: > > Hi Richard, > > We restarted buildbot-worker in Windows 2019 and it seems to be connecting now. We could see files > under Base Directory as shown below. > > We could see couple of errors related to absence of Perl and cmake in build Master Dashboard. So, > we have installed them as well. > > TableDescription automatically generated > > Yes, when you SSH, you will be connected to cmd.exe. One of the screenshots we shared had > PowerShell utility but you should be able to run the commands through cmd.exe as well. We are > using the same. > > Please let us know if you face any issues. > > Thanks & Regards, > > Madhur > > From: Richard Levitte > Date: Wednesday, 12 May 2021 at 2:08 PM > To: Madhur Walia > Cc: Richard Levitte , Sunil Kumar Yadav , Manoj > Maskara , Tim Hudson , buildbot-admin at openssl.org > , Bishakha Banerjee > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > The winserver2019 worker did show up once! At the time, you hadn't > installed the python package pywin32, but when I went in looking, it > looked like you had. However, the winserver2019 worker isn't showing > up now, could it be that it needs to be restarted? > > Do note that when we SSH to the machine, we end up with a cmd.exe > prompt. However, the images you've sent us suggest that you run from > a Mingw64 prompt, and I do not know how to get there from cmd.exe, so > it's will need instructions to do restarts for you. > > Cheers, > Richard > > Right now, it looks like you need to get the winserver2019 worker > started. I hope it's problem free at this point. > > On Fri, 07 May 2021 09:51:22 +0200, > Madhur Walia wrote: > > > > Hi Richard, > > > > We are able to connect to Buildbot Master from Windows 2019 as well now. To our surprise, > > Buildbot-worker/ Python was searching for Certificate directory in base directory. > > > > After pointing ssl-root-dir to a directory hosted in base directory, it was able to connect. > > > > Please confirm the connection. > > > > Also, What are the next steps for Photon 4 and Windows 2019 now? > > > > Thank you for your inputs. > > > > Regards, > > > > Madhur > > > > From: Madhur Walia > > Date: Thursday, 6 May 2021 at 10:04 PM > > To: Richard Levitte , Sunil Kumar Yadav > > Cc: Richard Levitte , Manoj Maskara , Tim Hudson > > , buildbot-admin at openssl.org > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > Thank you Richard. So, Photon 4.0 seems to be okay for now and next update would be from your > > development team. > > > > We captured a wireshark trace keeping default buildbot.tac and could see ?Unknown CA? error. We > > then pointed the trustroots/ ssl-root-dir to a custom path (to pem files), and encountered > another > > error which points to failure in trusting CA certificate filepath. > > > > TextDescription automatically generated > > > > We tried pointing trustroots directory to absolute certificate directory path but no luck. > > > > Other debugging steps involves, > > > > ? Running ?openssl s_client -state -debug -connect buildbot.openssl.org:9989? which > gives > > Verification: OK if we point the -CAfile to Hashed CA pem file names/ location. > > > > ? Executing, a python code to verify against CA file path, which shows a successful CA > > trust in Wireshark, > > > > import os > > > > import requests > > > > r=requests.get(' > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C1ceacd7244174bc1205808d915da6cf8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564850167341372%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qEO4AZQeTK%2BMYSGolbxRuGdz8s%2FoD5otyer%2FhL6R5r0%3D&reserved=0 > ',verify='C:/Certificates/a.pem') > > > > Graphical user interface, text, applicationDescription automatically generat > > > > This either seems to be a platform, (Windows) specific issue or something related to twisted OR > > something very miniscule that @Sunil Kumar Yadav and I are unable to catch. > > > > I can schedule a call to discuss this in more depth keeping in mind we are almost near to > > completion of 3~4 weeks window. > > > > Please let me know, Sunil and I are based out of India, IST time zone. We can talk during IST > > evening, Your Morning. > > > > Thanks & Regards, > > > > Madhur > > > > From: Richard Levitte > > Date: Wednesday, 5 May 2021 at 8:37 PM > > To: Madhur Walia > > Cc: Richard Levitte , Manoj Maskara , Tim Hudson > > , Sunil Kumar Yadav , buildbot-admin at openssl.org > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > As far as I can tell, The Photon 4 worker is good. The fact that > > "make test" currently fails isn't a problem with the worker as far as > > I can see... our development team will have to look at it. > > > > As for the Windows worker, it doesn't seem to connect. Have you > > verified that the two .pem files are in the directory that's specified > > in buildbot.tac? > > > > Cheers, > > Richard > > > > On Wed, 05 May 2021 12:11:46 +0200, > > Madhur Walia wrote: > > > > > > > > > Hi Richard, Tim, > > > > > > Awaiting further updates. Please assist. > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > From: Madhur Walia > > > Date: Monday, 3 May 2021 at 8:18 PM > > > To: Richard Levitte > > > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > > > , buildbot-admin at openssl.org > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > Hi Richard, > > > > > > We have installed git on Photon, please let us know next steps. > > > > > > Installed buildbot and VS2017 on Windows 2019 as shown below but the connection seems to be > > > dropping, > > > > > > Versions installed on Windows 2019, > > > > > > TextDescription automatically generated > > > > > > Win2019: Connection Failing, going in a loop, > > > > > > Graphical user interface, textDescription automatically generated > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > From: Madhur Walia > > > Date: Monday, 3 May 2021 at 2:37 PM > > > To: Richard Levitte > > > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > > > , buildbot-admin at openssl.org > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > Hi Richard, > > > > > > Thank you for the help. We had only installed buildbot-worker on Photon4 and Windows 2019. > After > > > installing Buildbot (master) on Photon4, the worker could start. > > > > > > We are now working on installing git on Photon4 and then troubleshooting Windows 2019. I will > > keep > > > you updated. > > > > > > Regards, > > > > > > Madhur > > > > > > From: Richard Levitte > > > Date: Monday, 3 May 2021 at 2:33 PM > > > To: Madhur Walia > > > Cc: Manoj Maskara , Tim Hudson , Sunil Kumar Yadav > > > , buildbot-admin at openssl.org > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > I now noticed that the Photon 4 workers have connected, so I assume > > > the 'optionsForClientTLS' is a thing of the past. > > > > > > Looking at one of the builds, > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C1ceacd7244174bc1205808d915da6cf8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564850167341372%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=5JtgunnNa%2FhxWWOxrZSXfVb%2BYLu76dfgnhXFDWX1bJs%3D&reserved=0 > > > , > > > it looks like git isn't installed on the worker... > > > > > > Cheers, > > > Richard > > > > > > On Mon, 03 May 2021 10:34:57 +0200, > > > Richard Levitte wrote: > > > > > > > > On Mon, 26 Apr 2021 20:25:34 +0200, > > > > Madhur Walia wrote: > > > > > > > > > > Hi Matt, > > > > > > > > > > Thank you for the instructions. However, we are facing couple of issues while starting > > > buildbot-worker, > > > > > > > > > > For both platforms, we pointed Certificate/SSL settings to a custom directory in > > buildbot.tac > > > as per your recommendation. We also tried importing both certs, isrg-root-xi & > lets-encrypt-r3 > > to > > > trust store of OS but no luck. > > > > > > > > > > Photon, > > > > > Getting error, " builtins.NameError: name 'optionsForClientTLS' is not defined" as > > shown > > > in Photon1 screenshot attached. > > > > > Also ran a curl command to check SSL connectivity, seems to be failing, attached > > > screenshot Photon2. > > > > > > > > Please check your versions of the following packages: > > > > > > > > - buildbot (should be at least version 2.6.0) > > > > - twisted (should be at least version 17.9.0 according to buildbot > > > > 2.6.0 requirements) > > > > > > > > 'optionsForClientTLS' is a method that appeared in twisted version 14.0. > > > > > > > > > Windows, > > > > > Getting, "Unicode error" as shown in Windows1 screenshot attached. > > > > > Also ran a curl command to check SSL connectivity, seems to be failing, attached > > > screenshot Windows2. > > > > > > > > From the error message at the end of Windows1.png, you have an invalid > > > > unicode character on line 30. Could it be a character with diacritics > > > > not encoded with UTF-8? > > > > > > > > Cheers, > > > > Richard > > > > > > > > > Do you have any pointers on these errors? Please let us know. > > > > > > > > > > Thanks & Regards, > > > > > Madhur > > > > > > > > > > ------------------------------------------------------------------ > > > > > > > > > > On 21/04/21, 4:47 PM, "Matt Caswell" wrote: > > > > > > > > > > Thanks Manoj. > > > > > > > > > > To be able to set up your worker, you must use version 2.6.0 or > > > > > higher. Older version do not support TLS-protected connections. > > > > > > > > > > Please see these instructions for installing the buildbot worker > > > > > software: > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C1ceacd7244174bc1205808d915da6cf8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564850167341372%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=iRWpQWOzlE8tvhjMaXa6NijZumpNdoqDe%2BK%2F%2Fe9V9H0%3D&reserved=0 > > > > > > > > > > When buildbot has been installed on the platform where the buildbot > > > > > worker is to be run, this is how a worker is created (for your PhotonOS > > > > > worker): > > > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > buildbot.openssl.org:9989 vmware-photonos40 nifs0Tweex_ > > > > > > > > > > And for your Windows server: > > > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > buildbot.openssl.org:9989 vmware-winserver2019 Efyin.Freg0 > > > > > > > > > > > > > > > where BASEDIR is determined by you. See further down for a few notes > > > > > on TLS. > > > > > > > > > > To run a buildbot worker, you do this: > > > > > > > > > > $ buildbot-worker start BASEDIR > > > > > > > > > > Apart from the software needed to run a buildbot worker, and the > > > > > utilities that are the normal part of the operating system, you also > > > > > need to ensure that the following components are available: > > > > > > > > > > - toolchains, i.e. C compiler, linker, make. If you have specified > > > > > toolchains in the worker request form, you need to ensure that all > > > > > of them are installed. > > > > > > > > > > - git > > > > > > > > > > Regarding TLS, it may be that the buildbot worker platform doesn't > > > > > have the appropriate certification verification roots set up. In that > > > > > case, you may need to apply the attached buildbot.tac patch, and store > > > > > the attached PEM files in a directory of your choice. Finish up by > > > > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with > > > > > the path of directory where you stored the PEM files. > > > > > > > > > > Matt > > > > > > > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > > > > Hi Tim & Richard, > > > > > > > > > > > > We have filled out the worker-request-form for 2 of our platforms, one unix type and > > > other Windows. Also, the platforms, for your convenience am listing here: > > > > > > > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 > > > (Platform type: Unix, x86_64, build+test, gcc) > > > > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell > PowerEdge > > > R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > > > > > > > Please provide the credentials and instruction on setting up the buildbot worker. > > > > > > > > > > > > Thanks, > > > > > > Manoj > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: fips-sponsors On Behalf Of Richard Levitte > > > > > > Sent: Monday, April 12, 2021 12:20 AM > > > > > > To: fips-sponsors at openssl.org > > > > > > Subject: [fips-sponsors] Buildbot workers > > > > > > > > > > > > Hi, > > > > > > > > > > > > We are finally ready to start getting buildbot worker requests. > > > > > > > > > > > > The way this will work is that we're asking you to answer a form with details for > each > > > worker you want to set up for us, such as what platform, what architecture, and where > relevant, > > > what toolchains are installed. > > > > > > > > > > > > The form is attached below, and include explanations for all the fields to fill in. > > > Please send it to buildbot-admin at openssl.org. > > > > > > > > > > > > In response, you will receive an email with the name and password we assign your > > worker > > > (s), and instructions how to set the worker up. > > > > > > > > > > > > > > > > [2 Photon1.png ] > > > > > > > > > > [3 Photon2.png ] > > > > > > > > > > [4 Windows1.png ] > > > > > > > > > > [5 Windows2.png ] > > > > > > > > > > [6 ] > > > > > _______________________________________________ > > > > > buildbot-admin mailing list > > > > > buildbot-admin at openssl.org > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C1ceacd7244174bc1205808d915da6cf8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564850167341372%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=wZbiGHwHyAKZCPtAWPDlWA9%2BaltCNG%2B58YnGNbaoZNg%3D&reserved=0 > > > > -- > > > > Richard Levitte levitte at openssl.org > > > > OpenSSL Project > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C1ceacd7244174bc1205808d915da6cf8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564850167351330%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=yP1U8baTf7Q9MkuhRaT66CadXTzHos7EcxkYTfuVO1s%3D&reserved=0 > > > > _______________________________________________ > > > > buildbot-admin mailing list > > > > buildbot-admin at openssl.org > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C1ceacd7244174bc1205808d915da6cf8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564850167351330%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hDWOPC5E0UcB4hGF189cy9K4%2B9wHXIB6od0u1%2BFnJMo%3D&reserved=0 > > > -- > > > Richard Levitte levitte at openssl.org > > > OpenSSL Project > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C1ceacd7244174bc1205808d915da6cf8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564850167351330%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=yP1U8baTf7Q9MkuhRaT66CadXTzHos7EcxkYTfuVO1s%3D&reserved=0 > > > > > > > > > > > > > > -- > > Richard Levitte levitte at openssl.org > > OpenSSL Project > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C1ceacd7244174bc1205808d915da6cf8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564850167351330%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=yP1U8baTf7Q9MkuhRaT66CadXTzHos7EcxkYTfuVO1s%3D&reserved=0 > -- > Richard Levitte levitte at openssl.org > OpenSSL Project > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C1ceacd7244174bc1205808d915da6cf8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564850167351330%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=yP1U8baTf7Q9MkuhRaT66CadXTzHos7EcxkYTfuVO1s%3D&reserved=0 > > > [2 image001.png ] -- Richard Levitte levitte at openssl.org OpenSSL Project https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C1ceacd7244174bc1205808d915da6cf8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564850167351330%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=yP1U8baTf7Q9MkuhRaT66CadXTzHos7EcxkYTfuVO1s%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From waliam at vmware.com Thu May 13 13:02:16 2021 From: waliam at vmware.com (Madhur Walia) Date: Thu, 13 May 2021 13:02:16 +0000 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org> <87zgx0qrda.wl-levitte@openssl.org> , Message-ID: Hi Tim, We followed your steps and seems to be hitting an error as shown, https://fips.buildbot.openssl.org/#/builders/31/builds/13. Our buildbot-worker location in Windows is C:\Users\Administrator\Desktop\Test_buildbot. So, you will be able to see the changes in buildbot.tac and env.py script as well. Nmake output shows as, [Text Description automatically generated] Thanks & Regards, Madhur From: Tim Hudson Date: Thursday, 13 May 2021 at 7:12 AM To: Madhur Walia Cc: Richard Levitte , Sunil Kumar Yadav , Manoj Maskara , buildbot-admin at openssl.org , Bishakha Banerjee Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers You can see the current issue is that nmake isn't in the path. See https://fips.buildbot.openssl.org/#/builders/31/builds/3 You need to have that setup for the buildbot worker to actually work. i.e. logged in as the user in windows running cmd you need to have it so that "nmake" is accessible and operating correctly. Have you completed that step? There are multiple ways to set that up - and the approach I took was to run the vcvars64.bat setup script from Microsoft and then dump the environment and include setting a matching environment in buildbot.tac. You can of course copy all the environment variables into the users environment. eng at DESKTOP-75K0EME C:\buildbot\tjh-win10-1-tls>type make-env.py import os for k, v in os.environ.items(): print('os.environ[\''+str(k)+'\']=\''+str(v).replace('\\','\\\\')+'\'') I run that script (in a window that has had vcvars64.bat run) and changed into the buildbot worker directory (where buildbot.tac exists) python make-env.py > env.py And I modified buildbot.tac to have: def include(filename): if os.path.exists(filename): execfile(filename) include('env.py') That is how I setup a windows based worker configuration - the one you see at https://fips.buildbot.openssl.org/#/workers/6 Tim. On Wed, May 12, 2021 at 9:41 PM Madhur Walia > wrote: Hi Richard, We restarted buildbot-worker in Windows 2019 and it seems to be connecting now. We could see files under Base Directory as shown below. We could see couple of errors related to absence of Perl and cmake in build Master Dashboard. So, we have installed them as well. [Table Description automatically generated] Yes, when you SSH, you will be connected to cmd.exe. One of the screenshots we shared had PowerShell utility but you should be able to run the commands through cmd.exe as well. We are using the same. Please let us know if you face any issues. Thanks & Regards, Madhur From: Richard Levitte > Date: Wednesday, 12 May 2021 at 2:08 PM To: Madhur Walia > Cc: Richard Levitte >, Sunil Kumar Yadav >, Manoj Maskara >, Tim Hudson >, buildbot-admin at openssl.org >, Bishakha Banerjee > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers The winserver2019 worker did show up once! At the time, you hadn't installed the python package pywin32, but when I went in looking, it looked like you had. However, the winserver2019 worker isn't showing up now, could it be that it needs to be restarted? Do note that when we SSH to the machine, we end up with a cmd.exe prompt. However, the images you've sent us suggest that you run from a Mingw64 prompt, and I do not know how to get there from cmd.exe, so it's will need instructions to do restarts for you. Cheers, Richard Right now, it looks like you need to get the winserver2019 worker started. I hope it's problem free at this point. On Fri, 07 May 2021 09:51:22 +0200, Madhur Walia wrote: > > Hi Richard, > > We are able to connect to Buildbot Master from Windows 2019 as well now. To our surprise, > Buildbot-worker/ Python was searching for Certificate directory in base directory. > > After pointing ssl-root-dir to a directory hosted in base directory, it was able to connect. > > Please confirm the connection. > > Also, What are the next steps for Photon 4 and Windows 2019 now? > > Thank you for your inputs. > > Regards, > > Madhur > > From: Madhur Walia > > Date: Thursday, 6 May 2021 at 10:04 PM > To: Richard Levitte >, Sunil Kumar Yadav > > Cc: Richard Levitte >, Manoj Maskara >, Tim Hudson > >, buildbot-admin at openssl.org > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > Thank you Richard. So, Photon 4.0 seems to be okay for now and next update would be from your > development team. > > We captured a wireshark trace keeping default buildbot.tac and could see ?Unknown CA? error. We > then pointed the trustroots/ ssl-root-dir to a custom path (to pem files), and encountered another > error which points to failure in trusting CA certificate filepath. > > TextDescription automatically generated > > We tried pointing trustroots directory to absolute certificate directory path but no luck. > > Other debugging steps involves, > > ? Running ?openssl s_client -state -debug -connect buildbot.openssl.org:9989? which gives > Verification: OK if we point the -CAfile to Hashed CA pem file names/ location. > > ? Executing, a python code to verify against CA file path, which shows a successful CA > trust in Wireshark, > > import os > > import requests > > r=requests.get('https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=l2%2FDPVWSKTnB1%2B18yyDzAOEZbjjFCIP%2BfdFdEwcX9wo%3D&reserved=0',verify='C:/Certificates/a.pem') > > Graphical user interface, text, applicationDescription automatically generat > > This either seems to be a platform, (Windows) specific issue or something related to twisted OR > something very miniscule that @Sunil Kumar Yadav and I are unable to catch. > > I can schedule a call to discuss this in more depth keeping in mind we are almost near to > completion of 3~4 weeks window. > > Please let me know, Sunil and I are based out of India, IST time zone. We can talk during IST > evening, Your Morning. > > Thanks & Regards, > > Madhur > > From: Richard Levitte > > Date: Wednesday, 5 May 2021 at 8:37 PM > To: Madhur Walia > > Cc: Richard Levitte >, Manoj Maskara >, Tim Hudson > >, Sunil Kumar Yadav >, buildbot-admin at openssl.org > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > As far as I can tell, The Photon 4 worker is good. The fact that > "make test" currently fails isn't a problem with the worker as far as > I can see... our development team will have to look at it. > > As for the Windows worker, it doesn't seem to connect. Have you > verified that the two .pem files are in the directory that's specified > in buildbot.tac? > > Cheers, > Richard > > On Wed, 05 May 2021 12:11:46 +0200, > Madhur Walia wrote: > > > > > > Hi Richard, Tim, > > > > Awaiting further updates. Please assist. > > > > Thanks & Regards, > > > > Madhur > > > > From: Madhur Walia > > > Date: Monday, 3 May 2021 at 8:18 PM > > To: Richard Levitte > > > Cc: Manoj Maskara >, Tim Hudson >, Sunil Kumar Yadav > > >, buildbot-admin at openssl.org > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > Hi Richard, > > > > We have installed git on Photon, please let us know next steps. > > > > Installed buildbot and VS2017 on Windows 2019 as shown below but the connection seems to be > > dropping, > > > > Versions installed on Windows 2019, > > > > TextDescription automatically generated > > > > Win2019: Connection Failing, going in a loop, > > > > Graphical user interface, textDescription automatically generated > > > > Thanks & Regards, > > > > Madhur > > > > From: Madhur Walia > > > Date: Monday, 3 May 2021 at 2:37 PM > > To: Richard Levitte > > > Cc: Manoj Maskara >, Tim Hudson >, Sunil Kumar Yadav > > >, buildbot-admin at openssl.org > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > Hi Richard, > > > > Thank you for the help. We had only installed buildbot-worker on Photon4 and Windows 2019. After > > installing Buildbot (master) on Photon4, the worker could start. > > > > We are now working on installing git on Photon4 and then troubleshooting Windows 2019. I will > keep > > you updated. > > > > Regards, > > > > Madhur > > > > From: Richard Levitte > > > Date: Monday, 3 May 2021 at 2:33 PM > > To: Madhur Walia > > > Cc: Manoj Maskara >, Tim Hudson >, Sunil Kumar Yadav > > >, buildbot-admin at openssl.org > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > I now noticed that the Photon 4 workers have connected, so I assume > > the 'optionsForClientTLS' is a thing of the past. > > > > Looking at one of the builds, > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TI%2BLbZSdaiW9wzttTf6W6Ee13y9nqGkYEppKBl2r4js%3D&reserved=0 > > , > > it looks like git isn't installed on the worker... > > > > Cheers, > > Richard > > > > On Mon, 03 May 2021 10:34:57 +0200, > > Richard Levitte wrote: > > > > > > On Mon, 26 Apr 2021 20:25:34 +0200, > > > Madhur Walia wrote: > > > > > > > > Hi Matt, > > > > > > > > Thank you for the instructions. However, we are facing couple of issues while starting > > buildbot-worker, > > > > > > > > For both platforms, we pointed Certificate/SSL settings to a custom directory in > buildbot.tac > > as per your recommendation. We also tried importing both certs, isrg-root-xi & lets-encrypt-r3 > to > > trust store of OS but no luck. > > > > > > > > Photon, > > > > Getting error, " builtins.NameError: name 'optionsForClientTLS' is not defined" as > shown > > in Photon1 screenshot attached. > > > > Also ran a curl command to check SSL connectivity, seems to be failing, attached > > screenshot Photon2. > > > > > > Please check your versions of the following packages: > > > > > > - buildbot (should be at least version 2.6.0) > > > - twisted (should be at least version 17.9.0 according to buildbot > > > 2.6.0 requirements) > > > > > > 'optionsForClientTLS' is a method that appeared in twisted version 14.0. > > > > > > > Windows, > > > > Getting, "Unicode error" as shown in Windows1 screenshot attached. > > > > Also ran a curl command to check SSL connectivity, seems to be failing, attached > > screenshot Windows2. > > > > > > From the error message at the end of Windows1.png, you have an invalid > > > unicode character on line 30. Could it be a character with diacritics > > > not encoded with UTF-8? > > > > > > Cheers, > > > Richard > > > > > > > Do you have any pointers on these errors? Please let us know. > > > > > > > > Thanks & Regards, > > > > Madhur > > > > > > > > ------------------------------------------------------------------ > > > > > > > > On 21/04/21, 4:47 PM, "Matt Caswell" > wrote: > > > > > > > > Thanks Manoj. > > > > > > > > To be able to set up your worker, you must use version 2.6.0 or > > > > higher. Older version do not support TLS-protected connections. > > > > > > > > Please see these instructions for installing the buildbot worker > > > > software: > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zYGoKToLms7AP%2Fefcpd9EdleLdDrnX3lotBLVxPjY3M%3D&reserved=0 > > > > > > > > When buildbot has been installed on the platform where the buildbot > > > > worker is to be run, this is how a worker is created (for your PhotonOS > > > > worker): > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > buildbot.openssl.org:9989 vmware-photonos40 nifs0Tweex_ > > > > > > > > And for your Windows server: > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > buildbot.openssl.org:9989 vmware-winserver2019 Efyin.Freg0 > > > > > > > > > > > > where BASEDIR is determined by you. See further down for a few notes > > > > on TLS. > > > > > > > > To run a buildbot worker, you do this: > > > > > > > > $ buildbot-worker start BASEDIR > > > > > > > > Apart from the software needed to run a buildbot worker, and the > > > > utilities that are the normal part of the operating system, you also > > > > need to ensure that the following components are available: > > > > > > > > - toolchains, i.e. C compiler, linker, make. If you have specified > > > > toolchains in the worker request form, you need to ensure that all > > > > of them are installed. > > > > > > > > - git > > > > > > > > Regarding TLS, it may be that the buildbot worker platform doesn't > > > > have the appropriate certification verification roots set up. In that > > > > case, you may need to apply the attached buildbot.tac patch, and store > > > > the attached PEM files in a directory of your choice. Finish up by > > > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with > > > > the path of directory where you stored the PEM files. > > > > > > > > Matt > > > > > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > > > Hi Tim & Richard, > > > > > > > > > > We have filled out the worker-request-form for 2 of our platforms, one unix type and > > other Windows. Also, the platforms, for your convenience am listing here: > > > > > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge R740 > > (Platform type: Unix, x86_64, build+test, gcc) > > > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel Xeon Gold 6230R on Dell PowerEdge > > R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > > > > > Please provide the credentials and instruction on setting up the buildbot worker. > > > > > > > > > > Thanks, > > > > > Manoj > > > > > > > > > > > > > > > -----Original Message----- > > > > > From: fips-sponsors > On Behalf Of Richard Levitte > > > > > Sent: Monday, April 12, 2021 12:20 AM > > > > > To: fips-sponsors at openssl.org > > > > > Subject: [fips-sponsors] Buildbot workers > > > > > > > > > > Hi, > > > > > > > > > > We are finally ready to start getting buildbot worker requests. > > > > > > > > > > The way this will work is that we're asking you to answer a form with details for each > > worker you want to set up for us, such as what platform, what architecture, and where relevant, > > what toolchains are installed. > > > > > > > > > > The form is attached below, and include explanations for all the fields to fill in. > > Please send it to buildbot-admin at openssl.org. > > > > > > > > > > In response, you will receive an email with the name and password we assign your > worker > > (s), and instructions how to set the worker up. > > > > > > > > > > > > > [2 Photon1.png ] > > > > > > > > [3 Photon2.png ] > > > > > > > > [4 Windows1.png ] > > > > > > > > [5 Windows2.png ] > > > > > > > > [6 ] > > > > _______________________________________________ > > > > buildbot-admin mailing list > > > > buildbot-admin at openssl.org > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6L9gkXe7BuoEq5B0C61BQqp%2BIbKhpQkN3SIIUlC56Vc%3D&reserved=0 > > > -- > > > Richard Levitte levitte at openssl.org > > > OpenSSL Project > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=2tBYFB4HeNnmlOlbCtY3foxltY%2FjAkxw08luxL5rWr0%3D&reserved=0 > > > _______________________________________________ > > > buildbot-admin mailing list > > > buildbot-admin at openssl.org > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Xg1zAuJT5GFZ2v29FvL9ouQrcfnpqoA1Zb8H69sQG%2BM%3D&reserved=0 > > -- > > Richard Levitte levitte at openssl.org > > OpenSSL Project > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > > > > > > > > > -- > Richard Levitte levitte at openssl.org > OpenSSL Project > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 -- Richard Levitte levitte at openssl.org OpenSSL Project https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 181472 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 873905 bytes Desc: image002.png URL: From matt at openssl.org Thu May 13 13:54:40 2021 From: matt at openssl.org (Matt Caswell) Date: Thu, 13 May 2021 14:54:40 +0100 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org> <87zgx0qrda.wl-levitte@openssl.org> Message-ID: <82879104-4de9-a21b-62b7-2f2f7f8f4b70@openssl.org> NASM is a pre-requisite for building OpenSSL. Have you installed it and is it on your %PATH%? https://www.nasm.us/ Matt On 13/05/2021 14:02, Madhur Walia wrote: > Hi Tim, > > We followed your steps and seems to be hitting an error as shown, > https://fips.buildbot.openssl.org/#/builders/31/builds/13 > . > > Our buildbot-worker location in Windows is > C:\Users\Administrator\Desktop\Test_buildbot. So, you will be able to > see the changes in buildbot.tac and env.py script as well. > > Nmake output shows as, > Text Description automatically generated > > Thanks & Regards, > > Madhur > > *From: *Tim Hudson > *Date: *Thursday, 13 May 2021 at 7:12 AM > *To: *Madhur Walia > *Cc: *Richard Levitte , Sunil Kumar Yadav > , Manoj Maskara , > buildbot-admin at openssl.org , Bishakha > Banerjee > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > You can see the current issue is that nmake isn't in the path. > > See https://fips.buildbot.openssl.org/#/builders/31/builds/3 > > > You need to have that setup for the buildbot worker to actually work. > > i.e. logged in as the user in windows running cmd you need to have it so > that "nmake" is accessible and operating correctly. > > Have you completed that step? > > There are multiple ways to set that up - and the approach I took was to > run the vcvars64.bat setup script from Microsoft and then dump the > environment and include setting a matching environment in buildbot.tac. > > You can of course copy all the environment variables into the users > environment. > > eng at DESKTOP-75K0EME C:\buildbot\tjh-win10-1-tls>type make-env.py > /import os > for k, v in os.environ.items(): > > print('os.environ[\''+str(k)+'\']=\''+str(v).replace('\\','\\\\')+'\'')/ > > I run that script (in a window that has had vcvars64.bat run) and > changed into the buildbot worker directory (where buildbot.tac exists) > > python make-env.py > env.py > > And I modified buildbot.tac to have: > > /def include(filename): > ? ? if os.path.exists(filename): > ? ? ? ? execfile(filename) > > include('env.py')/ > > That is how I setup a windows based worker configuration - the one you > see at https://fips.buildbot.openssl.org/#/workers/6 > > > Tim. > > On Wed, May 12, 2021 at 9:41 PM Madhur Walia > wrote: > > Hi Richard, > > We restarted buildbot-worker in Windows 2019 and it seems to be > connecting now. We could see files under Base Directory as shown below. > > We could see couple of errors related to absence of Perl and cmake > in build Master Dashboard. So, we have installed them as well. > > Table Description automatically generated > > Yes, when you SSH, you will be connected to cmd.exe. One of the > screenshots we shared had PowerShell utility but you should be able > to run the commands through cmd.exe as well. We are using the same. > > Please let us know if you face any issues. > > Thanks & Regards, > > Madhur > > *From: *Richard Levitte > > *Date: *Wednesday, 12 May 2021 at 2:08 PM > *To: *Madhur Walia > > *Cc: *Richard Levitte >, Sunil Kumar Yadav > >, Manoj > Maskara >, Tim > Hudson >, > buildbot-admin at openssl.org > >, Bishakha Banerjee > > > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > The winserver2019 worker did show up once!? At the time, you hadn't > installed the python package pywin32, but when I went in looking, it > looked like you had.? However, the winserver2019 worker isn't showing > up now, could it be that it needs to be restarted? > > Do note that when we SSH to the machine, we end up with a cmd.exe > prompt.? However, the images you've sent us suggest that you run from > a Mingw64 prompt, and I do not know how to get there from cmd.exe, so > it's will need instructions to do restarts for you. > > Cheers, > Richard > > Right now, it looks like you need to get the winserver2019 worker > started.? I hope it's problem free at this point. > > On Fri, 07 May 2021 09:51:22 +0200, > Madhur Walia wrote: > > > > Hi Richard, > > > > We are able to connect to Buildbot Master from Windows 2019 as > well now. To our surprise, > > Buildbot-worker/ Python was searching for Certificate directory > in base directory. > > > > After pointing ssl-root-dir to a directory hosted in base > directory, it was able to connect. > > > > Please confirm the connection. > > > > Also, What are the next steps for Photon 4 and Windows 2019 now? > > > > Thank you for your inputs. > > > > Regards, > > > > Madhur > > > > From: Madhur Walia > > > Date: Thursday, 6 May 2021 at 10:04 PM > > To: Richard Levitte >, Sunil Kumar Yadav > > > > Cc: Richard Levitte >, Manoj Maskara >, Tim Hudson > > >, > buildbot-admin at openssl.org > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > Thank you Richard. So, Photon 4.0 seems to be okay for now and > next update would be from your > > development team. > > > > We captured a wireshark trace keeping default buildbot.tac and > could see ?Unknown CA? error.? We > > then pointed the trustroots/ ssl-root-dir to a custom path (to > pem files), and encountered another > > error which points to failure in trusting CA certificate filepath. > > > > TextDescription automatically generated > > > > We tried pointing trustroots directory to absolute certificate > directory path but no luck. > > > > Other debugging steps involves, > > > > ????????? Running ?openssl s_client -state -debug -connect > buildbot.openssl.org:9989? which gives > > Verification: OK if we point the -CAfile to Hashed CA pem file > names/ location. > > > > ????????? Executing, a python code to verify against CA file > path, which shows a successful CA > > trust in Wireshark, > > > > import os > > > > import requests > > > > > r=requests.get('https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=l2%2FDPVWSKTnB1%2B18yyDzAOEZbjjFCIP%2BfdFdEwcX9wo%3D&reserved=0',verify='C:/Certificates/a.pem > ') > > > > Graphical user interface, text, applicationDescription > automatically generat > > > > This either seems to be a platform, (Windows) specific issue or > something related to twisted OR > > something very miniscule that @Sunil Kumar Yadav and I are unable > to catch. > > > > I can schedule a call to discuss this in more depth keeping in > mind we are almost near to > > completion of 3~4 weeks window. > > > > Please let me know, Sunil and I are based out of India, IST time > zone.? We can talk during IST > > evening, Your Morning. > > > > Thanks & Regards, > > > > Madhur > > > > From: Richard Levitte > > > Date: Wednesday, 5 May 2021 at 8:37 PM > > To: Madhur Walia > > > Cc: Richard Levitte >, Manoj Maskara >, Tim Hudson > > >, Sunil Kumar Yadav > >, > buildbot-admin at openssl.org > > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > As far as I can tell, The Photon 4 worker is good.? The fact that > > "make test" currently fails isn't a problem with the worker as far as > > I can see...? our development team will have to look at it. > > > > As for the Windows worker, it doesn't seem to connect.? Have you > > verified that the two .pem files are in the directory that's > specified > > in buildbot.tac? > > > > Cheers, > > Richard > > > > On Wed, 05 May 2021 12:11:46 +0200, > > Madhur Walia wrote: > > > > > > > > > Hi Richard, Tim, > > > > > > Awaiting further updates. Please assist. > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > From: Madhur Walia > > > > Date: Monday, 3 May 2021 at 8:18 PM > > > To: Richard Levitte > > > > Cc: Manoj Maskara >, Tim Hudson >, Sunil Kumar Yadav > > > >, > buildbot-admin at openssl.org > > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > Hi Richard, > > > > > > We have installed git on Photon, please let us know next steps. > > > > > > Installed buildbot and VS2017 on Windows 2019 as shown below > but the connection seems to be > > > dropping, > > > > > > Versions installed on Windows 2019, > > > > > > TextDescription automatically generated > > > > > > Win2019: Connection Failing, going in a loop, > > > > > > Graphical user interface, textDescription automatically generated > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > From: Madhur Walia > > > > Date: Monday, 3 May 2021 at 2:37 PM > > > To: Richard Levitte > > > > Cc: Manoj Maskara >, Tim Hudson >, Sunil Kumar Yadav > > > >, > buildbot-admin at openssl.org > > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > Hi Richard, > > > > > > Thank you for the help. We had only installed buildbot-worker > on Photon4 and Windows 2019. After > > > installing Buildbot (master) on Photon4, the worker could start. > > > > > > We are now working on installing git on Photon4 and then > troubleshooting Windows 2019. I will > > keep > > > you updated. > > > > > > Regards, > > > > > > Madhur > > > > > > From: Richard Levitte > > > > Date: Monday, 3 May 2021 at 2:33 PM > > > To: Madhur Walia > > > > Cc: Manoj Maskara >, Tim Hudson >, Sunil Kumar Yadav > > > >, > buildbot-admin at openssl.org > > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > I now noticed that the Photon 4 workers have connected, so I assume > > > the 'optionsForClientTLS' is a thing of the past. > > > > > > Looking at one of the builds, > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TI%2BLbZSdaiW9wzttTf6W6Ee13y9nqGkYEppKBl2r4js%3D&reserved=0 > > > > , > > > it looks like git isn't installed on the worker... > > > > > > Cheers, > > > Richard > > > > > > On Mon, 03 May 2021 10:34:57 +0200, > > > Richard Levitte wrote: > > > > > > > > On Mon, 26 Apr 2021 20:25:34 +0200, > > > > Madhur Walia wrote: > > > > > > > > > > Hi Matt, > > > > > > > > > > Thank you for the instructions. However, we are facing > couple of issues while starting > > > buildbot-worker, > > > > > > > > > > For both platforms, we pointed Certificate/SSL settings to > a custom directory in > > buildbot.tac > > > as per your recommendation.? We also tried importing both > certs, isrg-root-xi & lets-encrypt-r3 > > to > > > trust store of OS but no luck. > > > > > > > > > > Photon, > > > > >????? Getting error, " builtins.NameError: name > 'optionsForClientTLS' is not defined" as > > shown > > > in Photon1 screenshot attached. > > > > >????? Also ran a curl command to check SSL connectivity, > seems to be failing, attached > > > screenshot Photon2. > > > > > > > > Please check your versions of the following packages: > > > > > > > > - buildbot (should be at least version 2.6.0) > > > > - twisted (should be at least version 17.9.0 according to > buildbot > > > >?? 2.6.0 requirements) > > > > > > > > 'optionsForClientTLS' is a method that appeared in twisted > version 14.0. > > > > > > > > > Windows, > > > > >????? Getting, "Unicode error" as shown in Windows1 > screenshot attached. > > > > >????? Also ran a curl command to check SSL connectivity, > seems to be failing, attached > > > screenshot Windows2. > > > > > > > > From the error message at the end of Windows1.png, you have > an invalid > > > > unicode character on line 30.? Could it be a character with > diacritics > > > > not encoded with UTF-8? > > > > > > > > Cheers, > > > > Richard > > > > > > > > > Do you have any pointers on these errors? Please let us know. > > > > > > > > > > Thanks & Regards, > > > > > Madhur > > > > > > > > > > > ------------------------------------------------------------------ > > > > > > > > > > On 21/04/21, 4:47 PM, "Matt Caswell" > wrote: > > > > > > > > > >???? Thanks Manoj. > > > > > > > > > >???? To be able to set up your worker, you must use version > 2.6.0 or > > > > >???? higher.? Older version do not support TLS-protected > connections. > > > > > > > > > >???? Please see these instructions for installing the > buildbot worker > > > > >???? software: > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=zYGoKToLms7AP%2Fefcpd9EdleLdDrnX3lotBLVxPjY3M%3D&reserved=0 > > > > > > > > > > >???? When buildbot has been installed on the platform where > the buildbot > > > > >???? worker is to be run, this is how a worker is created > (for your PhotonOS > > > > >???? worker): > > > > > > > > > >????????? $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > buildbot.openssl.org:9989 > > vmware-photonos40 nifs0Tweex_ > > > > > > > > > >???? And for your Windows server: > > > > > > > > > >????????? $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > buildbot.openssl.org:9989 > > vmware-winserver2019 Efyin.Freg0 > > > > > > > > > > > > > > >???? where BASEDIR is determined by you.? See further down > for a few notes > > > > >???? on TLS. > > > > > > > > > >???? To run a buildbot worker, you do this: > > > > > > > > > >????????? $ buildbot-worker start BASEDIR > > > > > > > > > >???? Apart from the software needed to run a buildbot > worker, and the > > > > >???? utilities that are the normal part of the operating > system, you also > > > > >???? need to ensure that the following components are available: > > > > > > > > > >???? -?? toolchains, i.e. C compiler, linker, make.? If you > have specified > > > > >????????? toolchains in the worker request form, you need to > ensure that all > > > > >????????? of them are installed. > > > > > > > > > >???? -?? git > > > > > > > > > >???? Regarding TLS, it may be that the buildbot worker > platform doesn't > > > > >???? have the appropriate certification verification roots > set up.? In that > > > > >???? case, you may need to apply the attached buildbot.tac > patch, and store > > > > >???? the attached PEM files in a directory of your choice. > Finish up by > > > > >???? find the string '/PATH/TO/ssl-roots-dir' and replace > its contents with > > > > >???? the path of directory where you stored the PEM files. > > > > > > > > > >???? Matt > > > > > > > > > >???? On 21/04/2021 00:56, Manoj Maskara wrote: > > > > >???? > Hi Tim & Richard, > > > > >???? > > > > > >???? > We have filled out the worker-request-form for 2 of > our platforms, one unix type and > > > other Windows. Also, the platforms, for your convenience am > listing here: > > > > >???? > > > > > >???? > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon > Gold 6230R on Dell PowerEdge R740 > > > (Platform type: Unix, x86_64, build+test, gcc) > > > > >???? > 2) Windows Server 2019 running on ESXi 7.0 on Intel > Xeon Gold 6230R on Dell PowerEdge > > > R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > >???? > > > > > >???? > Please provide the credentials and instruction on > setting up the buildbot worker. > > > > >???? > > > > > >???? > Thanks, > > > > >???? > Manoj > > > > >???? > > > > > >???? > > > > > >???? > -----Original Message----- > > > > >???? > From: fips-sponsors > > On Behalf Of Richard Levitte > > > > >???? > Sent: Monday, April 12, 2021 12:20 AM > > > > >???? > To: fips-sponsors at openssl.org > > > > > >???? > Subject: [fips-sponsors] Buildbot workers > > > > >???? > > > > > >???? > Hi, > > > > >???? > > > > > >???? > We are finally ready to start getting buildbot worker > requests. > > > > >???? > > > > > >???? > The way this will work is that we're asking you to > answer a form with details for each > > > worker you want to set up for us, such as what platform, what > architecture, and where relevant, > > > what toolchains are installed. > > > > >???? > > > > > >???? > The form is attached below, and include explanations > for all the fields to fill in. > > > Please send it to buildbot-admin at openssl.org > . > > > > >???? > > > > > >???? > In response, you will receive an email with the name > and password we assign your > > worker > > > (s), and instructions how to set the worker up. > > > > >???? > > > > > > > > > > > [2 Photon1.png ] > > > > > > > > > > [3 Photon2.png ] > > > > > > > > > > [4 Windows1.png ] > > > > > > > > > > [5 Windows2.png ] > > > > > > > > > > [6? ] > > > > > _______________________________________________ > > > > > buildbot-admin mailing list > > > > > buildbot-admin at openssl.org > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=6L9gkXe7BuoEq5B0C61BQqp%2BIbKhpQkN3SIIUlC56Vc%3D&reserved=0 > > > > > -- > > > > Richard Levitte levitte at openssl.org > > > > OpenSSL Project > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996001349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=2tBYFB4HeNnmlOlbCtY3foxltY%2FjAkxw08luxL5rWr0%3D&reserved=0 > > > > > _______________________________________________ > > > > buildbot-admin mailing list > > > > buildbot-admin at openssl.org > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Xg1zAuJT5GFZ2v29FvL9ouQrcfnpqoA1Zb8H69sQG%2BM%3D&reserved=0 > > > > -- > > > Richard Levitte levitte at openssl.org > > > OpenSSL Project > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > > > > > > > > > > > > > > > -- > > Richard Levitte levitte at openssl.org > > OpenSSL Project > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > > -- > Richard Levitte levitte at openssl.org > OpenSSL Project > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C79227593bd5b4fce327408d9152149ad%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637564054996011306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=lkjvsfsm0hdlZXqy4pIqF%2FNeVK22VvJZrSUw5KBruoM%3D&reserved=0 > > > > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://mta.openssl.org/mailman/listinfo/buildbot-admin > From waliam at vmware.com Thu May 13 14:11:02 2021 From: waliam at vmware.com (Madhur Walia) Date: Thu, 13 May 2021 14:11:02 +0000 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: <82879104-4de9-a21b-62b7-2f2f7f8f4b70@openssl.org> References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org> <87zgx0qrda.wl-levitte@openssl.org> , <82879104-4de9-a21b-62b7-2f2f7f8f4b70@openssl.org> Message-ID: Hi Matt, We have installed it and it?s set in %PATH% as well. Thanks & Regards, Madhur From: Matt Caswell Date: Thursday, 13 May 2021 at 7:24 PM To: Madhur Walia , Tim Hudson Cc: Sunil Kumar Yadav , buildbot-admin at openssl.org , Bishakha Banerjee , Manoj Maskara Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers NASM is a pre-requisite for building OpenSSL. Have you installed it and is it on your %PATH%? https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.nasm.us%2F&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880266295%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=xTwsWLzYrEFTdO2M3VsaK2WokPx%2BGkYYimlwM6O0SOg%3D&reserved=0 Matt On 13/05/2021 14:02, Madhur Walia wrote: > Hi Tim, > > We followed your steps and seems to be hitting an error as shown, > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F13&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880266295%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=eQiey7%2B8NWsp4r4uSSXjMvTGg9HRnFQtIL79svmp8cg%3D&reserved=0 > . > > Our buildbot-worker location in Windows is > C:\Users\Administrator\Desktop\Test_buildbot. So, you will be able to > see the changes in buildbot.tac and env.py script as well. > > Nmake output shows as, > Text Description automatically generated > > Thanks & Regards, > > Madhur > > *From: *Tim Hudson > *Date: *Thursday, 13 May 2021 at 7:12 AM > *To: *Madhur Walia > *Cc: *Richard Levitte , Sunil Kumar Yadav > , Manoj Maskara , > buildbot-admin at openssl.org , Bishakha > Banerjee > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > You can see the current issue is that nmake isn't in the path. > > See https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F3&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880266295%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=OFDBTI4ZPLbmtXAtgCQN8atNjlpQ%2FaXgQayZ%2B40K3to%3D&reserved=0 > > > You need to have that setup for the buildbot worker to actually work. > > i.e. logged in as the user in windows running cmd you need to have it so > that "nmake" is accessible and operating correctly. > > Have you completed that step? > > There are multiple ways to set that up - and the approach I took was to > run the vcvars64.bat setup script from Microsoft and then dump the > environment and include setting a matching environment in buildbot.tac. > > You can of course copy all the environment variables into the users > environment. > > eng at DESKTOP-75K0EME C:\buildbot\tjh-win10-1-tls>type make-env.py > /import os > for k, v in os.environ.items(): > > print('os.environ[\''+str(k)+'\']=\''+str(v).replace('\\','\\\\')+'\'')/ > > I run that script (in a window that has had vcvars64.bat run) and > changed into the buildbot worker directory (where buildbot.tac exists) > > python make-env.py > env.py > > And I modified buildbot.tac to have: > > /def include(filename): > if os.path.exists(filename): > execfile(filename) > > include('env.py')/ > > That is how I setup a windows based worker configuration - the one you > see at https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fworkers%2F6&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880266295%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vownepl0TobVjmX3XKdMeruWqgrIuAQYOsoHh8mS%2Bsk%3D&reserved=0 > > > Tim. > > On Wed, May 12, 2021 at 9:41 PM Madhur Walia > wrote: > > Hi Richard, > > We restarted buildbot-worker in Windows 2019 and it seems to be > connecting now. We could see files under Base Directory as shown below. > > We could see couple of errors related to absence of Perl and cmake > in build Master Dashboard. So, we have installed them as well. > > Table Description automatically generated > > Yes, when you SSH, you will be connected to cmd.exe. One of the > screenshots we shared had PowerShell utility but you should be able > to run the commands through cmd.exe as well. We are using the same. > > Please let us know if you face any issues. > > Thanks & Regards, > > Madhur > > *From: *Richard Levitte > > *Date: *Wednesday, 12 May 2021 at 2:08 PM > *To: *Madhur Walia > > *Cc: *Richard Levitte >, Sunil Kumar Yadav > >, Manoj > Maskara >, Tim > Hudson >, > buildbot-admin at openssl.org > >, Bishakha Banerjee > > > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > The winserver2019 worker did show up once! At the time, you hadn't > installed the python package pywin32, but when I went in looking, it > looked like you had. However, the winserver2019 worker isn't showing > up now, could it be that it needs to be restarted? > > Do note that when we SSH to the machine, we end up with a cmd.exe > prompt. However, the images you've sent us suggest that you run from > a Mingw64 prompt, and I do not know how to get there from cmd.exe, so > it's will need instructions to do restarts for you. > > Cheers, > Richard > > Right now, it looks like you need to get the winserver2019 worker > started. I hope it's problem free at this point. > > On Fri, 07 May 2021 09:51:22 +0200, > Madhur Walia wrote: > > > > Hi Richard, > > > > We are able to connect to Buildbot Master from Windows 2019 as > well now. To our surprise, > > Buildbot-worker/ Python was searching for Certificate directory > in base directory. > > > > After pointing ssl-root-dir to a directory hosted in base > directory, it was able to connect. > > > > Please confirm the connection. > > > > Also, What are the next steps for Photon 4 and Windows 2019 now? > > > > Thank you for your inputs. > > > > Regards, > > > > Madhur > > > > From: Madhur Walia > > > Date: Thursday, 6 May 2021 at 10:04 PM > > To: Richard Levitte >, Sunil Kumar Yadav > > > > Cc: Richard Levitte >, Manoj Maskara >, Tim Hudson > > >, > buildbot-admin at openssl.org > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > Thank you Richard. So, Photon 4.0 seems to be okay for now and > next update would be from your > > development team. > > > > We captured a wireshark trace keeping default buildbot.tac and > could see ?Unknown CA? error. We > > then pointed the trustroots/ ssl-root-dir to a custom path (to > pem files), and encountered another > > error which points to failure in trusting CA certificate filepath. > > > > TextDescription automatically generated > > > > We tried pointing trustroots directory to absolute certificate > directory path but no luck. > > > > Other debugging steps involves, > > > > ? Running ?openssl s_client -state -debug -connect > buildbot.openssl.org:9989? which gives > > Verification: OK if we point the -CAfile to Hashed CA pem file > names/ location. > > > > ? Executing, a python code to verify against CA file > path, which shows a successful CA > > trust in Wireshark, > > > > import os > > > > import requests > > > > > r=requests.get('https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880276250%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=J6Ur3H8uEZqvxWsEhT2tP8xKFoTKWBJmqNwHkq9IQRw%3D&reserved=0 > ') > > > > Graphical user interface, text, applicationDescription > automatically generat > > > > This either seems to be a platform, (Windows) specific issue or > something related to twisted OR > > something very miniscule that @Sunil Kumar Yadav and I are unable > to catch. > > > > I can schedule a call to discuss this in more depth keeping in > mind we are almost near to > > completion of 3~4 weeks window. > > > > Please let me know, Sunil and I are based out of India, IST time > zone. We can talk during IST > > evening, Your Morning. > > > > Thanks & Regards, > > > > Madhur > > > > From: Richard Levitte > > > Date: Wednesday, 5 May 2021 at 8:37 PM > > To: Madhur Walia > > > Cc: Richard Levitte >, Manoj Maskara >, Tim Hudson > > >, Sunil Kumar Yadav > >, > buildbot-admin at openssl.org > > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > As far as I can tell, The Photon 4 worker is good. The fact that > > "make test" currently fails isn't a problem with the worker as far as > > I can see... our development team will have to look at it. > > > > As for the Windows worker, it doesn't seem to connect. Have you > > verified that the two .pem files are in the directory that's > specified > > in buildbot.tac? > > > > Cheers, > > Richard > > > > On Wed, 05 May 2021 12:11:46 +0200, > > Madhur Walia wrote: > > > > > > > > > Hi Richard, Tim, > > > > > > Awaiting further updates. Please assist. > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > From: Madhur Walia > > > > Date: Monday, 3 May 2021 at 8:18 PM > > > To: Richard Levitte > > > > Cc: Manoj Maskara >, Tim Hudson >, Sunil Kumar Yadav > > > >, > buildbot-admin at openssl.org > > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > Hi Richard, > > > > > > We have installed git on Photon, please let us know next steps. > > > > > > Installed buildbot and VS2017 on Windows 2019 as shown below > but the connection seems to be > > > dropping, > > > > > > Versions installed on Windows 2019, > > > > > > TextDescription automatically generated > > > > > > Win2019: Connection Failing, going in a loop, > > > > > > Graphical user interface, textDescription automatically generated > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > From: Madhur Walia > > > > Date: Monday, 3 May 2021 at 2:37 PM > > > To: Richard Levitte > > > > Cc: Manoj Maskara >, Tim Hudson >, Sunil Kumar Yadav > > > >, > buildbot-admin at openssl.org > > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > Hi Richard, > > > > > > Thank you for the help. We had only installed buildbot-worker > on Photon4 and Windows 2019. After > > > installing Buildbot (master) on Photon4, the worker could start. > > > > > > We are now working on installing git on Photon4 and then > troubleshooting Windows 2019. I will > > keep > > > you updated. > > > > > > Regards, > > > > > > Madhur > > > > > > From: Richard Levitte > > > > Date: Monday, 3 May 2021 at 2:33 PM > > > To: Madhur Walia > > > > Cc: Manoj Maskara >, Tim Hudson >, Sunil Kumar Yadav > > > >, > buildbot-admin at openssl.org > > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > I now noticed that the Photon 4 workers have connected, so I assume > > > the 'optionsForClientTLS' is a thing of the past. > > > > > > Looking at one of the builds, > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880276250%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=C%2BDojlb%2F3qOb9qaXgR%2BQz2c6Gi%2Fb7eCJUnhLiW15PAI%3D&reserved=0 > > > > , > > > it looks like git isn't installed on the worker... > > > > > > Cheers, > > > Richard > > > > > > On Mon, 03 May 2021 10:34:57 +0200, > > > Richard Levitte wrote: > > > > > > > > On Mon, 26 Apr 2021 20:25:34 +0200, > > > > Madhur Walia wrote: > > > > > > > > > > Hi Matt, > > > > > > > > > > Thank you for the instructions. However, we are facing > couple of issues while starting > > > buildbot-worker, > > > > > > > > > > For both platforms, we pointed Certificate/SSL settings to > a custom directory in > > buildbot.tac > > > as per your recommendation. We also tried importing both > certs, isrg-root-xi & lets-encrypt-r3 > > to > > > trust store of OS but no luck. > > > > > > > > > > Photon, > > > > > Getting error, " builtins.NameError: name > 'optionsForClientTLS' is not defined" as > > shown > > > in Photon1 screenshot attached. > > > > > Also ran a curl command to check SSL connectivity, > seems to be failing, attached > > > screenshot Photon2. > > > > > > > > Please check your versions of the following packages: > > > > > > > > - buildbot (should be at least version 2.6.0) > > > > - twisted (should be at least version 17.9.0 according to > buildbot > > > > 2.6.0 requirements) > > > > > > > > 'optionsForClientTLS' is a method that appeared in twisted > version 14.0. > > > > > > > > > Windows, > > > > > Getting, "Unicode error" as shown in Windows1 > screenshot attached. > > > > > Also ran a curl command to check SSL connectivity, > seems to be failing, attached > > > screenshot Windows2. > > > > > > > > From the error message at the end of Windows1.png, you have > an invalid > > > > unicode character on line 30. Could it be a character with > diacritics > > > > not encoded with UTF-8? > > > > > > > > Cheers, > > > > Richard > > > > > > > > > Do you have any pointers on these errors? Please let us know. > > > > > > > > > > Thanks & Regards, > > > > > Madhur > > > > > > > > > > > ------------------------------------------------------------------ > > > > > > > > > > On 21/04/21, 4:47 PM, "Matt Caswell" > wrote: > > > > > > > > > > Thanks Manoj. > > > > > > > > > > To be able to set up your worker, you must use version > 2.6.0 or > > > > > higher. Older version do not support TLS-protected > connections. > > > > > > > > > > Please see these instructions for installing the > buildbot worker > > > > > software: > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880276250%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=16cmxcJcPpUwHKDWYrhk%2BHSzMM2pzN6h1ZJdivAVVhM%3D&reserved=0 > > > > > > > > > > > When buildbot has been installed on the platform where > the buildbot > > > > > worker is to be run, this is how a worker is created > (for your PhotonOS > > > > > worker): > > > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > buildbot.openssl.org:9989 > > vmware-photonos40 nifs0Tweex_ > > > > > > > > > > And for your Windows server: > > > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > buildbot.openssl.org:9989 > > vmware-winserver2019 Efyin.Freg0 > > > > > > > > > > > > > > > where BASEDIR is determined by you. See further down > for a few notes > > > > > on TLS. > > > > > > > > > > To run a buildbot worker, you do this: > > > > > > > > > > $ buildbot-worker start BASEDIR > > > > > > > > > > Apart from the software needed to run a buildbot > worker, and the > > > > > utilities that are the normal part of the operating > system, you also > > > > > need to ensure that the following components are available: > > > > > > > > > > - toolchains, i.e. C compiler, linker, make. If you > have specified > > > > > toolchains in the worker request form, you need to > ensure that all > > > > > of them are installed. > > > > > > > > > > - git > > > > > > > > > > Regarding TLS, it may be that the buildbot worker > platform doesn't > > > > > have the appropriate certification verification roots > set up. In that > > > > > case, you may need to apply the attached buildbot.tac > patch, and store > > > > > the attached PEM files in a directory of your choice. > Finish up by > > > > > find the string '/PATH/TO/ssl-roots-dir' and replace > its contents with > > > > > the path of directory where you stored the PEM files. > > > > > > > > > > Matt > > > > > > > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > > > > Hi Tim & Richard, > > > > > > > > > > > > We have filled out the worker-request-form for 2 of > our platforms, one unix type and > > > other Windows. Also, the platforms, for your convenience am > listing here: > > > > > > > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon > Gold 6230R on Dell PowerEdge R740 > > > (Platform type: Unix, x86_64, build+test, gcc) > > > > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel > Xeon Gold 6230R on Dell PowerEdge > > > R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > > > > > > > Please provide the credentials and instruction on > setting up the buildbot worker. > > > > > > > > > > > > Thanks, > > > > > > Manoj > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: fips-sponsors > > On Behalf Of Richard Levitte > > > > > > Sent: Monday, April 12, 2021 12:20 AM > > > > > > To: fips-sponsors at openssl.org > > > > > > > Subject: [fips-sponsors] Buildbot workers > > > > > > > > > > > > Hi, > > > > > > > > > > > > We are finally ready to start getting buildbot worker > requests. > > > > > > > > > > > > The way this will work is that we're asking you to > answer a form with details for each > > > worker you want to set up for us, such as what platform, what > architecture, and where relevant, > > > what toolchains are installed. > > > > > > > > > > > > The form is attached below, and include explanations > for all the fields to fill in. > > > Please send it to buildbot-admin at openssl.org > . > > > > > > > > > > > > In response, you will receive an email with the name > and password we assign your > > worker > > > (s), and instructions how to set the worker up. > > > > > > > > > > > > > > > > [2 Photon1.png ] > > > > > > > > > > [3 Photon2.png ] > > > > > > > > > > [4 Windows1.png ] > > > > > > > > > > [5 Windows2.png ] > > > > > > > > > > [6 ] > > > > > _______________________________________________ > > > > > buildbot-admin mailing list > > > > > buildbot-admin at openssl.org > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880276250%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=U5fmBUjru2eq%2BFh9pLHIiXqTxkHc50l%2BBqvaY5499vk%3D&reserved=0 > > > > > -- > > > > Richard Levitte levitte at openssl.org > > > > OpenSSL Project > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880286205%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ZHzo3QNInoJ2jGIDnJ0rDxM3QK7RDzUIVZNFNI1hx3s%3D&reserved=0 > > > > > _______________________________________________ > > > > buildbot-admin mailing list > > > > buildbot-admin at openssl.org > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880286205%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=%2BNAei%2BxI2FkmScdtw7LCjiNBdyzMBKLkLSwFgiiHfTE%3D&reserved=0 > > > > -- > > > Richard Levitte levitte at openssl.org > > > OpenSSL Project > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880286205%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ZHzo3QNInoJ2jGIDnJ0rDxM3QK7RDzUIVZNFNI1hx3s%3D&reserved=0 > > > > > > > > > > > > > > > -- > > Richard Levitte levitte at openssl.org > > OpenSSL Project > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880286205%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ZHzo3QNInoJ2jGIDnJ0rDxM3QK7RDzUIVZNFNI1hx3s%3D&reserved=0 > > -- > Richard Levitte levitte at openssl.org > OpenSSL Project > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880296162%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=l1JHRrXIq95Xkpom%2B%2F7bKfnJilDFEHNhrsX6b%2Bb8sQo%3D&reserved=0 > > > > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880296162%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=QZrXDYIVw9c3sruU4udhTagkjF5PbF8uIYZYXeheWeI%3D&reserved=0 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt at openssl.org Thu May 13 15:56:55 2021 From: matt at openssl.org (Matt Caswell) Date: Thu, 13 May 2021 16:56:55 +0100 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org> <87zgx0qrda.wl-levitte@openssl.org> <82879104-4de9-a21b-62b7-2f2f7f8f4b70@openssl.org> Message-ID: <0d298536-8711-aaaf-ba7f-7c3b3419c180@openssl.org> On 13/05/2021 15:11, Madhur Walia wrote: > Hi Matt, > > We have installed it and it?s set in %PATH% as well. Hmmm. Are you sure about that? I can see that in this build: https://fips.buildbot.openssl.org/#/builders/31/builds/15 The Configure step is failing with: "NASM not found - make sure it's installed and available on %PATH%" Earlier the Configure step dumps out its %PATH%. Which shows it as: c:\users\administrator\appdata\local\programs\python\python37\lib\site-packages\pywin32_system32;C:\Perl64\bin;C:\Users\Administrator\AppData\Roaming\ActiveState\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\fips\fips_testing\bc\SW\Gradle_SW\gradle-4.10.1\bin;C:\fips\fips_testing\bc\SW\Ant_SW\apache-ant-1.10.7\bin;C:\Program Files\Java\jdk1.8.0_211\bin;C:\Program Files\dotnet\;C:\ProgramData\Microsoft\VisualStudio\Packages;C:\Program Files (x86)\Microsoft Visual Studio\2017\Community;C:\Program Files\Git;C:\Program Files\Git\bin;C:\Users\Administrator\AppData\Local\Programs\Python\Python37\Scripts\;C:\Users\Administrator\AppData\Local\Programs\Python\Python37\;C:\Users\Administrator\AppData\Local\Microsoft\WindowsApps;C:\Users\Administrator\.dotnet\tools;C:\Program Files (x86)\Microsoft Visual Studio\2017\Community;C:\ProgramData\Microsoft\VisualStudio\Packages;C:\Program Files\OpenSSL-Win64\bin;C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.13.26128\bin\;C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin;C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja; I don't see anything in that %PATH% which looks like it would hold NASM in it? Matt > > Thanks & Regards, > > Madhur > > *From: *Matt Caswell > *Date: *Thursday, 13 May 2021 at 7:24 PM > *To: *Madhur Walia , Tim Hudson > *Cc: *Sunil Kumar Yadav , > buildbot-admin at openssl.org , Bishakha > Banerjee , Manoj Maskara > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > NASM is a pre-requisite for building OpenSSL. > > Have you installed it and is it on your %PATH%? > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.nasm.us%2F&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880266295%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=xTwsWLzYrEFTdO2M3VsaK2WokPx%2BGkYYimlwM6O0SOg%3D&reserved=0 > > > Matt > > On 13/05/2021 14:02, Madhur Walia wrote: > > Hi Tim, > > > > We followed your steps and seems to be hitting an error as shown, > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F13&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880266295%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=eQiey7%2B8NWsp4r4uSSXjMvTGg9HRnFQtIL79svmp8cg%3D&reserved=0 > > > > > >. > > > > Our buildbot-worker location in Windows is > > C:\Users\Administrator\Desktop\Test_buildbot. So, you will be able to > > see the changes in buildbot.tac and env.py script as well. > > > > Nmake output shows as, > > Text Description automatically generated > > > > Thanks & Regards, > > > > Madhur > > > > *From: *Tim Hudson > > *Date: *Thursday, 13 May 2021 at 7:12 AM > > *To: *Madhur Walia > > *Cc: *Richard Levitte , Sunil Kumar Yadav > > , Manoj Maskara , > > buildbot-admin at openssl.org , Bishakha > > Banerjee > > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > You can see the current issue is that nmake isn't in the path. > > > > See > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F3&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880266295%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=OFDBTI4ZPLbmtXAtgCQN8atNjlpQ%2FaXgQayZ%2B40K3to%3D&reserved=0 > > > > > > > > > > You need to have that setup for the buildbot worker to actually work. > > > > i.e. logged in as the user in windows running cmd you need to have it so > > that "nmake" is accessible and operating correctly. > > > > Have you completed that step? > > > > There are multiple ways to set that up - and the approach I took was to > > run the vcvars64.bat setup script from Microsoft and then dump the > > environment and include setting a matching environment in buildbot.tac. > > > > You can of course copy all the environment variables into the users > > environment. > > > > eng at DESKTOP-75K0EME C:\buildbot\tjh-win10-1-tls>type make-env.py > > /import os > > for k, v in os.environ.items(): > > > > print('os.environ[\''+str(k)+'\']=\''+str(v).replace('\\','\\\\')+'\'')/ > > > > I run that script (in a window that has had vcvars64.bat run) and > > changed into the buildbot worker directory (where buildbot.tac exists) > > > > python make-env.py > env.py > > > > And I modified buildbot.tac to have: > > > > /def include(filename): > >? ? ? if os.path.exists(filename): > >? ? ? ? ? execfile(filename) > > > > include('env.py')/ > > > > That is how I setup a windows based worker configuration - the one you > > see at > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fworkers%2F6&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880266295%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vownepl0TobVjmX3XKdMeruWqgrIuAQYOsoHh8mS%2Bsk%3D&reserved=0 > > > > > > > > > > Tim. > > > > On Wed, May 12, 2021 at 9:41 PM Madhur Walia > >> wrote: > > > >???? Hi Richard, > > > >???? We restarted buildbot-worker in Windows 2019 and it seems to be > >???? connecting now. We could see files under Base Directory as shown > below. > > > >???? We could see couple of errors related to absence of Perl and cmake > >???? in build Master Dashboard. So, we have installed them as well. > > > >???? Table Description automatically generated > > > >???? Yes, when you SSH, you will be connected to cmd.exe. One of the > >???? screenshots we shared had PowerShell utility but you should be able > >???? to run the commands through cmd.exe as well. We are using the same. > > > >???? Please let us know if you face any issues. > > > >???? Thanks & Regards, > > > >???? Madhur > > > >???? *From: *Richard Levitte >???? >> > >???? *Date: *Wednesday, 12 May 2021 at 2:08 PM > >???? *To: *Madhur Walia >> > >???? *Cc: *Richard Levitte >???? >>, Sunil > Kumar Yadav > >???? >>, Manoj > >???? Maskara >>, Tim > >???? Hudson >>, > >???? buildbot-admin at openssl.org > >???? > >???? >>, Bishakha Banerjee > >???? >> > >???? *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > >???? The winserver2019 worker did show up once!? At the time, you hadn't > >???? installed the python package pywin32, but when I went in looking, it > >???? looked like you had.? However, the winserver2019 worker isn't showing > >???? up now, could it be that it needs to be restarted? > > > >???? Do note that when we SSH to the machine, we end up with a cmd.exe > >???? prompt.? However, the images you've sent us suggest that you run from > >???? a Mingw64 prompt, and I do not know how to get there from cmd.exe, so > >???? it's will need instructions to do restarts for you. > > > >???? Cheers, > >???? Richard > > > >???? Right now, it looks like you need to get the winserver2019 worker > >???? started.? I hope it's problem free at this point. > > > >???? On Fri, 07 May 2021 09:51:22 +0200, > >???? Madhur Walia wrote: > >????? > > >????? > Hi Richard, > >????? > > >????? > We are able to connect to Buildbot Master from Windows 2019 as > >???? well now. To our surprise, > >????? > Buildbot-worker/ Python was searching for Certificate directory > >???? in base directory. > >????? > > >????? > After pointing ssl-root-dir to a directory hosted in base > >???? directory, it was able to connect. > >????? > > >????? > Please confirm the connection. > >????? > > >????? > Also, What are the next steps for Photon 4 and Windows 2019 now? > >????? > > >????? > Thank you for your inputs. > >????? > > >????? > Regards, > >????? > > >????? > Madhur > >????? > > >????? > From: Madhur Walia >> > >????? > Date: Thursday, 6 May 2021 at 10:04 PM > >????? > To: Richard Levitte >???? >>, Sunil > Kumar Yadav > >???? >> > >????? > Cc: Richard Levitte >???? >>, Manoj > Maskara >???? >>, Tim > Hudson > >????? > >>, > >???? buildbot-admin at openssl.org > > >???? >> > >????? > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > >????? > > >????? > Thank you Richard. So, Photon 4.0 seems to be okay for now and > >???? next update would be from your > >????? > development team. > >????? > > >????? > We captured a wireshark trace keeping default buildbot.tac and > >???? could see ?Unknown CA? error.? We > >????? > then pointed the trustroots/ ssl-root-dir to a custom path (to > >???? pem files), and encountered another > >????? > error which points to failure in trusting CA certificate filepath. > >????? > > >????? > TextDescription automatically generated > >????? > > >????? > We tried pointing trustroots directory to absolute certificate > >???? directory path but no luck. > >????? > > >????? > Other debugging steps involves, > >????? > > >????? > ????????? Running ?openssl s_client -state -debug -connect > >???? buildbot.openssl.org:9989? which gives > >????? > Verification: OK if we point the -CAfile to Hashed CA pem file > >???? names/ location. > >????? > > >????? > ????????? Executing, a python code to verify against CA file > >???? path, which shows a successful CA > >????? > trust in Wireshark, > >????? > > >????? > import os > >????? > > >????? > import requests > >????? > > >????? > > > > r=requests.get('https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880276250%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=J6Ur3H8uEZqvxWsEhT2tP8xKFoTKWBJmqNwHkq9IQRw%3D&reserved=0 > > > >') > >????? > > >????? > Graphical user interface, text, applicationDescription > >???? automatically generat > >????? > > >????? > This either seems to be a platform, (Windows) specific issue or > >???? something related to twisted OR > >????? > something very miniscule that @Sunil Kumar Yadav and I are unable > >???? to catch. > >????? > > >????? > I can schedule a call to discuss this in more depth keeping in > >???? mind we are almost near to > >????? > completion of 3~4 weeks window. > >????? > > >????? > Please let me know, Sunil and I are based out of India, IST time > >???? zone.? We can talk during IST > >????? > evening, Your Morning. > >????? > > >????? > Thanks & Regards, > >????? > > >????? > Madhur > >????? > > >????? > From: Richard Levitte >???? >> > >????? > Date: Wednesday, 5 May 2021 at 8:37 PM > >????? > To: Madhur Walia >> > >????? > Cc: Richard Levitte >???? >>, Manoj > Maskara >???? >>, Tim > Hudson > >????? > >>, Sunil Kumar Yadav > >???? >>, > >???? buildbot-admin at openssl.org > > >????? > >> > >????? > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > >????? > > >????? > As far as I can tell, The Photon 4 worker is good.? The fact that > >????? > "make test" currently fails isn't a problem with the worker as > far as > >????? > I can see...? our development team will have to look at it. > >????? > > >????? > As for the Windows worker, it doesn't seem to connect.? Have you > >????? > verified that the two .pem files are in the directory that's > >???? specified > >????? > in buildbot.tac? > >????? > > >????? > Cheers, > >????? > Richard > >????? > > >????? > On Wed, 05 May 2021 12:11:46 +0200, > >????? > Madhur Walia wrote: > >????? > > > >????? > > > >????? > > Hi Richard, Tim, > >????? > > > >????? > > Awaiting further updates. Please assist. > >????? > > > >????? > > Thanks & Regards, > >????? > > > >????? > > Madhur > >????? > > > >????? > > From: Madhur Walia >> > >????? > > Date: Monday, 3 May 2021 at 8:18 PM > >????? > > To: Richard Levitte >???? >> > >????? > > Cc: Manoj Maskara >???? >>, Tim > Hudson >???? >>, Sunil Kumar Yadav > >????? > > >>, > >???? buildbot-admin at openssl.org > > >???? >> > >????? > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > >????? > > > >????? > > Hi Richard, > >????? > > > >????? > > We have installed git on Photon, please let us know next steps. > >????? > > > >????? > > Installed buildbot and VS2017 on Windows 2019 as shown below > >???? but the connection seems to be > >????? > > dropping, > >????? > > > >????? > > Versions installed on Windows 2019, > >????? > > > >????? > > TextDescription automatically generated > >????? > > > >????? > > Win2019: Connection Failing, going in a loop, > >????? > > > >????? > > Graphical user interface, textDescription automatically > generated > >????? > > > >????? > > Thanks & Regards, > >????? > > > >????? > > Madhur > >????? > > > >????? > > From: Madhur Walia >> > >????? > > Date: Monday, 3 May 2021 at 2:37 PM > >????? > > To: Richard Levitte >???? >> > >????? > > Cc: Manoj Maskara >???? >>, Tim > Hudson >???? >>, Sunil Kumar Yadav > >????? > > >>, > >???? buildbot-admin at openssl.org > > >???? >> > >????? > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > >????? > > > >????? > > Hi Richard, > >????? > > > >????? > > Thank you for the help. We had only installed buildbot-worker > >???? on Photon4 and Windows 2019. After > >????? > > installing Buildbot (master) on Photon4, the worker could start. > >????? > > > >????? > > We are now working on installing git on Photon4 and then > >???? troubleshooting Windows 2019. I will > >????? > keep > >????? > > you updated. > >????? > > > >????? > > Regards, > >????? > > > >????? > > Madhur > >????? > > > >????? > > From: Richard Levitte >???? >> > >????? > > Date: Monday, 3 May 2021 at 2:33 PM > >????? > > To: Madhur Walia >> > >????? > > Cc: Manoj Maskara >???? >>, Tim > Hudson >???? >>, Sunil Kumar Yadav > >????? > > >>, > >???? buildbot-admin at openssl.org > > >???? >> > >????? > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > >????? > > > >????? > > I now noticed that the Photon 4 workers have connected, so I > assume > >????? > > the 'optionsForClientTLS' is a thing of the past. > >????? > > > >????? > > Looking at one of the builds, > >????? > > > >????? > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880276250%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=C%2BDojlb%2F3qOb9qaXgR%2BQz2c6Gi%2Fb7eCJUnhLiW15PAI%3D&reserved=0 > > > > > > >????? > > , > >????? > > it looks like git isn't installed on the worker... > >????? > > > >????? > > Cheers, > >????? > > Richard > >????? > > > >????? > > On Mon, 03 May 2021 10:34:57 +0200, > >????? > > Richard Levitte wrote: > >????? > > > > >????? > > > On Mon, 26 Apr 2021 20:25:34 +0200, > >????? > > > Madhur Walia wrote: > >????? > > > > > >????? > > > > Hi Matt, > >????? > > > > > >????? > > > > Thank you for the instructions. However, we are facing > >???? couple of issues while starting > >????? > > buildbot-worker, > >????? > > > > > >????? > > > > For both platforms, we pointed Certificate/SSL settings to > >???? a custom directory in > >????? > buildbot.tac > >????? > > as per your recommendation.? We also tried importing both > >???? certs, isrg-root-xi & lets-encrypt-r3 > >????? > to > >????? > > trust store of OS but no luck. > >????? > > > > > >????? > > > > Photon, > >????? > > > >????? Getting error, " builtins.NameError: name > >???? 'optionsForClientTLS' is not defined" as > >????? > shown > >????? > > in Photon1 screenshot attached. > >????? > > > >????? Also ran a curl command to check SSL connectivity, > >???? seems to be failing, attached > >????? > > screenshot Photon2. > >????? > > > > >????? > > > Please check your versions of the following packages: > >????? > > > > >????? > > > - buildbot (should be at least version 2.6.0) > >????? > > > - twisted (should be at least version 17.9.0 according to > >???? buildbot > >????? > > >?? 2.6.0 requirements) > >????? > > > > >????? > > > 'optionsForClientTLS' is a method that appeared in twisted > >???? version 14.0. > >????? > > > > >????? > > > > Windows, > >????? > > > >????? Getting, "Unicode error" as shown in Windows1 > >???? screenshot attached. > >????? > > > >????? Also ran a curl command to check SSL connectivity, > >???? seems to be failing, attached > >????? > > screenshot Windows2. > >????? > > > > >????? > > > From the error message at the end of Windows1.png, you have > >???? an invalid > >????? > > > unicode character on line 30.? Could it be a character with > >???? diacritics > >????? > > > not encoded with UTF-8? > >????? > > > > >????? > > > Cheers, > >????? > > > Richard > >????? > > > > >????? > > > > Do you have any pointers on these errors? Please let us > know. > >????? > > > > > >????? > > > > Thanks & Regards, > >????? > > > > Madhur > >????? > > > > > >????? > > > > > >???? ------------------------------------------------------------------ > >????? > > > > > >????? > > > > On 21/04/21, 4:47 PM, "Matt Caswell" >???? >> wrote: > >????? > > > > > >????? > > > >???? Thanks Manoj. > >????? > > > > > >????? > > > >???? To be able to set up your worker, you must use version > >???? 2.6.0 or > >????? > > > >???? higher.? Older version do not support TLS-protected > >???? connections. > >????? > > > > > >????? > > > >???? Please see these instructions for installing the > >???? buildbot worker > >????? > > > >???? software: > >????? > > > > > >????? > > > > > >????? > > > >????? > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880276250%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=16cmxcJcPpUwHKDWYrhk%2BHSzMM2pzN6h1ZJdivAVVhM%3D&reserved=0 > > > > > > >????? > > > > > >????? > > > >???? When buildbot has been installed on the platform where > >???? the buildbot > >????? > > > >???? worker is to be run, this is how a worker is created > >???? (for your PhotonOS > >????? > > > >???? worker): > >????? > > > > > >????? > > > >????????? $ buildbot-worker create-worker --use-tls BASEDIR \ > >????? > > > > buildbot.openssl.org:9989 > > > > > >???? vmware-photonos40 nifs0Tweex_ > >????? > > > > > >????? > > > >???? And for your Windows server: > >????? > > > > > >????? > > > >????????? $ buildbot-worker create-worker --use-tls BASEDIR \ > >????? > > > > buildbot.openssl.org:9989 > > > > > >???? vmware-winserver2019 Efyin.Freg0 > >????? > > > > > >????? > > > > > >????? > > > >???? where BASEDIR is determined by you.? See further down > >???? for a few notes > >????? > > > >???? on TLS. > >????? > > > > > >????? > > > >???? To run a buildbot worker, you do this: > >????? > > > > > >????? > > > >????????? $ buildbot-worker start BASEDIR > >????? > > > > > >????? > > > >???? Apart from the software needed to run a buildbot > >???? worker, and the > >????? > > > >???? utilities that are the normal part of the operating > >???? system, you also > >????? > > > >???? need to ensure that the following components are > available: > >????? > > > > > >????? > > > >???? -?? toolchains, i.e. C compiler, linker, make.? If you > >???? have specified > >????? > > > >????????? toolchains in the worker request form, you need to > >???? ensure that all > >????? > > > >????????? of them are installed. > >????? > > > > > >????? > > > >???? -?? git > >????? > > > > > >????? > > > >???? Regarding TLS, it may be that the buildbot worker > >???? platform doesn't > >????? > > > >???? have the appropriate certification verification roots > >???? set up.? In that > >????? > > > >???? case, you may need to apply the attached buildbot.tac > >???? patch, and store > >????? > > > >???? the attached PEM files in a directory of your choice. > >???? Finish up by > >????? > > > >???? find the string '/PATH/TO/ssl-roots-dir' and replace > >???? its contents with > >????? > > > >???? the path of directory where you stored the PEM files. > >????? > > > > > >????? > > > >???? Matt > >????? > > > > > >????? > > > >???? On 21/04/2021 00:56, Manoj Maskara wrote: > >????? > > > >???? > Hi Tim & Richard, > >????? > > > >???? > > >????? > > > >???? > We have filled out the worker-request-form for 2 of > >???? our platforms, one unix type and > >????? > > other Windows. Also, the platforms, for your convenience am > >???? listing here: > >????? > > > >???? > > >????? > > > >???? > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon > >???? Gold 6230R on Dell PowerEdge R740 > >????? > > (Platform type: Unix, x86_64, build+test, gcc) > >????? > > > >???? > 2) Windows Server 2019 running on ESXi 7.0 on Intel > >???? Xeon Gold 6230R on Dell PowerEdge > >????? > > R740 (Platform type: Windows, x86_64, build+test, vs2017) > >????? > > > >???? > > >????? > > > >???? > Please provide the credentials and instruction on > >???? setting up the buildbot worker. > >????? > > > >???? > > >????? > > > >???? > Thanks, > >????? > > > >???? > Manoj > >????? > > > >???? > > >????? > > > >???? > > >????? > > > >???? > -----Original Message----- > >????? > > > >???? > From: fips-sponsors > >???? >???? >> On Behalf Of Richard Levitte > >????? > > > >???? > Sent: Monday, April 12, 2021 12:20 AM > >????? > > > >???? > To: fips-sponsors at openssl.org > >???? > > >????? > > > >???? > Subject: [fips-sponsors] Buildbot workers > >????? > > > >???? > > >????? > > > >???? > Hi, > >????? > > > >???? > > >????? > > > >???? > We are finally ready to start getting buildbot worker > >???? requests. > >????? > > > >???? > > >????? > > > >???? > The way this will work is that we're asking you to > >???? answer a form with details for each > >????? > > worker you want to set up for us, such as what platform, what > >???? architecture, and where relevant, > >????? > > what toolchains are installed. > >????? > > > >???? > > >????? > > > >???? > The form is attached below, and include explanations > >???? for all the fields to fill in. > >????? > > Please send it to buildbot-admin at openssl.org > >???? >. > >????? > > > >???? > > >????? > > > >???? > In response, you will receive an email with the name > >???? and password we assign your > >????? > worker > >????? > > (s), and instructions how to set the worker up. > >????? > > > >???? > > >????? > > > > > >????? > > > > [2 Photon1.png ] > >????? > > > > > >????? > > > > [3 Photon2.png ] > >????? > > > > > >????? > > > > [4 Windows1.png ] > >????? > > > > > >????? > > > > [5 Windows2.png ] > >????? > > > > > >????? > > > > [6? ] > >????? > > > > _______________________________________________ > >????? > > > > buildbot-admin mailing list > >????? > > > > buildbot-admin at openssl.org > > > >????? > > > > > >????? > > > >????? > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880276250%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=U5fmBUjru2eq%2BFh9pLHIiXqTxkHc50l%2BBqvaY5499vk%3D&reserved=0 > > > > > > >????? > > > -- > >????? > > > Richard Levitte levitte at openssl.org > > > >????? > > > OpenSSL Project > >????? > > > >????? > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880286205%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ZHzo3QNInoJ2jGIDnJ0rDxM3QK7RDzUIVZNFNI1hx3s%3D&reserved=0 > > > > > > >????? > > > _______________________________________________ > >????? > > > buildbot-admin mailing list > >????? > > > buildbot-admin at openssl.org > > > >????? > > > > >????? > > > >????? > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880286205%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=%2BNAei%2BxI2FkmScdtw7LCjiNBdyzMBKLkLSwFgiiHfTE%3D&reserved=0 > > > > > > >????? > > -- > >????? > > Richard Levitte levitte at openssl.org > > > >????? > > OpenSSL Project > >????? > > > >????? > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880286205%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ZHzo3QNInoJ2jGIDnJ0rDxM3QK7RDzUIVZNFNI1hx3s%3D&reserved=0 > > > > > > >????? > > > >????? > > > >????? > > > >????? > > > >????? > -- > >????? > Richard Levitte levitte at openssl.org > > > >????? > OpenSSL Project > >????? > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880286205%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ZHzo3QNInoJ2jGIDnJ0rDxM3QK7RDzUIVZNFNI1hx3s%3D&reserved=0 > > > > > >???? -- > >???? Richard Levitte levitte at openssl.org > > >???? OpenSSL Project > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880296162%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=l1JHRrXIq95Xkpom%2B%2F7bKfnJilDFEHNhrsX6b%2Bb8sQo%3D&reserved=0 > > > > > > > > > > > _______________________________________________ > > buildbot-admin mailing list > > buildbot-admin at openssl.org > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C54cfbdbaf6f741f618f808d91616a9f8%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565108880296162%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=QZrXDYIVw9c3sruU4udhTagkjF5PbF8uIYZYXeheWeI%3D&reserved=0 > > > > From waliam at vmware.com Thu May 13 16:16:47 2021 From: waliam at vmware.com (Madhur Walia) Date: Thu, 13 May 2021 16:16:47 +0000 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: <0d298536-8711-aaaf-ba7f-7c3b3419c180@openssl.org> References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org> <87zgx0qrda.wl-levitte@openssl.org> <82879104-4de9-a21b-62b7-2f2f7f8f4b70@openssl.org> , <0d298536-8711-aaaf-ba7f-7c3b3419c180@openssl.org> Message-ID: Hi Matt, Yes, we installed it after you emailed us which means after the test you?re referring to. New test should be able to pick up NASM Path, Screenshot from Windows 2019, [Graphical user interface, text Description automatically generated] Thanks & Regards, Madhur From: Matt Caswell Date: Thursday, 13 May 2021 at 9:27 PM To: Madhur Walia , Tim Hudson Cc: Sunil Kumar Yadav , buildbot-admin at openssl.org , Bishakha Banerjee , Manoj Maskara Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers On 13/05/2021 15:11, Madhur Walia wrote: > Hi Matt, > > We have installed it and it?s set in %PATH% as well. Hmmm. Are you sure about that? I can see that in this build: https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F15&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238167299%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=RY8%2Fa%2BnoI5vPN6thYgqszpDwmcxgzRZ9QKnQyXrZnA0%3D&reserved=0 The Configure step is failing with: "NASM not found - make sure it's installed and available on %PATH%" Earlier the Configure step dumps out its %PATH%. Which shows it as: c:\users\administrator\appdata\local\programs\python\python37\lib\site-packages\pywin32_system32;C:\Perl64\bin;C:\Users\Administrator\AppData\Roaming\ActiveState\bin;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\fips\fips_testing\bc\SW\Gradle_SW\gradle-4.10.1\bin;C:\fips\fips_testing\bc\SW\Ant_SW\apache-ant-1.10.7\bin;C:\Program Files\Java\jdk1.8.0_211\bin;C:\Program Files\dotnet\;C:\ProgramData\Microsoft\VisualStudio\Packages;C:\Program Files (x86)\Microsoft Visual Studio\2017\Community;C:\Program Files\Git;C:\Program Files\Git\bin;C:\Users\Administrator\AppData\Local\Programs\Python\Python37\Scripts\;C:\Users\Administrator\AppData\Local\Programs\Python\Python37\;C:\Users\Administrator\AppData\Local\Microsoft\WindowsApps;C:\Users\Administrator\.dotnet\tools;C:\Program Files (x86)\Microsoft Visual Studio\2017\Community;C:\ProgramData\Microsoft\VisualStudio\Packages;C:\Program Files\OpenSSL-Win64\bin;C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.13.26128\bin\;C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin;C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja; I don't see anything in that %PATH% which looks like it would hold NASM in it? Matt > > Thanks & Regards, > > Madhur > > *From: *Matt Caswell > *Date: *Thursday, 13 May 2021 at 7:24 PM > *To: *Madhur Walia , Tim Hudson > *Cc: *Sunil Kumar Yadav , > buildbot-admin at openssl.org , Bishakha > Banerjee , Manoj Maskara > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > NASM is a pre-requisite for building OpenSSL. > > Have you installed it and is it on your %PATH%? > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.nasm.us%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238167299%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Eke5MmFSCja7wrymzKooWaqLhaHQrM8exL73enH%2BVr8%3D&reserved=0 > > > Matt > > On 13/05/2021 14:02, Madhur Walia wrote: > > Hi Tim, > > > > We followed your steps and seems to be hitting an error as shown, > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F13&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238177253%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3Ap1OYxHicEljZvqDLgXDRJVFqSb6HAmBSZRzlvWu2U%3D&reserved=0 > > > > > >. > > > > Our buildbot-worker location in Windows is > > C:\Users\Administrator\Desktop\Test_buildbot. So, you will be able to > > see the changes in buildbot.tac and env.py script as well. > > > > Nmake output shows as, > > Text Description automatically generated > > > > Thanks & Regards, > > > > Madhur > > > > *From: *Tim Hudson > > *Date: *Thursday, 13 May 2021 at 7:12 AM > > *To: *Madhur Walia > > *Cc: *Richard Levitte , Sunil Kumar Yadav > > , Manoj Maskara , > > buildbot-admin at openssl.org , Bishakha > > Banerjee > > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > You can see the current issue is that nmake isn't in the path. > > > > See > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F3&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238177253%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hB0HnsNtFX0RumIdKTbAbF2kg0O6N95hsowvFLMBNIo%3D&reserved=0 > > > > > > > > > > You need to have that setup for the buildbot worker to actually work. > > > > i.e. logged in as the user in windows running cmd you need to have it so > > that "nmake" is accessible and operating correctly. > > > > Have you completed that step? > > > > There are multiple ways to set that up - and the approach I took was to > > run the vcvars64.bat setup script from Microsoft and then dump the > > environment and include setting a matching environment in buildbot.tac. > > > > You can of course copy all the environment variables into the users > > environment. > > > > eng at DESKTOP-75K0EME C:\buildbot\tjh-win10-1-tls>type make-env.py > > /import os > > for k, v in os.environ.items(): > > > > print('os.environ[\''+str(k)+'\']=\''+str(v).replace('\\','\\\\')+'\'')/ > > > > I run that script (in a window that has had vcvars64.bat run) and > > changed into the buildbot worker directory (where buildbot.tac exists) > > > > python make-env.py > env.py > > > > And I modified buildbot.tac to have: > > > > /def include(filename): > > if os.path.exists(filename): > > execfile(filename) > > > > include('env.py')/ > > > > That is how I setup a windows based worker configuration - the one you > > see at > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fworkers%2F6&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238187210%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3wU3r8xyhhpbwAb361QDL0s5p77Yqb%2BLAUj3p4IOG%2BI%3D&reserved=0 > > > > > > > > > > Tim. > > > > On Wed, May 12, 2021 at 9:41 PM Madhur Walia > >> wrote: > > > > Hi Richard, > > > > We restarted buildbot-worker in Windows 2019 and it seems to be > > connecting now. We could see files under Base Directory as shown > below. > > > > We could see couple of errors related to absence of Perl and cmake > > in build Master Dashboard. So, we have installed them as well. > > > > Table Description automatically generated > > > > Yes, when you SSH, you will be connected to cmd.exe. One of the > > screenshots we shared had PowerShell utility but you should be able > > to run the commands through cmd.exe as well. We are using the same. > > > > Please let us know if you face any issues. > > > > Thanks & Regards, > > > > Madhur > > > > *From: *Richard Levitte > >> > > *Date: *Wednesday, 12 May 2021 at 2:08 PM > > *To: *Madhur Walia >> > > *Cc: *Richard Levitte > >>, Sunil > Kumar Yadav > > >>, Manoj > > Maskara >>, Tim > > Hudson >>, > > buildbot-admin at openssl.org > > > > >>, Bishakha Banerjee > > >> > > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > The winserver2019 worker did show up once! At the time, you hadn't > > installed the python package pywin32, but when I went in looking, it > > looked like you had. However, the winserver2019 worker isn't showing > > up now, could it be that it needs to be restarted? > > > > Do note that when we SSH to the machine, we end up with a cmd.exe > > prompt. However, the images you've sent us suggest that you run from > > a Mingw64 prompt, and I do not know how to get there from cmd.exe, so > > it's will need instructions to do restarts for you. > > > > Cheers, > > Richard > > > > Right now, it looks like you need to get the winserver2019 worker > > started. I hope it's problem free at this point. > > > > On Fri, 07 May 2021 09:51:22 +0200, > > Madhur Walia wrote: > > > > > > Hi Richard, > > > > > > We are able to connect to Buildbot Master from Windows 2019 as > > well now. To our surprise, > > > Buildbot-worker/ Python was searching for Certificate directory > > in base directory. > > > > > > After pointing ssl-root-dir to a directory hosted in base > > directory, it was able to connect. > > > > > > Please confirm the connection. > > > > > > Also, What are the next steps for Photon 4 and Windows 2019 now? > > > > > > Thank you for your inputs. > > > > > > Regards, > > > > > > Madhur > > > > > > From: Madhur Walia >> > > > Date: Thursday, 6 May 2021 at 10:04 PM > > > To: Richard Levitte > >>, Sunil > Kumar Yadav > > >> > > > Cc: Richard Levitte > >>, Manoj > Maskara > >>, Tim > Hudson > > > >>, > > buildbot-admin at openssl.org > > > >> > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > Thank you Richard. So, Photon 4.0 seems to be okay for now and > > next update would be from your > > > development team. > > > > > > We captured a wireshark trace keeping default buildbot.tac and > > could see ?Unknown CA? error. We > > > then pointed the trustroots/ ssl-root-dir to a custom path (to > > pem files), and encountered another > > > error which points to failure in trusting CA certificate filepath. > > > > > > TextDescription automatically generated > > > > > > We tried pointing trustroots directory to absolute certificate > > directory path but no luck. > > > > > > Other debugging steps involves, > > > > > > ? Running ?openssl s_client -state -debug -connect > > buildbot.openssl.org:9989? which gives > > > Verification: OK if we point the -CAfile to Hashed CA pem file > > names/ location. > > > > > > ? Executing, a python code to verify against CA file > > path, which shows a successful CA > > > trust in Wireshark, > > > > > > import os > > > > > > import requests > > > > > > > > > r=requests.get('https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238187210%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=1Kw8uRtRgMbPdat598X%2FZ0tZXULtsoXZZEiY6fDSO6c%3D&reserved=0 > > > >') > > > > > > Graphical user interface, text, applicationDescription > > automatically generat > > > > > > This either seems to be a platform, (Windows) specific issue or > > something related to twisted OR > > > something very miniscule that @Sunil Kumar Yadav and I are unable > > to catch. > > > > > > I can schedule a call to discuss this in more depth keeping in > > mind we are almost near to > > > completion of 3~4 weeks window. > > > > > > Please let me know, Sunil and I are based out of India, IST time > > zone. We can talk during IST > > > evening, Your Morning. > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > From: Richard Levitte > >> > > > Date: Wednesday, 5 May 2021 at 8:37 PM > > > To: Madhur Walia >> > > > Cc: Richard Levitte > >>, Manoj > Maskara > >>, Tim > Hudson > > > >>, Sunil Kumar Yadav > > >>, > > buildbot-admin at openssl.org > > > > >> > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > As far as I can tell, The Photon 4 worker is good. The fact that > > > "make test" currently fails isn't a problem with the worker as > far as > > > I can see... our development team will have to look at it. > > > > > > As for the Windows worker, it doesn't seem to connect. Have you > > > verified that the two .pem files are in the directory that's > > specified > > > in buildbot.tac? > > > > > > Cheers, > > > Richard > > > > > > On Wed, 05 May 2021 12:11:46 +0200, > > > Madhur Walia wrote: > > > > > > > > > > > > Hi Richard, Tim, > > > > > > > > Awaiting further updates. Please assist. > > > > > > > > Thanks & Regards, > > > > > > > > Madhur > > > > > > > > From: Madhur Walia >> > > > > Date: Monday, 3 May 2021 at 8:18 PM > > > > To: Richard Levitte > >> > > > > Cc: Manoj Maskara > >>, Tim > Hudson > >>, Sunil Kumar Yadav > > > > >>, > > buildbot-admin at openssl.org > > > >> > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > Hi Richard, > > > > > > > > We have installed git on Photon, please let us know next steps. > > > > > > > > Installed buildbot and VS2017 on Windows 2019 as shown below > > but the connection seems to be > > > > dropping, > > > > > > > > Versions installed on Windows 2019, > > > > > > > > TextDescription automatically generated > > > > > > > > Win2019: Connection Failing, going in a loop, > > > > > > > > Graphical user interface, textDescription automatically > generated > > > > > > > > Thanks & Regards, > > > > > > > > Madhur > > > > > > > > From: Madhur Walia >> > > > > Date: Monday, 3 May 2021 at 2:37 PM > > > > To: Richard Levitte > >> > > > > Cc: Manoj Maskara > >>, Tim > Hudson > >>, Sunil Kumar Yadav > > > > >>, > > buildbot-admin at openssl.org > > > >> > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > Hi Richard, > > > > > > > > Thank you for the help. We had only installed buildbot-worker > > on Photon4 and Windows 2019. After > > > > installing Buildbot (master) on Photon4, the worker could start. > > > > > > > > We are now working on installing git on Photon4 and then > > troubleshooting Windows 2019. I will > > > keep > > > > you updated. > > > > > > > > Regards, > > > > > > > > Madhur > > > > > > > > From: Richard Levitte > >> > > > > Date: Monday, 3 May 2021 at 2:33 PM > > > > To: Madhur Walia >> > > > > Cc: Manoj Maskara > >>, Tim > Hudson > >>, Sunil Kumar Yadav > > > > >>, > > buildbot-admin at openssl.org > > > >> > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > I now noticed that the Photon 4 workers have connected, so I > assume > > > > the 'optionsForClientTLS' is a thing of the past. > > > > > > > > Looking at one of the builds, > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238187210%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=SIXYdAx1Lm%2Bpaw9UPENgK3vhw%2BvFS0xDKau82r4BpsU%3D&reserved=0 > > > > > > > > > , > > > > it looks like git isn't installed on the worker... > > > > > > > > Cheers, > > > > Richard > > > > > > > > On Mon, 03 May 2021 10:34:57 +0200, > > > > Richard Levitte wrote: > > > > > > > > > > On Mon, 26 Apr 2021 20:25:34 +0200, > > > > > Madhur Walia wrote: > > > > > > > > > > > > Hi Matt, > > > > > > > > > > > > Thank you for the instructions. However, we are facing > > couple of issues while starting > > > > buildbot-worker, > > > > > > > > > > > > For both platforms, we pointed Certificate/SSL settings to > > a custom directory in > > > buildbot.tac > > > > as per your recommendation. We also tried importing both > > certs, isrg-root-xi & lets-encrypt-r3 > > > to > > > > trust store of OS but no luck. > > > > > > > > > > > > Photon, > > > > > > Getting error, " builtins.NameError: name > > 'optionsForClientTLS' is not defined" as > > > shown > > > > in Photon1 screenshot attached. > > > > > > Also ran a curl command to check SSL connectivity, > > seems to be failing, attached > > > > screenshot Photon2. > > > > > > > > > > Please check your versions of the following packages: > > > > > > > > > > - buildbot (should be at least version 2.6.0) > > > > > - twisted (should be at least version 17.9.0 according to > > buildbot > > > > > 2.6.0 requirements) > > > > > > > > > > 'optionsForClientTLS' is a method that appeared in twisted > > version 14.0. > > > > > > > > > > > Windows, > > > > > > Getting, "Unicode error" as shown in Windows1 > > screenshot attached. > > > > > > Also ran a curl command to check SSL connectivity, > > seems to be failing, attached > > > > screenshot Windows2. > > > > > > > > > > From the error message at the end of Windows1.png, you have > > an invalid > > > > > unicode character on line 30. Could it be a character with > > diacritics > > > > > not encoded with UTF-8? > > > > > > > > > > Cheers, > > > > > Richard > > > > > > > > > > > Do you have any pointers on these errors? Please let us > know. > > > > > > > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > > > > > > > > > ------------------------------------------------------------------ > > > > > > > > > > > > On 21/04/21, 4:47 PM, "Matt Caswell" > >> wrote: > > > > > > > > > > > > Thanks Manoj. > > > > > > > > > > > > To be able to set up your worker, you must use version > > 2.6.0 or > > > > > > higher. Older version do not support TLS-protected > > connections. > > > > > > > > > > > > Please see these instructions for installing the > > buildbot worker > > > > > > software: > > > > > > > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238197166%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fsCDjpeEUnRMg5eUi7kx49BIOcRZTZ6WBIC%2BKGOmgGY%3D&reserved=0 > > > > > > > > > > > > > > > > > When buildbot has been installed on the platform where > > the buildbot > > > > > > worker is to be run, this is how a worker is created > > (for your PhotonOS > > > > > > worker): > > > > > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > > buildbot.openssl.org:9989 > > > > > > vmware-photonos40 nifs0Tweex_ > > > > > > > > > > > > And for your Windows server: > > > > > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > > buildbot.openssl.org:9989 > > > > > > vmware-winserver2019 Efyin.Freg0 > > > > > > > > > > > > > > > > > > where BASEDIR is determined by you. See further down > > for a few notes > > > > > > on TLS. > > > > > > > > > > > > To run a buildbot worker, you do this: > > > > > > > > > > > > $ buildbot-worker start BASEDIR > > > > > > > > > > > > Apart from the software needed to run a buildbot > > worker, and the > > > > > > utilities that are the normal part of the operating > > system, you also > > > > > > need to ensure that the following components are > available: > > > > > > > > > > > > - toolchains, i.e. C compiler, linker, make. If you > > have specified > > > > > > toolchains in the worker request form, you need to > > ensure that all > > > > > > of them are installed. > > > > > > > > > > > > - git > > > > > > > > > > > > Regarding TLS, it may be that the buildbot worker > > platform doesn't > > > > > > have the appropriate certification verification roots > > set up. In that > > > > > > case, you may need to apply the attached buildbot.tac > > patch, and store > > > > > > the attached PEM files in a directory of your choice. > > Finish up by > > > > > > find the string '/PATH/TO/ssl-roots-dir' and replace > > its contents with > > > > > > the path of directory where you stored the PEM files. > > > > > > > > > > > > Matt > > > > > > > > > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > > > > > Hi Tim & Richard, > > > > > > > > > > > > > > We have filled out the worker-request-form for 2 of > > our platforms, one unix type and > > > > other Windows. Also, the platforms, for your convenience am > > listing here: > > > > > > > > > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon > > Gold 6230R on Dell PowerEdge R740 > > > > (Platform type: Unix, x86_64, build+test, gcc) > > > > > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel > > Xeon Gold 6230R on Dell PowerEdge > > > > R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > > > > > > > > > Please provide the credentials and instruction on > > setting up the buildbot worker. > > > > > > > > > > > > > > Thanks, > > > > > > > Manoj > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: fips-sponsors > > > >> On Behalf Of Richard Levitte > > > > > > > Sent: Monday, April 12, 2021 12:20 AM > > > > > > > To: fips-sponsors at openssl.org > > > > > > > > > > Subject: [fips-sponsors] Buildbot workers > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > We are finally ready to start getting buildbot worker > > requests. > > > > > > > > > > > > > > The way this will work is that we're asking you to > > answer a form with details for each > > > > worker you want to set up for us, such as what platform, what > > architecture, and where relevant, > > > > what toolchains are installed. > > > > > > > > > > > > > > The form is attached below, and include explanations > > for all the fields to fill in. > > > > Please send it to buildbot-admin at openssl.org > > >. > > > > > > > > > > > > > > In response, you will receive an email with the name > > and password we assign your > > > worker > > > > (s), and instructions how to set the worker up. > > > > > > > > > > > > > > > > > > > [2 Photon1.png ] > > > > > > > > > > > > [3 Photon2.png ] > > > > > > > > > > > > [4 Windows1.png ] > > > > > > > > > > > > [5 Windows2.png ] > > > > > > > > > > > > [6 ] > > > > > > _______________________________________________ > > > > > > buildbot-admin mailing list > > > > > > buildbot-admin at openssl.org > > > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238207122%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=n79%2BOk9uzGAzWHbmboXhv3T4D0HkJQWYq1n56lhmfio%3D&reserved=0 > > > > > > > > > > -- > > > > > Richard Levitte levitte at openssl.org > > > > > > > OpenSSL Project > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238207122%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=V0LgWvF5OlhhIgvtBAzW7A5GVUb2geKh1sB2g4dTT3o%3D&reserved=0 > > > > > > > > > > _______________________________________________ > > > > > buildbot-admin mailing list > > > > > buildbot-admin at openssl.org > > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238217081%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=FLUKSLfQGjB7YLj9ZLmwnX1EWKaWgPJMUKEggTPG8CY%3D&reserved=0 > > > > > > > > > -- > > > > Richard Levitte levitte at openssl.org > > > > > > OpenSSL Project > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238217081%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=52fgJwIpQ64sdlhTaaaqlTaNJtJSqMRA6nf3Fky68vg%3D&reserved=0 > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Richard Levitte levitte at openssl.org > > > > > OpenSSL Project > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238227034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=DULJN4BNF2w91KPofJyXgLMcxe8a6hmDM7%2FNf6lXKQ8%3D&reserved=0 > > > > > > -- > > Richard Levitte levitte at openssl.org > > > OpenSSL Project > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238227034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=DULJN4BNF2w91KPofJyXgLMcxe8a6hmDM7%2FNf6lXKQ8%3D&reserved=0 > > > > > > > > > > > _______________________________________________ > > buildbot-admin mailing list > > buildbot-admin at openssl.org > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238236992%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=nUM1XycQZPJoVOH%2Bt%2FoSjiXwv9o2xTmG7QSs4Jy0vTo%3D&reserved=0 > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1621288 bytes Desc: image001.png URL: From levitte at openssl.org Fri May 14 01:53:58 2021 From: levitte at openssl.org (Richard Levitte) Date: Fri, 14 May 2021 03:53:58 +0200 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org> <87zgx0qrda.wl-levitte@openssl.org> <82879104-4de9-a21b-62b7-2f2f7f8f4b70@openssl.org> Message-ID: <871raaaxmx.wl-levitte@openssl.org> I can see that you have the paths set correctly in your env.py. I can also see that you've added the lines to have it included by buildbot.tac. However, there's a slight syntax error; an extra space before the 'include' call: |def include(filename): | if os.path.exists(filename): | execfile(filename) | | include('env.py') ^ Here is the extra space That extra space makes that include call part of the function definition, because it's at the same indentation level as the 'if' statement 3 lines above. This means that the include function is never actually called. Python is an annoying language in that sense, that indentation is syntactically significant. Now, unfortuantely, I don't know of any command line text editor on Windows, so I can't safely edit buildbot.tac for you. You will have to make that change. Cheers, Richard On Thu, 13 May 2021 18:16:47 +0200, Madhur Walia wrote: > > Hi Matt, > > Yes, we installed it after you emailed us which means after the test you?re referring to. New test > should be able to pick up NASM Path, > > Screenshot from Windows 2019, > > Graphical user interface, textDescription automatically generated > > Thanks & Regards, > > Madhur > > From: Matt Caswell > Date: Thursday, 13 May 2021 at 9:27 PM > To: Madhur Walia , Tim Hudson > Cc: Sunil Kumar Yadav , buildbot-admin at openssl.org > , Bishakha Banerjee , Manoj Maskara > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > On 13/05/2021 15:11, Madhur Walia wrote: > > Hi Matt, > > > > We have installed it and it?s set in %PATH% as well. > > Hmmm. Are you sure about that? > > I can see that in this build: > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F15&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238167299%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=RY8%2Fa%2BnoI5vPN6thYgqszpDwmcxgzRZ9QKnQyXrZnA0%3D&reserved=0 > > The Configure step is failing with: > > "NASM not found - make sure it's installed and available on %PATH%" > > Earlier the Configure step dumps out its %PATH%. Which shows it as: > > c:\users\administrator\appdata\local\programs\python\python37\lib\site-packages\pywin32_system32; > C:\Perl64\bin;C:\Users\Administrator\AppData\Roaming\ActiveState\bin;C:\Program > Files (x86)\Common > Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\ > System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\fips\fips_testing\bc\SW\Gradle_SW > \gradle-4.10.1\bin;C:\fips\fips_testing\bc\SW\Ant_SW\apache-ant-1.10.7\bin;C:\Program > Files\Java\jdk1.8.0_211\bin;C:\Program > Files\dotnet\;C:\ProgramData\Microsoft\VisualStudio\Packages;C:\Program > Files (x86)\Microsoft Visual Studio\2017\Community;C:\Program > Files\Git;C:\Program > Files\Git\bin;C:\Users\Administrator\AppData\Local\Programs\Python\Python37\Scripts\;C:\Users\ > Administrator\AppData\Local\Programs\Python\Python37\;C:\Users\Administrator\AppData\Local\ > Microsoft\WindowsApps;C:\Users\Administrator\.dotnet\tools;C:\Program > Files (x86)\Microsoft Visual > Studio\2017\Community;C:\ProgramData\Microsoft\VisualStudio\Packages;C:\Program > Files\OpenSSL-Win64\bin;C:\Program Files (x86)\Microsoft Visual > Studio\2017\Community\VC\Tools\MSVC\14.13.26128\bin\;C:\Program Files > (x86)\Microsoft Visual > Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin;C:\Program > Files (x86)\Microsoft Visual > Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja; > > I don't see anything in that %PATH% which looks like it would hold NASM > in it? > > Matt > > > > > Thanks & Regards, > > > > Madhur > > > > *From: *Matt Caswell > > *Date: *Thursday, 13 May 2021 at 7:24 PM > > *To: *Madhur Walia , Tim Hudson > > *Cc: *Sunil Kumar Yadav , > > buildbot-admin at openssl.org , Bishakha > > Banerjee , Manoj Maskara > > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > NASM is a pre-requisite for building OpenSSL. > > > > Have you installed it and is it on your %PATH%? > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.nasm.us%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238167299%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Eke5MmFSCja7wrymzKooWaqLhaHQrM8exL73enH%2BVr8%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.nasm.us%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238167299%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Eke5MmFSCja7wrymzKooWaqLhaHQrM8exL73enH%2BVr8%3D&reserved=0 > > > > > > Matt > > > > On 13/05/2021 14:02, Madhur Walia wrote: > > > Hi Tim, > > > > > > We followed your steps and seems to be hitting an error as shown, > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F13&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238177253%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3Ap1OYxHicEljZvqDLgXDRJVFqSb6HAmBSZRzlvWu2U%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F13&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238177253%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3Ap1OYxHicEljZvqDLgXDRJVFqSb6HAmBSZRzlvWu2U%3D&reserved=0 > > > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F13&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238177253%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3Ap1OYxHicEljZvqDLgXDRJVFqSb6HAmBSZRzlvWu2U%3D&reserved=0 > >>. > > > > > > Our buildbot-worker location in Windows is > > > C:\Users\Administrator\Desktop\Test_buildbot. So, you will be able to > > > see the changes in buildbot.tac and env.py script as well. > > > > > > Nmake output shows as, > > > Text Description automatically generated > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > *From: *Tim Hudson > > > *Date: *Thursday, 13 May 2021 at 7:12 AM > > > *To: *Madhur Walia > > > *Cc: *Richard Levitte , Sunil Kumar Yadav > > > , Manoj Maskara , > > > buildbot-admin at openssl.org , Bishakha > > > Banerjee > > > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > You can see the current issue is that nmake isn't in the path. > > > > > > See > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F3&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238177253%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hB0HnsNtFX0RumIdKTbAbF2kg0O6N95hsowvFLMBNIo%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F3&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238177253%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hB0HnsNtFX0RumIdKTbAbF2kg0O6N95hsowvFLMBNIo%3D&reserved=0 > > > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F3&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238177253%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hB0HnsNtFX0RumIdKTbAbF2kg0O6N95hsowvFLMBNIo%3D&reserved=0 > >> > > > > > > You need to have that setup for the buildbot worker to actually work. > > > > > > i.e. logged in as the user in windows running cmd you need to have it so > > > that "nmake" is accessible and operating correctly. > > > > > > Have you completed that step? > > > > > > There are multiple ways to set that up - and the approach I took was to > > > run the vcvars64.bat setup script from Microsoft and then dump the > > > environment and include setting a matching environment in buildbot.tac. > > > > > > You can of course copy all the environment variables into the users > > > environment. > > > > > > eng at DESKTOP-75K0EME C:\buildbot\tjh-win10-1-tls>type make-env.py > > > /import os > > > for k, v in os.environ.items(): > > > > > > print('os.environ[\''+str(k)+'\']=\''+str(v).replace('\\','\\\\')+'\'')/ > > > > > > I run that script (in a window that has had vcvars64.bat run) and > > > changed into the buildbot worker directory (where buildbot.tac exists) > > > > > > python make-env.py > env.py > > > > > > And I modified buildbot.tac to have: > > > > > > /def include(filename): > > > if os.path.exists(filename): > > > execfile(filename) > > > > > > include('env.py')/ > > > > > > That is how I setup a windows based worker configuration - the one you > > > see at > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fworkers%2F6&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238187210%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3wU3r8xyhhpbwAb361QDL0s5p77Yqb%2BLAUj3p4IOG%2BI%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fworkers%2F6&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238187210%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3wU3r8xyhhpbwAb361QDL0s5p77Yqb%2BLAUj3p4IOG%2BI%3D&reserved=0 > > > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fworkers%2F6&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238187210%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3wU3r8xyhhpbwAb361QDL0s5p77Yqb%2BLAUj3p4IOG%2BI%3D&reserved=0 > >> > > > > > > Tim. > > > > > > On Wed, May 12, 2021 at 9:41 PM Madhur Walia > > >> wrote: > > > > > > Hi Richard, > > > > > > We restarted buildbot-worker in Windows 2019 and it seems to be > > > connecting now. We could see files under Base Directory as shown > > below. > > > > > > We could see couple of errors related to absence of Perl and cmake > > > in build Master Dashboard. So, we have installed them as well. > > > > > > Table Description automatically generated > > > > > > Yes, when you SSH, you will be connected to cmd.exe. One of the > > > screenshots we shared had PowerShell utility but you should be able > > > to run the commands through cmd.exe as well. We are using the same. > > > > > > Please let us know if you face any issues. > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > *From: *Richard Levitte > > >> > > > *Date: *Wednesday, 12 May 2021 at 2:08 PM > > > *To: *Madhur Walia > >> > > > *Cc: *Richard Levitte > > >>, Sunil > > Kumar Yadav > > > > >>, Manoj > > > Maskara > >>, Tim > > > Hudson > >>, > > > buildbot-admin at openssl.org > > > > > > > > >>, Bishakha Banerjee > > > > >> > > > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > The winserver2019 worker did show up once! At the time, you hadn't > > > installed the python package pywin32, but when I went in looking, it > > > looked like you had. However, the winserver2019 worker isn't showing > > > up now, could it be that it needs to be restarted? > > > > > > Do note that when we SSH to the machine, we end up with a cmd.exe > > > prompt. However, the images you've sent us suggest that you run from > > > a Mingw64 prompt, and I do not know how to get there from cmd.exe, so > > > it's will need instructions to do restarts for you. > > > > > > Cheers, > > > Richard > > > > > > Right now, it looks like you need to get the winserver2019 worker > > > started. I hope it's problem free at this point. > > > > > > On Fri, 07 May 2021 09:51:22 +0200, > > > Madhur Walia wrote: > > > > > > > > Hi Richard, > > > > > > > > We are able to connect to Buildbot Master from Windows 2019 as > > > well now. To our surprise, > > > > Buildbot-worker/ Python was searching for Certificate directory > > > in base directory. > > > > > > > > After pointing ssl-root-dir to a directory hosted in base > > > directory, it was able to connect. > > > > > > > > Please confirm the connection. > > > > > > > > Also, What are the next steps for Photon 4 and Windows 2019 now? > > > > > > > > Thank you for your inputs. > > > > > > > > Regards, > > > > > > > > Madhur > > > > > > > > From: Madhur Walia > >> > > > > Date: Thursday, 6 May 2021 at 10:04 PM > > > > To: Richard Levitte > > >>, Sunil > > Kumar Yadav > > > > >> > > > > Cc: Richard Levitte > > >>, Manoj > > Maskara > > >>, Tim > > Hudson > > > > > >>, > > > buildbot-admin at openssl.org > > > > > > >> > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > Thank you Richard. So, Photon 4.0 seems to be okay for now and > > > next update would be from your > > > > development team. > > > > > > > > We captured a wireshark trace keeping default buildbot.tac and > > > could see ?Unknown CA? error. We > > > > then pointed the trustroots/ ssl-root-dir to a custom path (to > > > pem files), and encountered another > > > > error which points to failure in trusting CA certificate filepath. > > > > > > > > TextDescription automatically generated > > > > > > > > We tried pointing trustroots directory to absolute certificate > > > directory path but no luck. > > > > > > > > Other debugging steps involves, > > > > > > > > ? Running ?openssl s_client -state -debug -connect > > > buildbot.openssl.org:9989? which gives > > > > Verification: OK if we point the -CAfile to Hashed CA pem file > > > names/ location. > > > > > > > > ? Executing, a python code to verify against CA file > > > path, which shows a successful CA > > > > trust in Wireshark, > > > > > > > > import os > > > > > > > > import requests > > > > > > > > > > > > > r=requests.get(' > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238187210%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=1Kw8uRtRgMbPdat598X%2FZ0tZXULtsoXZZEiY6fDSO6c%3D&reserved=0 > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238187210%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=1Kw8uRtRgMbPdat598X%2FZ0tZXULtsoXZZEiY6fDSO6c%3D&reserved=0 > >>') > > > > > > > > Graphical user interface, text, applicationDescription > > > automatically generat > > > > > > > > This either seems to be a platform, (Windows) specific issue or > > > something related to twisted OR > > > > something very miniscule that @Sunil Kumar Yadav and I are unable > > > to catch. > > > > > > > > I can schedule a call to discuss this in more depth keeping in > > > mind we are almost near to > > > > completion of 3~4 weeks window. > > > > > > > > Please let me know, Sunil and I are based out of India, IST time > > > zone. We can talk during IST > > > > evening, Your Morning. > > > > > > > > Thanks & Regards, > > > > > > > > Madhur > > > > > > > > From: Richard Levitte > > >> > > > > Date: Wednesday, 5 May 2021 at 8:37 PM > > > > To: Madhur Walia > >> > > > > Cc: Richard Levitte > > >>, Manoj > > Maskara > > >>, Tim > > Hudson > > > > > >>, Sunil Kumar Yadav > > > > >>, > > > buildbot-admin at openssl.org > > > > > > > >> > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > As far as I can tell, The Photon 4 worker is good. The fact that > > > > "make test" currently fails isn't a problem with the worker as > > far as > > > > I can see... our development team will have to look at it. > > > > > > > > As for the Windows worker, it doesn't seem to connect. Have you > > > > verified that the two .pem files are in the directory that's > > > specified > > > > in buildbot.tac? > > > > > > > > Cheers, > > > > Richard > > > > > > > > On Wed, 05 May 2021 12:11:46 +0200, > > > > Madhur Walia wrote: > > > > > > > > > > > > > > > Hi Richard, Tim, > > > > > > > > > > Awaiting further updates. Please assist. > > > > > > > > > > Thanks & Regards, > > > > > > > > > > Madhur > > > > > > > > > > From: Madhur Walia > >> > > > > > Date: Monday, 3 May 2021 at 8:18 PM > > > > > To: Richard Levitte > > >> > > > > > Cc: Manoj Maskara > > >>, Tim > > Hudson > > >>, Sunil Kumar Yadav > > > > > > >>, > > > buildbot-admin at openssl.org > > > > > > >> > > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > > > Hi Richard, > > > > > > > > > > We have installed git on Photon, please let us know next steps. > > > > > > > > > > Installed buildbot and VS2017 on Windows 2019 as shown below > > > but the connection seems to be > > > > > dropping, > > > > > > > > > > Versions installed on Windows 2019, > > > > > > > > > > TextDescription automatically generated > > > > > > > > > > Win2019: Connection Failing, going in a loop, > > > > > > > > > > Graphical user interface, textDescription automatically > > generated > > > > > > > > > > Thanks & Regards, > > > > > > > > > > Madhur > > > > > > > > > > From: Madhur Walia > >> > > > > > Date: Monday, 3 May 2021 at 2:37 PM > > > > > To: Richard Levitte > > >> > > > > > Cc: Manoj Maskara > > >>, Tim > > Hudson > > >>, Sunil Kumar Yadav > > > > > > >>, > > > buildbot-admin at openssl.org > > > > > > >> > > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > > > Hi Richard, > > > > > > > > > > Thank you for the help. We had only installed buildbot-worker > > > on Photon4 and Windows 2019. After > > > > > installing Buildbot (master) on Photon4, the worker could start. > > > > > > > > > > We are now working on installing git on Photon4 and then > > > troubleshooting Windows 2019. I will > > > > keep > > > > > you updated. > > > > > > > > > > Regards, > > > > > > > > > > Madhur > > > > > > > > > > From: Richard Levitte > > >> > > > > > Date: Monday, 3 May 2021 at 2:33 PM > > > > > To: Madhur Walia > >> > > > > > Cc: Manoj Maskara > > >>, Tim > > Hudson > > >>, Sunil Kumar Yadav > > > > > > >>, > > > buildbot-admin at openssl.org > > > > > > >> > > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > > > I now noticed that the Photon 4 workers have connected, so I > > assume > > > > > the 'optionsForClientTLS' is a thing of the past. > > > > > > > > > > Looking at one of the builds, > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238187210%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=SIXYdAx1Lm%2Bpaw9UPENgK3vhw%2BvFS0xDKau82r4BpsU%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238187210%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=SIXYdAx1Lm%2Bpaw9UPENgK3vhw%2BvFS0xDKau82r4BpsU%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238197166%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=FNHvIlNb6yGzZC1wtLCJU1GsPRYkX8URjnmNVbdZuLo%3D&reserved=0 > >> > > > > > , > > > > > it looks like git isn't installed on the worker... > > > > > > > > > > Cheers, > > > > > Richard > > > > > > > > > > On Mon, 03 May 2021 10:34:57 +0200, > > > > > Richard Levitte wrote: > > > > > > > > > > > > On Mon, 26 Apr 2021 20:25:34 +0200, > > > > > > Madhur Walia wrote: > > > > > > > > > > > > > > Hi Matt, > > > > > > > > > > > > > > Thank you for the instructions. However, we are facing > > > couple of issues while starting > > > > > buildbot-worker, > > > > > > > > > > > > > > For both platforms, we pointed Certificate/SSL settings to > > > a custom directory in > > > > buildbot.tac > > > > > as per your recommendation. We also tried importing both > > > certs, isrg-root-xi & lets-encrypt-r3 > > > > to > > > > > trust store of OS but no luck. > > > > > > > > > > > > > > Photon, > > > > > > > Getting error, " builtins.NameError: name > > > 'optionsForClientTLS' is not defined" as > > > > shown > > > > > in Photon1 screenshot attached. > > > > > > > Also ran a curl command to check SSL connectivity, > > > seems to be failing, attached > > > > > screenshot Photon2. > > > > > > > > > > > > Please check your versions of the following packages: > > > > > > > > > > > > - buildbot (should be at least version 2.6.0) > > > > > > - twisted (should be at least version 17.9.0 according to > > > buildbot > > > > > > 2.6.0 requirements) > > > > > > > > > > > > 'optionsForClientTLS' is a method that appeared in twisted > > > version 14.0. > > > > > > > > > > > > > Windows, > > > > > > > Getting, "Unicode error" as shown in Windows1 > > > screenshot attached. > > > > > > > Also ran a curl command to check SSL connectivity, > > > seems to be failing, attached > > > > > screenshot Windows2. > > > > > > > > > > > > From the error message at the end of Windows1.png, you have > > > an invalid > > > > > > unicode character on line 30. Could it be a character with > > > diacritics > > > > > > not encoded with UTF-8? > > > > > > > > > > > > Cheers, > > > > > > Richard > > > > > > > > > > > > > Do you have any pointers on these errors? Please let us > > know. > > > > > > > > > > > > > > Thanks & Regards, > > > > > > > Madhur > > > > > > > > > > > > > > > > > ------------------------------------------------------------------ > > > > > > > > > > > > > > On 21/04/21, 4:47 PM, "Matt Caswell" > > >> wrote: > > > > > > > > > > > > > > Thanks Manoj. > > > > > > > > > > > > > > To be able to set up your worker, you must use version > > > 2.6.0 or > > > > > > > higher. Older version do not support TLS-protected > > > connections. > > > > > > > > > > > > > > Please see these instructions for installing the > > > buildbot worker > > > > > > > software: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238197166%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fsCDjpeEUnRMg5eUi7kx49BIOcRZTZ6WBIC%2BKGOmgGY%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238197166%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fsCDjpeEUnRMg5eUi7kx49BIOcRZTZ6WBIC%2BKGOmgGY%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238197166%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fsCDjpeEUnRMg5eUi7kx49BIOcRZTZ6WBIC%2BKGOmgGY%3D&reserved=0 > >> > > > > > > > > > > > > > > When buildbot has been installed on the platform where > > > the buildbot > > > > > > > worker is to be run, this is how a worker is created > > > (for your PhotonOS > > > > > > > worker): > > > > > > > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > > > buildbot.openssl.org:9989 > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238197166%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ZcmuOOr2KPSvAWmgEZNDi9olrY2tSncwGOogjM%2BDkn8%3D&reserved=0 > >> > > > vmware-photonos40 nifs0Tweex_ > > > > > > > > > > > > > > And for your Windows server: > > > > > > > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > > > buildbot.openssl.org:9989 > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238207122%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=XoOAi4eZQq7UesQbxyW8%2BAN%2BoXXkYRaxia9AQbO7n5A%3D&reserved=0 > >> > > > vmware-winserver2019 Efyin.Freg0 > > > > > > > > > > > > > > > > > > > > > where BASEDIR is determined by you. See further down > > > for a few notes > > > > > > > on TLS. > > > > > > > > > > > > > > To run a buildbot worker, you do this: > > > > > > > > > > > > > > $ buildbot-worker start BASEDIR > > > > > > > > > > > > > > Apart from the software needed to run a buildbot > > > worker, and the > > > > > > > utilities that are the normal part of the operating > > > system, you also > > > > > > > need to ensure that the following components are > > available: > > > > > > > > > > > > > > - toolchains, i.e. C compiler, linker, make. If you > > > have specified > > > > > > > toolchains in the worker request form, you need to > > > ensure that all > > > > > > > of them are installed. > > > > > > > > > > > > > > - git > > > > > > > > > > > > > > Regarding TLS, it may be that the buildbot worker > > > platform doesn't > > > > > > > have the appropriate certification verification roots > > > set up. In that > > > > > > > case, you may need to apply the attached buildbot.tac > > > patch, and store > > > > > > > the attached PEM files in a directory of your choice. > > > Finish up by > > > > > > > find the string '/PATH/TO/ssl-roots-dir' and replace > > > its contents with > > > > > > > the path of directory where you stored the PEM files. > > > > > > > > > > > > > > Matt > > > > > > > > > > > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > > > > > > Hi Tim & Richard, > > > > > > > > > > > > > > > > We have filled out the worker-request-form for 2 of > > > our platforms, one unix type and > > > > > other Windows. Also, the platforms, for your convenience am > > > listing here: > > > > > > > > > > > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon > > > Gold 6230R on Dell PowerEdge R740 > > > > > (Platform type: Unix, x86_64, build+test, gcc) > > > > > > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel > > > Xeon Gold 6230R on Dell PowerEdge > > > > > R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > > > > > > > > > > > Please provide the credentials and instruction on > > > setting up the buildbot worker. > > > > > > > > > > > > > > > > Thanks, > > > > > > > > Manoj > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > From: fips-sponsors > > > > > > >> On Behalf Of Richard Levitte > > > > > > > > Sent: Monday, April 12, 2021 12:20 AM > > > > > > > > To: fips-sponsors at openssl.org > > > > > > > > > > > > Subject: [fips-sponsors] Buildbot workers > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > We are finally ready to start getting buildbot worker > > > requests. > > > > > > > > > > > > > > > > The way this will work is that we're asking you to > > > answer a form with details for each > > > > > worker you want to set up for us, such as what platform, what > > > architecture, and where relevant, > > > > > what toolchains are installed. > > > > > > > > > > > > > > > > The form is attached below, and include explanations > > > for all the fields to fill in. > > > > > Please send it to buildbot-admin at openssl.org > > > > >. > > > > > > > > > > > > > > > > In response, you will receive an email with the name > > > and password we assign your > > > > worker > > > > > (s), and instructions how to set the worker up. > > > > > > > > > > > > > > > > > > > > > > [2 Photon1.png ] > > > > > > > > > > > > > > [3 Photon2.png ] > > > > > > > > > > > > > > [4 Windows1.png ] > > > > > > > > > > > > > > [5 Windows2.png ] > > > > > > > > > > > > > > [6 ] > > > > > > > _______________________________________________ > > > > > > > buildbot-admin mailing list > > > > > > > buildbot-admin at openssl.org > > > > > > > > > > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238207122%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=n79%2BOk9uzGAzWHbmboXhv3T4D0HkJQWYq1n56lhmfio%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238207122%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=n79%2BOk9uzGAzWHbmboXhv3T4D0HkJQWYq1n56lhmfio%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238207122%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=n79%2BOk9uzGAzWHbmboXhv3T4D0HkJQWYq1n56lhmfio%3D&reserved=0 > >> > > > > > > -- > > > > > > Richard Levitte levitte at openssl.org > > > > > > > > > OpenSSL Project > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238207122%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=V0LgWvF5OlhhIgvtBAzW7A5GVUb2geKh1sB2g4dTT3o%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238207122%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=V0LgWvF5OlhhIgvtBAzW7A5GVUb2geKh1sB2g4dTT3o%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238217081%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=52fgJwIpQ64sdlhTaaaqlTaNJtJSqMRA6nf3Fky68vg%3D&reserved=0 > >> > > > > > > _______________________________________________ > > > > > > buildbot-admin mailing list > > > > > > buildbot-admin at openssl.org > > > > > > > > > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238217081%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=FLUKSLfQGjB7YLj9ZLmwnX1EWKaWgPJMUKEggTPG8CY%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238217081%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=FLUKSLfQGjB7YLj9ZLmwnX1EWKaWgPJMUKEggTPG8CY%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238217081%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=FLUKSLfQGjB7YLj9ZLmwnX1EWKaWgPJMUKEggTPG8CY%3D&reserved=0 > >> > > > > > -- > > > > > Richard Levitte levitte at openssl.org > > > > > > > > OpenSSL Project > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238217081%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=52fgJwIpQ64sdlhTaaaqlTaNJtJSqMRA6nf3Fky68vg%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238217081%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=52fgJwIpQ64sdlhTaaaqlTaNJtJSqMRA6nf3Fky68vg%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238227034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=DULJN4BNF2w91KPofJyXgLMcxe8a6hmDM7%2FNf6lXKQ8%3D&reserved=0 > >> > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Richard Levitte levitte at openssl.org > > > > > > > OpenSSL Project > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238227034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=DULJN4BNF2w91KPofJyXgLMcxe8a6hmDM7%2FNf6lXKQ8%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238227034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=DULJN4BNF2w91KPofJyXgLMcxe8a6hmDM7%2FNf6lXKQ8%3D&reserved=0 > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238227034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=DULJN4BNF2w91KPofJyXgLMcxe8a6hmDM7%2FNf6lXKQ8%3D&reserved=0 > > > > > -- > > > Richard Levitte levitte at openssl.org > > > > > OpenSSL Project > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238227034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=DULJN4BNF2w91KPofJyXgLMcxe8a6hmDM7%2FNf6lXKQ8%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238227034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=DULJN4BNF2w91KPofJyXgLMcxe8a6hmDM7%2FNf6lXKQ8%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238227034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=DULJN4BNF2w91KPofJyXgLMcxe8a6hmDM7%2FNf6lXKQ8%3D&reserved=0 > >> > > > > > > > > > _______________________________________________ > > > buildbot-admin mailing list > > > buildbot-admin at openssl.org > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238236992%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=nUM1XycQZPJoVOH%2Bt%2FoSjiXwv9o2xTmG7QSs4Jy0vTo%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7Ce9842d48b72446790aa808d91627bd9d%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565182238236992%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=nUM1XycQZPJoVOH%2Bt%2FoSjiXwv9o2xTmG7QSs4Jy0vTo%3D&reserved=0 > > > > > > > > > > [1.2 image001.png ] > [2 ] > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://mta.openssl.org/mailman/listinfo/buildbot-admin -- Richard Levitte levitte at openssl.org OpenSSL Project http://www.openssl.org/~levitte/ From waliam at vmware.com Fri May 14 09:32:19 2021 From: waliam at vmware.com (Madhur Walia) Date: Fri, 14 May 2021 09:32:19 +0000 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: <871raaaxmx.wl-levitte@openssl.org> References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org> <87zgx0qrda.wl-levitte@openssl.org> <82879104-4de9-a21b-62b7-2f2f7f8f4b70@openssl.org> , <871raaaxmx.wl-levitte@openssl.org> Message-ID: Hi Richard, If I set the configuration as below with correct indentation, I get an error as shown below for execfile, which in a sense means include function is successfully being called but execfile is failing, |def include(filename): | if os.path.exists(filename): | execfile(filename) | |include('env.py') Error, [Text Description automatically generated] I did some research and found that execfile function was removed in Python 3 and we are using 3.7.1. So, I used the below exec instead, which didn?t produce any execfile error. I think include and exec functions are being called now. [Graphical user interface, text, application Description automatically generated] Please let me know if this is fine. I can make the modifications you propose. Thanks & Regards, Madhur From: Richard Levitte Date: Friday, 14 May 2021 at 7:24 AM To: Madhur Walia Cc: Matt Caswell , Tim Hudson , Sunil Kumar Yadav , Manoj Maskara , Bishakha Banerjee , buildbot-admin at openssl.org Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers I can see that you have the paths set correctly in your env.py. I can also see that you've added the lines to have it included by buildbot.tac. However, there's a slight syntax error; an extra space before the 'include' call: |def include(filename): | if os.path.exists(filename): | execfile(filename) | | include('env.py') ^ Here is the extra space That extra space makes that include call part of the function definition, because it's at the same indentation level as the 'if' statement 3 lines above. This means that the include function is never actually called. Python is an annoying language in that sense, that indentation is syntactically significant. Now, unfortuantely, I don't know of any command line text editor on Windows, so I can't safely edit buildbot.tac for you. You will have to make that change. Cheers, Richard On Thu, 13 May 2021 18:16:47 +0200, Madhur Walia wrote: > > Hi Matt, > > Yes, we installed it after you emailed us which means after the test you?re referring to. New test > should be able to pick up NASM Path, > > Screenshot from Windows 2019, > > Graphical user interface, textDescription automatically generated > > Thanks & Regards, > > Madhur > > From: Matt Caswell > Date: Thursday, 13 May 2021 at 9:27 PM > To: Madhur Walia , Tim Hudson > Cc: Sunil Kumar Yadav , buildbot-admin at openssl.org > , Bishakha Banerjee , Manoj Maskara > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > On 13/05/2021 15:11, Madhur Walia wrote: > > Hi Matt, > > > > We have installed it and it?s set in %PATH% as well. > > Hmmm. Are you sure about that? > > I can see that in this build: > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F15&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538571016%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=8WKgVKhE0j13MKWM1sIy7B4PlZ4htmE9kdCMfqGju7A%3D&reserved=0 > > The Configure step is failing with: > > "NASM not found - make sure it's installed and available on %PATH%" > > Earlier the Configure step dumps out its %PATH%. Which shows it as: > > c:\users\administrator\appdata\local\programs\python\python37\lib\site-packages\pywin32_system32; > C:\Perl64\bin;C:\Users\Administrator\AppData\Roaming\ActiveState\bin;C:\Program > Files (x86)\Common > Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\ > System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\fips\fips_testing\bc\SW\Gradle_SW > \gradle-4.10.1\bin;C:\fips\fips_testing\bc\SW\Ant_SW\apache-ant-1.10.7\bin;C:\Program > Files\Java\jdk1.8.0_211\bin;C:\Program > Files\dotnet\;C:\ProgramData\Microsoft\VisualStudio\Packages;C:\Program > Files (x86)\Microsoft Visual Studio\2017\Community;C:\Program > Files\Git;C:\Program > Files\Git\bin;C:\Users\Administrator\AppData\Local\Programs\Python\Python37\Scripts\;C:\Users\ > Administrator\AppData\Local\Programs\Python\Python37\;C:\Users\Administrator\AppData\Local\ > Microsoft\WindowsApps;C:\Users\Administrator\.dotnet\tools;C:\Program > Files (x86)\Microsoft Visual > Studio\2017\Community;C:\ProgramData\Microsoft\VisualStudio\Packages;C:\Program > Files\OpenSSL-Win64\bin;C:\Program Files (x86)\Microsoft Visual > Studio\2017\Community\VC\Tools\MSVC\14.13.26128\bin\;C:\Program Files > (x86)\Microsoft Visual > Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin;C:\Program > Files (x86)\Microsoft Visual > Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja; > > I don't see anything in that %PATH% which looks like it would hold NASM > in it? > > Matt > > > > > Thanks & Regards, > > > > Madhur > > > > *From: *Matt Caswell > > *Date: *Thursday, 13 May 2021 at 7:24 PM > > *To: *Madhur Walia , Tim Hudson > > *Cc: *Sunil Kumar Yadav , > > buildbot-admin at openssl.org , Bishakha > > Banerjee , Manoj Maskara > > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > NASM is a pre-requisite for building OpenSSL. > > > > Have you installed it and is it on your %PATH%? > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.nasm.us%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538580971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=aAv6kzS2JMfvgcxbFhIgHc%2FTZpuWsjjL5huv8gKrl68%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.nasm.us%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538580971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=aAv6kzS2JMfvgcxbFhIgHc%2FTZpuWsjjL5huv8gKrl68%3D&reserved=0 > > > > > > Matt > > > > On 13/05/2021 14:02, Madhur Walia wrote: > > > Hi Tim, > > > > > > We followed your steps and seems to be hitting an error as shown, > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F13&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538580971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=X0Yl7Mnj8K5s3uZbQUeSoFtzQcBeiGjlXb1l1IHxR%2FA%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F13&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538580971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=X0Yl7Mnj8K5s3uZbQUeSoFtzQcBeiGjlXb1l1IHxR%2FA%3D&reserved=0 > > > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F13&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538580971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=X0Yl7Mnj8K5s3uZbQUeSoFtzQcBeiGjlXb1l1IHxR%2FA%3D&reserved=0 > >>. > > > > > > Our buildbot-worker location in Windows is > > > C:\Users\Administrator\Desktop\Test_buildbot. So, you will be able to > > > see the changes in buildbot.tac and env.py script as well. > > > > > > Nmake output shows as, > > > Text Description automatically generated > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > *From: *Tim Hudson > > > *Date: *Thursday, 13 May 2021 at 7:12 AM > > > *To: *Madhur Walia > > > *Cc: *Richard Levitte , Sunil Kumar Yadav > > > , Manoj Maskara , > > > buildbot-admin at openssl.org , Bishakha > > > Banerjee > > > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > You can see the current issue is that nmake isn't in the path. > > > > > > See > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F3&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538580971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=9EgwIlzgbWheMap09LZZi39imUjH9FRJ6mt2ufdL3Us%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F3&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538580971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=9EgwIlzgbWheMap09LZZi39imUjH9FRJ6mt2ufdL3Us%3D&reserved=0 > > > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F3&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538590936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=P8VgucIzKYuJxPweJb%2FTGbyo0SFLKWijqvKa6y8QDmA%3D&reserved=0 > >> > > > > > > You need to have that setup for the buildbot worker to actually work. > > > > > > i.e. logged in as the user in windows running cmd you need to have it so > > > that "nmake" is accessible and operating correctly. > > > > > > Have you completed that step? > > > > > > There are multiple ways to set that up - and the approach I took was to > > > run the vcvars64.bat setup script from Microsoft and then dump the > > > environment and include setting a matching environment in buildbot.tac. > > > > > > You can of course copy all the environment variables into the users > > > environment. > > > > > > eng at DESKTOP-75K0EME C:\buildbot\tjh-win10-1-tls>type make-env.py > > > /import os > > > for k, v in os.environ.items(): > > > > > > print('os.environ[\''+str(k)+'\']=\''+str(v).replace('\\','\\\\')+'\'')/ > > > > > > I run that script (in a window that has had vcvars64.bat run) and > > > changed into the buildbot worker directory (where buildbot.tac exists) > > > > > > python make-env.py > env.py > > > > > > And I modified buildbot.tac to have: > > > > > > /def include(filename): > > > if os.path.exists(filename): > > > execfile(filename) > > > > > > include('env.py')/ > > > > > > That is how I setup a windows based worker configuration - the one you > > > see at > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fworkers%2F6&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538590936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ah7AZUg4pbCgyNv%2FABEeVt0TbspNu3Ou%2FSh4CDdZ2g8%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fworkers%2F6&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538590936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ah7AZUg4pbCgyNv%2FABEeVt0TbspNu3Ou%2FSh4CDdZ2g8%3D&reserved=0 > > > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fworkers%2F6&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538590936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ah7AZUg4pbCgyNv%2FABEeVt0TbspNu3Ou%2FSh4CDdZ2g8%3D&reserved=0 > >> > > > > > > Tim. > > > > > > On Wed, May 12, 2021 at 9:41 PM Madhur Walia > > >> wrote: > > > > > > Hi Richard, > > > > > > We restarted buildbot-worker in Windows 2019 and it seems to be > > > connecting now. We could see files under Base Directory as shown > > below. > > > > > > We could see couple of errors related to absence of Perl and cmake > > > in build Master Dashboard. So, we have installed them as well. > > > > > > Table Description automatically generated > > > > > > Yes, when you SSH, you will be connected to cmd.exe. One of the > > > screenshots we shared had PowerShell utility but you should be able > > > to run the commands through cmd.exe as well. We are using the same. > > > > > > Please let us know if you face any issues. > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > *From: *Richard Levitte > > >> > > > *Date: *Wednesday, 12 May 2021 at 2:08 PM > > > *To: *Madhur Walia > >> > > > *Cc: *Richard Levitte > > >>, Sunil > > Kumar Yadav > > > > >>, Manoj > > > Maskara > >>, Tim > > > Hudson > >>, > > > buildbot-admin at openssl.org > > > > > > > > >>, Bishakha Banerjee > > > > >> > > > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > The winserver2019 worker did show up once! At the time, you hadn't > > > installed the python package pywin32, but when I went in looking, it > > > looked like you had. However, the winserver2019 worker isn't showing > > > up now, could it be that it needs to be restarted? > > > > > > Do note that when we SSH to the machine, we end up with a cmd.exe > > > prompt. However, the images you've sent us suggest that you run from > > > a Mingw64 prompt, and I do not know how to get there from cmd.exe, so > > > it's will need instructions to do restarts for you. > > > > > > Cheers, > > > Richard > > > > > > Right now, it looks like you need to get the winserver2019 worker > > > started. I hope it's problem free at this point. > > > > > > On Fri, 07 May 2021 09:51:22 +0200, > > > Madhur Walia wrote: > > > > > > > > Hi Richard, > > > > > > > > We are able to connect to Buildbot Master from Windows 2019 as > > > well now. To our surprise, > > > > Buildbot-worker/ Python was searching for Certificate directory > > > in base directory. > > > > > > > > After pointing ssl-root-dir to a directory hosted in base > > > directory, it was able to connect. > > > > > > > > Please confirm the connection. > > > > > > > > Also, What are the next steps for Photon 4 and Windows 2019 now? > > > > > > > > Thank you for your inputs. > > > > > > > > Regards, > > > > > > > > Madhur > > > > > > > > From: Madhur Walia > >> > > > > Date: Thursday, 6 May 2021 at 10:04 PM > > > > To: Richard Levitte > > >>, Sunil > > Kumar Yadav > > > > >> > > > > Cc: Richard Levitte > > >>, Manoj > > Maskara > > >>, Tim > > Hudson > > > > > >>, > > > buildbot-admin at openssl.org > > > > > > >> > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > Thank you Richard. So, Photon 4.0 seems to be okay for now and > > > next update would be from your > > > > development team. > > > > > > > > We captured a wireshark trace keeping default buildbot.tac and > > > could see ?Unknown CA? error. We > > > > then pointed the trustroots/ ssl-root-dir to a custom path (to > > > pem files), and encountered another > > > > error which points to failure in trusting CA certificate filepath. > > > > > > > > TextDescription automatically generated > > > > > > > > We tried pointing trustroots directory to absolute certificate > > > directory path but no luck. > > > > > > > > Other debugging steps involves, > > > > > > > > ? Running ?openssl s_client -state -debug -connect > > > buildbot.openssl.org:9989? which gives > > > > Verification: OK if we point the -CAfile to Hashed CA pem file > > > names/ location. > > > > > > > > ? Executing, a python code to verify against CA file > > > path, which shows a successful CA > > > > trust in Wireshark, > > > > > > > > import os > > > > > > > > import requests > > > > > > > > > > > > > r=requests.get(' > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538590936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=WdumwLeuN1YqFDuITV3E2EftBZGF9cIFar2bi6D%2FOhw%3D&reserved=0 > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538590936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=WdumwLeuN1YqFDuITV3E2EftBZGF9cIFar2bi6D%2FOhw%3D&reserved=0 > >>') > > > > > > > > Graphical user interface, text, applicationDescription > > > automatically generat > > > > > > > > This either seems to be a platform, (Windows) specific issue or > > > something related to twisted OR > > > > something very miniscule that @Sunil Kumar Yadav and I are unable > > > to catch. > > > > > > > > I can schedule a call to discuss this in more depth keeping in > > > mind we are almost near to > > > > completion of 3~4 weeks window. > > > > > > > > Please let me know, Sunil and I are based out of India, IST time > > > zone. We can talk during IST > > > > evening, Your Morning. > > > > > > > > Thanks & Regards, > > > > > > > > Madhur > > > > > > > > From: Richard Levitte > > >> > > > > Date: Wednesday, 5 May 2021 at 8:37 PM > > > > To: Madhur Walia > >> > > > > Cc: Richard Levitte > > >>, Manoj > > Maskara > > >>, Tim > > Hudson > > > > > >>, Sunil Kumar Yadav > > > > >>, > > > buildbot-admin at openssl.org > > > > > > > >> > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > As far as I can tell, The Photon 4 worker is good. The fact that > > > > "make test" currently fails isn't a problem with the worker as > > far as > > > > I can see... our development team will have to look at it. > > > > > > > > As for the Windows worker, it doesn't seem to connect. Have you > > > > verified that the two .pem files are in the directory that's > > > specified > > > > in buildbot.tac? > > > > > > > > Cheers, > > > > Richard > > > > > > > > On Wed, 05 May 2021 12:11:46 +0200, > > > > Madhur Walia wrote: > > > > > > > > > > > > > > > Hi Richard, Tim, > > > > > > > > > > Awaiting further updates. Please assist. > > > > > > > > > > Thanks & Regards, > > > > > > > > > > Madhur > > > > > > > > > > From: Madhur Walia > >> > > > > > Date: Monday, 3 May 2021 at 8:18 PM > > > > > To: Richard Levitte > > >> > > > > > Cc: Manoj Maskara > > >>, Tim > > Hudson > > >>, Sunil Kumar Yadav > > > > > > >>, > > > buildbot-admin at openssl.org > > > > > > >> > > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > > > Hi Richard, > > > > > > > > > > We have installed git on Photon, please let us know next steps. > > > > > > > > > > Installed buildbot and VS2017 on Windows 2019 as shown below > > > but the connection seems to be > > > > > dropping, > > > > > > > > > > Versions installed on Windows 2019, > > > > > > > > > > TextDescription automatically generated > > > > > > > > > > Win2019: Connection Failing, going in a loop, > > > > > > > > > > Graphical user interface, textDescription automatically > > generated > > > > > > > > > > Thanks & Regards, > > > > > > > > > > Madhur > > > > > > > > > > From: Madhur Walia > >> > > > > > Date: Monday, 3 May 2021 at 2:37 PM > > > > > To: Richard Levitte > > >> > > > > > Cc: Manoj Maskara > > >>, Tim > > Hudson > > >>, Sunil Kumar Yadav > > > > > > >>, > > > buildbot-admin at openssl.org > > > > > > >> > > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > > > Hi Richard, > > > > > > > > > > Thank you for the help. We had only installed buildbot-worker > > > on Photon4 and Windows 2019. After > > > > > installing Buildbot (master) on Photon4, the worker could start. > > > > > > > > > > We are now working on installing git on Photon4 and then > > > troubleshooting Windows 2019. I will > > > > keep > > > > > you updated. > > > > > > > > > > Regards, > > > > > > > > > > Madhur > > > > > > > > > > From: Richard Levitte > > >> > > > > > Date: Monday, 3 May 2021 at 2:33 PM > > > > > To: Madhur Walia > >> > > > > > Cc: Manoj Maskara > > >>, Tim > > Hudson > > >>, Sunil Kumar Yadav > > > > > > >>, > > > buildbot-admin at openssl.org > > > > > > >> > > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > > > I now noticed that the Photon 4 workers have connected, so I > > assume > > > > > the 'optionsForClientTLS' is a thing of the past. > > > > > > > > > > Looking at one of the builds, > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538600882%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YQhAksX0G%2BC8rm8lFYba9jhEonqbNg%2BZSNUqCgijvhI%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538600882%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YQhAksX0G%2BC8rm8lFYba9jhEonqbNg%2BZSNUqCgijvhI%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538600882%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YQhAksX0G%2BC8rm8lFYba9jhEonqbNg%2BZSNUqCgijvhI%3D&reserved=0 > >> > > > > > , > > > > > it looks like git isn't installed on the worker... > > > > > > > > > > Cheers, > > > > > Richard > > > > > > > > > > On Mon, 03 May 2021 10:34:57 +0200, > > > > > Richard Levitte wrote: > > > > > > > > > > > > On Mon, 26 Apr 2021 20:25:34 +0200, > > > > > > Madhur Walia wrote: > > > > > > > > > > > > > > Hi Matt, > > > > > > > > > > > > > > Thank you for the instructions. However, we are facing > > > couple of issues while starting > > > > > buildbot-worker, > > > > > > > > > > > > > > For both platforms, we pointed Certificate/SSL settings to > > > a custom directory in > > > > buildbot.tac > > > > > as per your recommendation. We also tried importing both > > > certs, isrg-root-xi & lets-encrypt-r3 > > > > to > > > > > trust store of OS but no luck. > > > > > > > > > > > > > > Photon, > > > > > > > Getting error, " builtins.NameError: name > > > 'optionsForClientTLS' is not defined" as > > > > shown > > > > > in Photon1 screenshot attached. > > > > > > > Also ran a curl command to check SSL connectivity, > > > seems to be failing, attached > > > > > screenshot Photon2. > > > > > > > > > > > > Please check your versions of the following packages: > > > > > > > > > > > > - buildbot (should be at least version 2.6.0) > > > > > > - twisted (should be at least version 17.9.0 according to > > > buildbot > > > > > > 2.6.0 requirements) > > > > > > > > > > > > 'optionsForClientTLS' is a method that appeared in twisted > > > version 14.0. > > > > > > > > > > > > > Windows, > > > > > > > Getting, "Unicode error" as shown in Windows1 > > > screenshot attached. > > > > > > > Also ran a curl command to check SSL connectivity, > > > seems to be failing, attached > > > > > screenshot Windows2. > > > > > > > > > > > > From the error message at the end of Windows1.png, you have > > > an invalid > > > > > > unicode character on line 30. Could it be a character with > > > diacritics > > > > > > not encoded with UTF-8? > > > > > > > > > > > > Cheers, > > > > > > Richard > > > > > > > > > > > > > Do you have any pointers on these errors? Please let us > > know. > > > > > > > > > > > > > > Thanks & Regards, > > > > > > > Madhur > > > > > > > > > > > > > > > > > ------------------------------------------------------------------ > > > > > > > > > > > > > > On 21/04/21, 4:47 PM, "Matt Caswell" > > >> wrote: > > > > > > > > > > > > > > Thanks Manoj. > > > > > > > > > > > > > > To be able to set up your worker, you must use version > > > 2.6.0 or > > > > > > > higher. Older version do not support TLS-protected > > > connections. > > > > > > > > > > > > > > Please see these instructions for installing the > > > buildbot worker > > > > > > > software: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538600882%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fGqRW2%2BtI4BXq0kmHvqd%2Fo010dNxSu%2FLBm5isMAHe3g%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538600882%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fGqRW2%2BtI4BXq0kmHvqd%2Fo010dNxSu%2FLBm5isMAHe3g%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538600882%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fGqRW2%2BtI4BXq0kmHvqd%2Fo010dNxSu%2FLBm5isMAHe3g%3D&reserved=0 > >> > > > > > > > > > > > > > > When buildbot has been installed on the platform where > > > the buildbot > > > > > > > worker is to be run, this is how a worker is created > > > (for your PhotonOS > > > > > > > worker): > > > > > > > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > > > buildbot.openssl.org:9989 > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538610838%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Mnt45BCwWJR%2B606DvDroCq19wRb0VRvYLii1rg6hK1M%3D&reserved=0 > >> > > > vmware-photonos40 nifs0Tweex_ > > > > > > > > > > > > > > And for your Windows server: > > > > > > > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > > > buildbot.openssl.org:9989 > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538610838%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Mnt45BCwWJR%2B606DvDroCq19wRb0VRvYLii1rg6hK1M%3D&reserved=0 > >> > > > vmware-winserver2019 Efyin.Freg0 > > > > > > > > > > > > > > > > > > > > > where BASEDIR is determined by you. See further down > > > for a few notes > > > > > > > on TLS. > > > > > > > > > > > > > > To run a buildbot worker, you do this: > > > > > > > > > > > > > > $ buildbot-worker start BASEDIR > > > > > > > > > > > > > > Apart from the software needed to run a buildbot > > > worker, and the > > > > > > > utilities that are the normal part of the operating > > > system, you also > > > > > > > need to ensure that the following components are > > available: > > > > > > > > > > > > > > - toolchains, i.e. C compiler, linker, make. If you > > > have specified > > > > > > > toolchains in the worker request form, you need to > > > ensure that all > > > > > > > of them are installed. > > > > > > > > > > > > > > - git > > > > > > > > > > > > > > Regarding TLS, it may be that the buildbot worker > > > platform doesn't > > > > > > > have the appropriate certification verification roots > > > set up. In that > > > > > > > case, you may need to apply the attached buildbot.tac > > > patch, and store > > > > > > > the attached PEM files in a directory of your choice. > > > Finish up by > > > > > > > find the string '/PATH/TO/ssl-roots-dir' and replace > > > its contents with > > > > > > > the path of directory where you stored the PEM files. > > > > > > > > > > > > > > Matt > > > > > > > > > > > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > > > > > > Hi Tim & Richard, > > > > > > > > > > > > > > > > We have filled out the worker-request-form for 2 of > > > our platforms, one unix type and > > > > > other Windows. Also, the platforms, for your convenience am > > > listing here: > > > > > > > > > > > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon > > > Gold 6230R on Dell PowerEdge R740 > > > > > (Platform type: Unix, x86_64, build+test, gcc) > > > > > > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel > > > Xeon Gold 6230R on Dell PowerEdge > > > > > R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > > > > > > > > > > > Please provide the credentials and instruction on > > > setting up the buildbot worker. > > > > > > > > > > > > > > > > Thanks, > > > > > > > > Manoj > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > From: fips-sponsors > > > > > > >> On Behalf Of Richard Levitte > > > > > > > > Sent: Monday, April 12, 2021 12:20 AM > > > > > > > > To: fips-sponsors at openssl.org > > > > > > > > > > > > Subject: [fips-sponsors] Buildbot workers > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > We are finally ready to start getting buildbot worker > > > requests. > > > > > > > > > > > > > > > > The way this will work is that we're asking you to > > > answer a form with details for each > > > > > worker you want to set up for us, such as what platform, what > > > architecture, and where relevant, > > > > > what toolchains are installed. > > > > > > > > > > > > > > > > The form is attached below, and include explanations > > > for all the fields to fill in. > > > > > Please send it to buildbot-admin at openssl.org > > > > >. > > > > > > > > > > > > > > > > In response, you will receive an email with the name > > > and password we assign your > > > > worker > > > > > (s), and instructions how to set the worker up. > > > > > > > > > > > > > > > > > > > > > > [2 Photon1.png ] > > > > > > > > > > > > > > [3 Photon2.png ] > > > > > > > > > > > > > > [4 Windows1.png ] > > > > > > > > > > > > > > [5 Windows2.png ] > > > > > > > > > > > > > > [6 ] > > > > > > > _______________________________________________ > > > > > > > buildbot-admin mailing list > > > > > > > buildbot-admin at openssl.org > > > > > > > > > > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538610838%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=T0y3ND%2BZhEhj6hGJ%2FUpAvy9IccJv2prps%2Faw1NRKL7M%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538610838%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=T0y3ND%2BZhEhj6hGJ%2FUpAvy9IccJv2prps%2Faw1NRKL7M%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538610838%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=T0y3ND%2BZhEhj6hGJ%2FUpAvy9IccJv2prps%2Faw1NRKL7M%3D&reserved=0 > >> > > > > > > -- > > > > > > Richard Levitte levitte at openssl.org > > > > > > > > > OpenSSL Project > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538610838%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=UkWboZ7D9Aq%2FCLovXp5cQg8DAqmOF2oF4PKJXbTCfNs%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538620796%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=f29xdRdAP%2FRfkDlnohVEmnfJfhqXgW0z4zhu6SksiAg%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538620796%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=f29xdRdAP%2FRfkDlnohVEmnfJfhqXgW0z4zhu6SksiAg%3D&reserved=0 > >> > > > > > > _______________________________________________ > > > > > > buildbot-admin mailing list > > > > > > buildbot-admin at openssl.org > > > > > > > > > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538620796%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=mp9eetQUKRYzXB4U5ePOBGSTydZJbhdIu9Wl3gR5ZgY%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538620796%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=mp9eetQUKRYzXB4U5ePOBGSTydZJbhdIu9Wl3gR5ZgY%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538620796%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=mp9eetQUKRYzXB4U5ePOBGSTydZJbhdIu9Wl3gR5ZgY%3D&reserved=0 > >> > > > > > -- > > > > > Richard Levitte levitte at openssl.org > > > > > > > > OpenSSL Project > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538620796%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=f29xdRdAP%2FRfkDlnohVEmnfJfhqXgW0z4zhu6SksiAg%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538630752%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ug2PAMTL%2F0EMfGFTR4iIdmzbQCW9ylOoN9E11D9uh1g%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538630752%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ug2PAMTL%2F0EMfGFTR4iIdmzbQCW9ylOoN9E11D9uh1g%3D&reserved=0 > >> > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Richard Levitte levitte at openssl.org > > > > > > > OpenSSL Project > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538630752%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ug2PAMTL%2F0EMfGFTR4iIdmzbQCW9ylOoN9E11D9uh1g%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538630752%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ug2PAMTL%2F0EMfGFTR4iIdmzbQCW9ylOoN9E11D9uh1g%3D&reserved=0 > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538630752%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ug2PAMTL%2F0EMfGFTR4iIdmzbQCW9ylOoN9E11D9uh1g%3D&reserved=0 > > > > > -- > > > Richard Levitte levitte at openssl.org > > > > > OpenSSL Project > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538630752%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ug2PAMTL%2F0EMfGFTR4iIdmzbQCW9ylOoN9E11D9uh1g%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538630752%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ug2PAMTL%2F0EMfGFTR4iIdmzbQCW9ylOoN9E11D9uh1g%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538640708%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=nx6%2FUlbYjAVKGtQOTExbwRJIImJyIo42ALV%2F5pkdwWw%3D&reserved=0 > >> > > > > > > > > > _______________________________________________ > > > buildbot-admin mailing list > > > buildbot-admin at openssl.org > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538640708%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=gRgrl8FlujFp3FyaShjRLbifc7XoYR0HbauVg8tY%2BxI%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538640708%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=gRgrl8FlujFp3FyaShjRLbifc7XoYR0HbauVg8tY%2BxI%3D&reserved=0 > > > > > > > > > > [1.2 image001.png ] > [2 ] > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538640708%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=gRgrl8FlujFp3FyaShjRLbifc7XoYR0HbauVg8tY%2BxI%3D&reserved=0 -- Richard Levitte levitte at openssl.org OpenSSL Project https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538640708%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=nx6%2FUlbYjAVKGtQOTExbwRJIImJyIo42ALV%2F5pkdwWw%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1735258 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 466163 bytes Desc: image002.png URL: From tjh at cryptsoft.com Sun May 16 01:35:45 2021 From: tjh at cryptsoft.com (Tim Hudson) Date: Sun, 16 May 2021 11:35:45 +1000 Subject: [buildbot-admin] buildbot appears to be non-functional Message-ID: Website isn't responding at the moment ... https://fips.buildbot.openssl.org/#/workers Tim. -------------- next part -------------- An HTML attachment was scrubbed... URL: From levitte at openssl.org Sun May 16 04:49:10 2021 From: levitte at openssl.org (Richard Levitte) Date: Sun, 16 May 2021 06:49:10 +0200 Subject: [buildbot-admin] buildbot appears to be non-functional In-Reply-To: References: Message-ID: <87lf8f8erd.wl-levitte@openssl.org> It's up and running again. This is a symptom of no more disk space available... in this case, it's MySQL that stops responding, leading to an empty buildbot. I've added more disk space for that guest now, and restart mysql and buildbot at fips. It's up again. Cheers, Richard On Sun, 16 May 2021 03:35:45 +0200, Tim Hudson wrote: > > Website isn't responding at the moment ...? > > https://fips.buildbot.openssl.org/#/workers > > Tim. > > > [2 ] > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://mta.openssl.org/mailman/listinfo/buildbot-admin -- Richard Levitte levitte at openssl.org OpenSSL Project http://www.openssl.org/~levitte/ From levitte at openssl.org Tue May 18 20:05:25 2021 From: levitte at openssl.org (Richard Levitte) Date: Tue, 18 May 2021 22:05:25 +0200 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <87y2cwmc3h.wl-levitte@openssl.org> <87mttbm1gf.wl-levitte@openssl.org> <87o8dfqbwh.wl-levitte@openssl.org> Message-ID: <87h7iz95a2.wl-levitte@openssl.org> [ Also adding buildbot-admin at openssl.org (I should have done that long ago) ] Yes, some technical details is what I'm trying to get. Right now, that worker is building, sure, but that's a MacOS build, which wasn't what you wanted. So Tim, Connor, if you have something to share, I can hopefully do better progress on our end. Cheers, Richard On Mon, 17 May 2021 15:28:50 +0200, Nivedita Chevvakula wrote: > > On this buildbot slave we don't run any our projects, we have set this slave only for buildbot worker. Please let me know if I give ssh creds it will expedite the process. > > Also adding Connor and Timmy, hopefully they can clarify on how we build OpenSSL project. > > Best, > Niv > > ?On 5/13/21, 4:24 AM, "Richard Levitte" wrote: > > What we expect to do is this at a minimum: > > perl Configure {args...} > make > > In the form that you filled in, there was the option to specify > necessary environment variables (which can affect the configuration > step) and configuration options. I was hoping that would be enough to > get something going. > > I do not know what you're talking about regarding a .conf file created > by the Configure step. I understand that you have some sort of super > project that involves building OpenSSL as a component, though, so I > can only assume that somewhere in there, it should be possible to find > how the OpenSSL part is configured, i.e. I assume that there is a run > of Configure hiding in there somewhere, and that it should be possible > to see what arguments are used, as well as any relevant environment > variables. > > Does this answer your question? > > Cheers, > Richard > > On Fri, 07 May 2021 15:12:11 +0200, > Nivedita Chevvakula wrote: > > > > We generate a project using cmake that gets built as a dependency of other components in our project. If you are trying to do - build everything using make, which requires a .conf file created with ./Configure step. If so should have one of those somewhere that satisfies what you are looking to produce for iOS, as well as a different one for Android, please provide that we can put it in place on the build bot and just use that? > > > > Please advise. > > > > Best, > > Niv > > > > ?On 5/4/21, 2:56 AM, "Richard Levitte" wrote: > > > > Hi, > > > > The worker is connecting fine, so far so good. > > > > However, I realised that there are things missing, where we need > > information from you! > > > > This worker is meant to build for iOS, is it not? That should require > > extra OpenSSL configuration options. So let me ask you this, when you > > usually build OpenSSL for iOS, exactly how do you usually configure > > OpenSSL? > > > > Cheers, > > Richard > > > > On Tue, 04 May 2021 03:46:17 +0200, > > Nivedita Chevvakula wrote: > > > > > > Richard, > > > > > > You can ignore my last mail with error starting buildbot. It is seems to work now after editing > > > syntax for python2.7. Also we have created user ?buildbot? for this mac as recommended. Please let > > > me know if we need to pass those credentials or need to setup anything else for the build bot. > > > > > > Best, > > > > > > Niv > > > > > > From: Nivedita Chevvakula > > > Date: Monday, May 3, 2021 at 6:44 PM > > > To: Richard Levitte > > > Subject: Re: [fips-sponsors] Buildbot workers > > > > > > Richard, > > > > > > Buildbot has now installed with linker, make, c compilers. > > > > > > While starting the worker to connect to master after editing tac file as you mentioned getting > > > syntax error . not able to pin point why. Attaching the error log and the tac file here. Could you > > > please help. > > > > > > Best, > > > > > > Niv > > > > > > From: Nivedita Chevvakula > > > Date: Monday, May 3, 2021 at 9:22 AM > > > To: Richard Levitte > > > Cc: "levitte at openssl.org" , Tim Champagne , Kevin > > > Fox > > > Subject: Re: [fips-sponsors] Buildbot workers > > > > > > Hi Richard, > > > > > > Thank you for sending the worker bot setup requirements, I will go thru and will set up the > > > workerbot and will install the rest. Do you have any deadline for this setup please share so that > > > it will help me prioritize. > > > > > > So far these tools are installed over the mac : > > > > > > 1. Android Studio 4.1.3 > > > 2. Xcode 12.5 > > > 3. clang version 12.0.5 > > > 4. Gcc > > > 5. Visual Studio Community 2019 for Mac > > > > > > === Visual Studio Community 2019 for Mac === > > > > > > Version 8.9.7 (build 8) > > > > > > Installation UUID: f1ca8dad-7314-419a-8a39-880ba8a71230 > > > > > > GTK+ 2.24.23 (Raleigh theme) > > > > > > Xamarin.Mac 6.18.0.23 (d16-6 / 088c73638) > > > > > > Package version: 612000125 > > > > > > === Mono Framework MDK === > > > > > > Runtime: > > > > > > Mono 6.12.0.125 (2020-02/8c552e98bd6) (64-bit) > > > > > > Package version: 612000125 > > > > > > === Roslyn (Language Service) === > > > > > > 3.9.0-6.21152.10+c10f884b30737542ddd84ca889a4aad9281ce210 > > > > > > === NuGet === > > > > > > Version: 5.8.0.6860 > > > > > > === .NET Core SDK === > > > > > > SDK: /usr/local/share/dotnet/sdk/5.0.202/Sdks > > > > > > SDK Versions: > > > > > > 5.0.202 > > > > > > 3.1.408 > > > > > > 2.1.4 > > > > > > MSBuild SDKs: /Applications/Visual Studio.app/Contents/Resources/lib/monodevelop/bin/MSBuild/ > > > Current/bin/Sdks > > > > > > === .NET Core Runtime === > > > > > > Runtime: /usr/local/share/dotnet/dotnet > > > > > > Runtime Versions: > > > > > > 5.0.5 > > > > > > 3.1.14 > > > > > > 2.0.5 > > > > > > === .NET Core 3.1 SDK === > > > > > > SDK: 3.1.408 > > > > > > === Xamarin.Profiler === > > > > > > Version: 1.6.15.68 > > > > > > Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler > > > > > > === Updater === > > > > > > Version: 11 > > > > > > === Apple Developer Tools === > > > > > > Xcode 12.5 (18205) > > > > > > Build 12E262 > > > > > > === Xamarin.Mac === > > > > > > Xamarin.Mac not installed. Can't find /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/ > > > Version. > > > > > > === Xamarin.iOS === > > > > > > Xamarin.iOS not installed. > > > > > > Can't find mtouch or the Version file at /Library/Frameworks/Xamarin.iOS.framework/Versions/ > > > Current. > > > > > > === Xamarin Designer === > > > > > > Version: 16.9.0.324 > > > > > > Hash: b1e216c75 > > > > > > Branch: remotes/origin/d16-9 > > > > > > Build date: 2021-04-16 00:02:50 UTC > > > > > > === Xamarin.Android === > > > > > > Version: 11.2.2.1 (Visual Studio Community) > > > > > > Commit: xamarin-android/d16-9/877f572 > > > > > > Android SDK: /Users/ec2-user/Library/Developer/Xamarin/android-sdk-macosx > > > > > > Supported Android versions: > > > > > > None installed > > > > > > SDK Tools Version: 26.1.1 > > > > > > SDK Platform Tools Version: 30.0.4 > > > > > > SDK Build Tools Version: 30.0.2 > > > > > > Build Information: > > > > > > Mono: 5e9cb6d > > > > > > Java.Interop: xamarin/java.interop/d16-9 at 54f8c24 > > > > > > ProGuard: Guardsquare/proguard/v7.0.1 at 912d149 > > > > > > SQLite: xamarin/sqlite/3.34.1 at daff8f4 > > > > > > Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-9 at d210f11 > > > > > > === Microsoft OpenJDK for Mobile === > > > > > > Java SDK: /Users/ec2-user/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_1.8.0.25 > > > > > > 1.8.0-25 > > > > > > Android Designer EPL code available here: > > > > > > https://github.com/xamarin/AndroidDesigner.EPL > > > > > > === Android SDK Manager === > > > > > > Version: 16.9.0.22 > > > > > > Hash: a391de2 > > > > > > Branch: remotes/origin/d16-9~2 > > > > > > Build date: 2021-03-24 08:30:26 UTC > > > > > > === Android Device Manager === > > > > > > Version: 16.9.0.17 > > > > > > Hash: fc2b3db > > > > > > Branch: remotes/origin/dev/jmt/d16-9bump~1 > > > > > > Build date: 2021-03-24 08:30:44 UTC > > > > > > === Build Information === > > > > > > Release ID: 809070008 > > > > > > Git revision: 8b7ac2442978ec88d09703fafa4e43eb774f0a26 > > > > > > Build date: 2021-04-16 07:38:03-04 > > > > > > Build branch: release-8.9 > > > > > > Xamarin extensions: 8b7ac2442978ec88d09703fafa4e43eb774f0a26 > > > > > > === Operating System === > > > > > > Mac OS X 10.16.0 > > > > > > Darwin 20.3.0 Darwin Kernel Version 20.3.0 > > > > > > Thu Jan 21 00:07:06 PST 2021 > > > > > > root:xnu-7195.81.3~1/RELEASE_X86_64 x86_64 > > > > > > Best, > > > > > > Niv > > > > > > From: Richard Levitte > > > Date: Monday, May 3, 2021 at 4:54 AM > > > To: Nivedita Chevvakula > > > Cc: levitte at openssl.org , Tim Champagne , Kevin Fox > > > > > > Subject: Re: [fips-sponsors] Buildbot workers > > > > > > Hi, > > > > > > Thank you for offering workers to us! > > > > > > To be able to set up your worker, you must use version 2.6.0 or > > > higher. Older version do not support TLS-protected connections. > > > > > > Please see these instructions for installing the buildbot worker > > > software: > > > > > > http://docs.buildbot.net/latest/manual/installation/worker.html > > > > > > When buildbot has been installed on the platform where the buildbot > > > worker is to be run, this is how a worker is created: > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > buildbot.openssl.org:9989 'bluecedar-01' 'Rak;osErfabOn5' > > > > > > where BASEDIR is determined by you. See further down for a few notes > > > on TLS. > > > > > > To run a buildbot worker, you do this: > > > > > > $ buildbot-worker start BASEDIR > > > > > > Apart from the software needed to run a buildbot worker, and the > > > utilities that are the normal part of the operating system, you also > > > need to ensure that the following components are available: > > > > > > - toolchains, i.e. C compiler, linker, make. If you have specified > > > toolchains in the worker request form, you need to ensure that all > > > of them are installed. > > > > > > - git > > > > > > Regarding TLS, it may be that the buildbot worker platform doesn't > > > have the appropriate certification verification roots set up. In that > > > case, you may need to apply the attached buildbot.tac patch, and store > > > the attached PEM files in a directory of your choice. Finish up by > > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with > > > the path of directory where you stored the PEM files. > > > > > > > > -- > > Richard Levitte levitte at openssl.org > > OpenSSL Project http://www.openssl.org/~levitte/ > -- > Richard Levitte levitte at openssl.org > OpenSSL Project http://www.openssl.org/~levitte/ -- Richard Levitte levitte at openssl.org OpenSSL Project http://www.openssl.org/~levitte/ From ckelley at bluecedar.com Wed May 19 00:54:35 2021 From: ckelley at bluecedar.com (Connor Kelley) Date: Wed, 19 May 2021 00:54:35 +0000 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: <87h7iz95a2.wl-levitte@openssl.org> References: <87k0p89dfr.wl-levitte@openssl.org> <87y2cwmc3h.wl-levitte@openssl.org> <87mttbm1gf.wl-levitte@openssl.org> <87o8dfqbwh.wl-levitte@openssl.org> , <87h7iz95a2.wl-levitte@openssl.org> Message-ID: Hi Richard, I?ve got a working build that required a couple of updates to the 15-iOS.conf file to get it current. With those changes plus the configure invocation the build seemingly completes successfully. What is the process for submitting a PR to get those changes in and usable? Thanks, -Connor Get Outlook for iOS ________________________________ From: Richard Levitte Sent: Tuesday, May 18, 2021 4:05:25 PM To: Nivedita Chevvakula Cc: Richard Levitte ; Tim Champagne ; Connor Kelley ; buildbot-admin at openssl.org Subject: Re: [fips-sponsors] Buildbot workers [ Also adding buildbot-admin at openssl.org (I should have done that long ago) ] Yes, some technical details is what I'm trying to get. Right now, that worker is building, sure, but that's a MacOS build, which wasn't what you wanted. So Tim, Connor, if you have something to share, I can hopefully do better progress on our end. Cheers, Richard On Mon, 17 May 2021 15:28:50 +0200, Nivedita Chevvakula wrote: > > On this buildbot slave we don't run any our projects, we have set this slave only for buildbot worker. Please let me know if I give ssh creds it will expedite the process. > > Also adding Connor and Timmy, hopefully they can clarify on how we build OpenSSL project. > > Best, > Niv > > ?On 5/13/21, 4:24 AM, "Richard Levitte" wrote: > > What we expect to do is this at a minimum: > > perl Configure {args...} > make > > In the form that you filled in, there was the option to specify > necessary environment variables (which can affect the configuration > step) and configuration options. I was hoping that would be enough to > get something going. > > I do not know what you're talking about regarding a .conf file created > by the Configure step. I understand that you have some sort of super > project that involves building OpenSSL as a component, though, so I > can only assume that somewhere in there, it should be possible to find > how the OpenSSL part is configured, i.e. I assume that there is a run > of Configure hiding in there somewhere, and that it should be possible > to see what arguments are used, as well as any relevant environment > variables. > > Does this answer your question? > > Cheers, > Richard > > On Fri, 07 May 2021 15:12:11 +0200, > Nivedita Chevvakula wrote: > > > > We generate a project using cmake that gets built as a dependency of other components in our project. If you are trying to do - build everything using make, which requires a .conf file created with ./Configure step. If so should have one of those somewhere that satisfies what you are looking to produce for iOS, as well as a different one for Android, please provide that we can put it in place on the build bot and just use that? > > > > Please advise. > > > > Best, > > Niv > > > > ?On 5/4/21, 2:56 AM, "Richard Levitte" wrote: > > > > Hi, > > > > The worker is connecting fine, so far so good. > > > > However, I realised that there are things missing, where we need > > information from you! > > > > This worker is meant to build for iOS, is it not? That should require > > extra OpenSSL configuration options. So let me ask you this, when you > > usually build OpenSSL for iOS, exactly how do you usually configure > > OpenSSL? > > > > Cheers, > > Richard > > > > On Tue, 04 May 2021 03:46:17 +0200, > > Nivedita Chevvakula wrote: > > > > > > Richard, > > > > > > You can ignore my last mail with error starting buildbot. It is seems to work now after editing > > > syntax for python2.7. Also we have created user ?buildbot? for this mac as recommended. Please let > > > me know if we need to pass those credentials or need to setup anything else for the build bot. > > > > > > Best, > > > > > > Niv > > > > > > From: Nivedita Chevvakula > > > Date: Monday, May 3, 2021 at 6:44 PM > > > To: Richard Levitte > > > Subject: Re: [fips-sponsors] Buildbot workers > > > > > > Richard, > > > > > > Buildbot has now installed with linker, make, c compilers. > > > > > > While starting the worker to connect to master after editing tac file as you mentioned getting > > > syntax error . not able to pin point why. Attaching the error log and the tac file here. Could you > > > please help. > > > > > > Best, > > > > > > Niv > > > > > > From: Nivedita Chevvakula > > > Date: Monday, May 3, 2021 at 9:22 AM > > > To: Richard Levitte > > > Cc: "levitte at openssl.org" , Tim Champagne , Kevin > > > Fox > > > Subject: Re: [fips-sponsors] Buildbot workers > > > > > > Hi Richard, > > > > > > Thank you for sending the worker bot setup requirements, I will go thru and will set up the > > > workerbot and will install the rest. Do you have any deadline for this setup please share so that > > > it will help me prioritize. > > > > > > So far these tools are installed over the mac : > > > > > > 1. Android Studio 4.1.3 > > > 2. Xcode 12.5 > > > 3. clang version 12.0.5 > > > 4. Gcc > > > 5. Visual Studio Community 2019 for Mac > > > > > > === Visual Studio Community 2019 for Mac === > > > > > > Version 8.9.7 (build 8) > > > > > > Installation UUID: f1ca8dad-7314-419a-8a39-880ba8a71230 > > > > > > GTK+ 2.24.23 (Raleigh theme) > > > > > > Xamarin.Mac 6.18.0.23 (d16-6 / 088c73638) > > > > > > Package version: 612000125 > > > > > > === Mono Framework MDK === > > > > > > Runtime: > > > > > > Mono 6.12.0.125 (2020-02/8c552e98bd6) (64-bit) > > > > > > Package version: 612000125 > > > > > > === Roslyn (Language Service) === > > > > > > 3.9.0-6.21152.10+c10f884b30737542ddd84ca889a4aad9281ce210 > > > > > > === NuGet === > > > > > > Version: 5.8.0.6860 > > > > > > === .NET Core SDK === > > > > > > SDK: /usr/local/share/dotnet/sdk/5.0.202/Sdks > > > > > > SDK Versions: > > > > > > 5.0.202 > > > > > > 3.1.408 > > > > > > 2.1.4 > > > > > > MSBuild SDKs: /Applications/Visual Studio.app/Contents/Resources/lib/monodevelop/bin/MSBuild/ > > > Current/bin/Sdks > > > > > > === .NET Core Runtime === > > > > > > Runtime: /usr/local/share/dotnet/dotnet > > > > > > Runtime Versions: > > > > > > 5.0.5 > > > > > > 3.1.14 > > > > > > 2.0.5 > > > > > > === .NET Core 3.1 SDK === > > > > > > SDK: 3.1.408 > > > > > > === Xamarin.Profiler === > > > > > > Version: 1.6.15.68 > > > > > > Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler > > > > > > === Updater === > > > > > > Version: 11 > > > > > > === Apple Developer Tools === > > > > > > Xcode 12.5 (18205) > > > > > > Build 12E262 > > > > > > === Xamarin.Mac === > > > > > > Xamarin.Mac not installed. Can't find /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/ > > > Version. > > > > > > === Xamarin.iOS === > > > > > > Xamarin.iOS not installed. > > > > > > Can't find mtouch or the Version file at /Library/Frameworks/Xamarin.iOS.framework/Versions/ > > > Current. > > > > > > === Xamarin Designer === > > > > > > Version: 16.9.0.324 > > > > > > Hash: b1e216c75 > > > > > > Branch: remotes/origin/d16-9 > > > > > > Build date: 2021-04-16 00:02:50 UTC > > > > > > === Xamarin.Android === > > > > > > Version: 11.2.2.1 (Visual Studio Community) > > > > > > Commit: xamarin-android/d16-9/877f572 > > > > > > Android SDK: /Users/ec2-user/Library/Developer/Xamarin/android-sdk-macosx > > > > > > Supported Android versions: > > > > > > None installed > > > > > > SDK Tools Version: 26.1.1 > > > > > > SDK Platform Tools Version: 30.0.4 > > > > > > SDK Build Tools Version: 30.0.2 > > > > > > Build Information: > > > > > > Mono: 5e9cb6d > > > > > > Java.Interop: xamarin/java.interop/d16-9 at 54f8c24 > > > > > > ProGuard: Guardsquare/proguard/v7.0.1 at 912d149 > > > > > > SQLite: xamarin/sqlite/3.34.1 at daff8f4 > > > > > > Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-9 at d210f11 > > > > > > === Microsoft OpenJDK for Mobile === > > > > > > Java SDK: /Users/ec2-user/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_1.8.0.25 > > > > > > 1.8.0-25 > > > > > > Android Designer EPL code available here: > > > > > > https://github.com/xamarin/AndroidDesigner.EPL > > > > > > === Android SDK Manager === > > > > > > Version: 16.9.0.22 > > > > > > Hash: a391de2 > > > > > > Branch: remotes/origin/d16-9~2 > > > > > > Build date: 2021-03-24 08:30:26 UTC > > > > > > === Android Device Manager === > > > > > > Version: 16.9.0.17 > > > > > > Hash: fc2b3db > > > > > > Branch: remotes/origin/dev/jmt/d16-9bump~1 > > > > > > Build date: 2021-03-24 08:30:44 UTC > > > > > > === Build Information === > > > > > > Release ID: 809070008 > > > > > > Git revision: 8b7ac2442978ec88d09703fafa4e43eb774f0a26 > > > > > > Build date: 2021-04-16 07:38:03-04 > > > > > > Build branch: release-8.9 > > > > > > Xamarin extensions: 8b7ac2442978ec88d09703fafa4e43eb774f0a26 > > > > > > === Operating System === > > > > > > Mac OS X 10.16.0 > > > > > > Darwin 20.3.0 Darwin Kernel Version 20.3.0 > > > > > > Thu Jan 21 00:07:06 PST 2021 > > > > > > root:xnu-7195.81.3~1/RELEASE_X86_64 x86_64 > > > > > > Best, > > > > > > Niv > > > > > > From: Richard Levitte > > > Date: Monday, May 3, 2021 at 4:54 AM > > > To: Nivedita Chevvakula > > > Cc: levitte at openssl.org , Tim Champagne , Kevin Fox > > > > > > Subject: Re: [fips-sponsors] Buildbot workers > > > > > > Hi, > > > > > > Thank you for offering workers to us! > > > > > > To be able to set up your worker, you must use version 2.6.0 or > > > higher. Older version do not support TLS-protected connections. > > > > > > Please see these instructions for installing the buildbot worker > > > software: > > > > > > http://docs.buildbot.net/latest/manual/installation/worker.html > > > > > > When buildbot has been installed on the platform where the buildbot > > > worker is to be run, this is how a worker is created: > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > buildbot.openssl.org:9989 'bluecedar-01' 'Rak;osErfabOn5' > > > > > > where BASEDIR is determined by you. See further down for a few notes > > > on TLS. > > > > > > To run a buildbot worker, you do this: > > > > > > $ buildbot-worker start BASEDIR > > > > > > Apart from the software needed to run a buildbot worker, and the > > > utilities that are the normal part of the operating system, you also > > > need to ensure that the following components are available: > > > > > > - toolchains, i.e. C compiler, linker, make. If you have specified > > > toolchains in the worker request form, you need to ensure that all > > > of them are installed. > > > > > > - git > > > > > > Regarding TLS, it may be that the buildbot worker platform doesn't > > > have the appropriate certification verification roots set up. In that > > > case, you may need to apply the attached buildbot.tac patch, and store > > > the attached PEM files in a directory of your choice. Finish up by > > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with > > > the path of directory where you stored the PEM files. > > > > > > > > -- > > Richard Levitte levitte at openssl.org > > OpenSSL Project http://www.openssl.org/~levitte/ > -- > Richard Levitte levitte at openssl.org > OpenSSL Project http://www.openssl.org/~levitte/ -- Richard Levitte levitte at openssl.org OpenSSL Project http://www.openssl.org/~levitte/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt at openssl.org Wed May 19 07:57:26 2021 From: matt at openssl.org (Matt Caswell) Date: Wed, 19 May 2021 08:57:26 +0100 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <87y2cwmc3h.wl-levitte@openssl.org> <87mttbm1gf.wl-levitte@openssl.org> <87o8dfqbwh.wl-levitte@openssl.org> <87h7iz95a2.wl-levitte@openssl.org> Message-ID: Hi Connor, Please submit them as a pull request on our public github site: https://github.com/openssl/openssl/pulls If you email the PR number here once created then we will know to give it the attention it deserves. If the changes are anything other than very trivial then we will also need an ICLA from you individually, as well as a CCLA from Blue Cedar. See: https://www.openssl.org/policies/cla.html Matt On 19/05/2021 01:54, Connor Kelley wrote: > Hi Richard, > I?ve got a working build that required a couple of updates to the > 15-iOS.conf file to get it current. With those changes plus the > configure invocation the build seemingly completes successfully. What is > the process for submitting a PR to get those changes in and usable? > > Thanks, > -Connor > > Get Outlook for iOS > ------------------------------------------------------------------------ > *From:* Richard Levitte > *Sent:* Tuesday, May 18, 2021 4:05:25 PM > *To:* Nivedita Chevvakula > *Cc:* Richard Levitte ; Tim Champagne > ; Connor Kelley ; > buildbot-admin at openssl.org > *Subject:* Re: [fips-sponsors] Buildbot workers > [ Also adding buildbot-admin at openssl.org (I should have done that long > ago) ] > > Yes, some technical details is what I'm trying to get. > Right now, that worker is building, sure, but that's a MacOS build, > which wasn't what you wanted. > > So Tim, Connor, if you have something to share, I can hopefully do > better progress on our end. > > Cheers, > Richard > > On Mon, 17 May 2021 15:28:50 +0200, > Nivedita Chevvakula wrote: >> >> On this buildbot slave we don't run any our projects, we have set this slave only for buildbot worker. Please let me know if I give ssh creds it will expedite the process. >> >> Also adding Connor and Timmy, hopefully they can clarify on how we build OpenSSL project. >> >> Best, >> Niv >> >> ?On 5/13/21, 4:24 AM, "Richard Levitte" wrote: >> >>???? What we expect to do is this at a minimum: >> >>???????? perl Configure {args...} >>???????? make >> >>???? In the form that you filled in, there was the option to specify >>???? necessary environment variables (which can affect the configuration >>???? step) and configuration options.? I was hoping that would be enough to >>???? get something going. >> >>???? I do not know what you're talking about regarding a .conf file created >>???? by the Configure step.? I understand that you have some sort of super >>???? project that involves building OpenSSL as a component, though, so I >>???? can only assume that somewhere in there, it should be possible to find >>???? how the OpenSSL part is configured, i.e. I assume that there is a run >>???? of Configure hiding in there somewhere, and that it should be possible >>???? to see what arguments are used, as well as any relevant environment >>???? variables. >> >>???? Does this answer your question? >> >>???? Cheers, >>???? Richard >> >>???? On Fri, 07 May 2021 15:12:11 +0200, >>???? Nivedita Chevvakula wrote: >>???? > >>???? > We generate a project using cmake that gets built as a dependency of other components in our project. If you are trying to do - build everything using make, which requires a .conf file created with ./Configure step. If so should have one of those somewhere that satisfies what you are looking to produce for iOS, as well as a > different one for Android, please provide that we can put it in place on > the build bot and just use that? >>???? > >>???? > Please advise. >>???? > >>???? > Best, >>???? > Niv >>???? > >>???? > ?On 5/4/21, 2:56 AM, "Richard Levitte" wrote: >>???? > >>???? >???? Hi, >>???? > >>???? >???? The worker is connecting fine, so far so good. >>???? > >>???? >???? However, I realised that there are things missing, where we need >>???? >???? information from you! >>???? > >>???? >???? This worker is meant to build for iOS, is it not?? That should require >>???? >???? extra OpenSSL configuration options.? So let me ask you this, when you >>???? >???? usually build OpenSSL for iOS, exactly how do you usually configure >>???? >???? OpenSSL? >>???? > >>???? >???? Cheers, >>???? >???? Richard >>???? > >>???? >???? On Tue, 04 May 2021 03:46:17 +0200, >>???? >???? Nivedita Chevvakula wrote: >>???? >???? > >>???? >???? > Richard, >>???? >???? > >>???? >???? > You can ignore my last mail with error starting buildbot. It is seems to work now after editing >>???? >???? > syntax for python2.7. Also we have created user ?buildbot? for this mac as recommended. Please let >>???? >???? > me know if we need to pass those credentials or need to setup anything else for the build bot. >>???? >???? > >>???? >???? > Best, >>???? >???? > >>???? >???? > Niv >>???? >???? > >>???? >???? > From: Nivedita Chevvakula >>???? >???? > Date: Monday, May 3, 2021 at 6:44 PM >>???? >???? > To: Richard Levitte >>???? >???? > Subject: Re: [fips-sponsors] Buildbot workers >>???? >???? > >>???? >???? > Richard, >>???? >???? > >>???? >???? > Buildbot has now installed with linker, make, c compilers. >>???? >???? > >>???? >???? > While starting the worker to connect to master after editing tac file as you mentioned getting >>???? >???? > syntax error . not able to pin point why. Attaching the error log and the tac file here. Could you >>???? >???? > please help. >>???? >???? > >>???? >???? > Best, >>???? >???? > >>???? >???? > Niv >>???? >???? > >>???? >???? > From: Nivedita Chevvakula >>???? >???? > Date: Monday, May 3, 2021 at 9:22 AM >>???? >???? > To: Richard Levitte >>???? >???? > Cc: "levitte at openssl.org" , Tim Champagne , Kevin >>???? >???? > Fox >>???? >???? > Subject: Re: [fips-sponsors] Buildbot workers >>???? >???? > >>???? >???? > Hi Richard, >>???? >???? > >>???? >???? > Thank you for sending the worker bot setup requirements, I will go thru and will set up the >>???? >???? > workerbot and will install the rest. Do you have any deadline for this setup please share so that >>???? >???? > it will help me prioritize. >>???? >???? > >>???? >???? > So far these tools are installed over the mac : >>???? >???? > >>???? >???? >? 1. Android Studio 4.1.3 >>???? >???? >? 2. Xcode 12.5 >>???? >???? >? 3. clang version 12.0.5 >>???? >???? >? 4. Gcc >>???? >???? >? 5. Visual Studio Community 2019 for Mac >>???? >???? > >>???? >???? > === Visual Studio Community 2019 for Mac === >>???? >???? > >>???? >???? > Version 8.9.7 (build 8) >>???? >???? > >>???? >???? > Installation UUID: f1ca8dad-7314-419a-8a39-880ba8a71230 >>???? >???? > >>???? >???? > GTK+ 2.24.23 (Raleigh theme) >>???? >???? > >>???? >???? > Xamarin.Mac 6.18.0.23 (d16-6 / 088c73638) >>???? >???? > >>???? >???? > Package version: 612000125 >>???? >???? > >>???? >???? > === Mono Framework MDK === >>???? >???? > >>???? >???? > Runtime: >>???? >???? > >>???? >???? > Mono 6.12.0.125 (2020-02/8c552e98bd6) (64-bit) >>???? >???? > >>???? >???? > Package version: 612000125 >>???? >???? > >>???? >???? > === Roslyn (Language Service) === >>???? >???? > >>???? >???? > 3.9.0-6.21152.10+c10f884b30737542ddd84ca889a4aad9281ce210 >>???? >???? > >>???? >???? > === NuGet === >>???? >???? > >>???? >???? > Version: 5.8.0.6860 >>???? >???? > >>???? >???? > === .NET Core SDK === >>???? >???? > >>???? >???? > SDK: /usr/local/share/dotnet/sdk/5.0.202/Sdks >>???? >???? > >>???? >???? > SDK Versions: >>???? >???? > >>???? >???? > 5.0.202 >>???? >???? > >>???? >???? > 3.1.408 >>???? >???? > >>???? >???? > 2.1.4 >>???? >???? > >>???? >???? > MSBuild SDKs: /Applications/Visual Studio.app/Contents/Resources/lib/monodevelop/bin/MSBuild/ >>???? >???? > Current/bin/Sdks >>???? >???? > >>???? >???? > === .NET Core Runtime === >>???? >???? > >>???? >???? > Runtime: /usr/local/share/dotnet/dotnet >>???? >???? > >>???? >???? > Runtime Versions: >>???? >???? > >>???? >???? > 5.0.5 >>???? >???? > >>???? >???? > 3.1.14 >>???? >???? > >>???? >???? > 2.0.5 >>???? >???? > >>???? >???? > === .NET Core 3.1 SDK === >>???? >???? > >>???? >???? > SDK: 3.1.408 >>???? >???? > >>???? >???? > === Xamarin.Profiler === >>???? >???? > >>???? >???? > Version: 1.6.15.68 >>???? >???? > >>???? >???? > Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler >>???? >???? > >>???? >???? > === Updater === >>???? >???? > >>???? >???? > Version: 11 >>???? >???? > >>???? >???? > === Apple Developer Tools === >>???? >???? > >>???? >???? > Xcode 12.5 (18205) >>???? >???? > >>???? >???? > Build 12E262 >>???? >???? > >>???? >???? > === Xamarin.Mac === >>???? >???? > >>???? >???? > Xamarin.Mac not installed. Can't find /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/ >>???? >???? > Version. >>???? >???? > >>???? >???? > === Xamarin.iOS === >>???? >???? > >>???? >???? > Xamarin.iOS not installed. >>???? >???? > >>???? >???? > Can't find mtouch or the Version file at /Library/Frameworks/Xamarin.iOS.framework/Versions/ >>???? >???? > Current. >>???? >???? > >>???? >???? > === Xamarin Designer === >>???? >???? > >>???? >???? > Version: 16.9.0.324 >>???? >???? > >>???? >???? > Hash: b1e216c75 >>???? >???? > >>???? >???? > Branch: remotes/origin/d16-9 >>???? >???? > >>???? >???? > Build date: 2021-04-16 00:02:50 UTC >>???? >???? > >>???? >???? > === Xamarin.Android === >>???? >???? > >>???? >???? > Version: 11.2.2.1 (Visual Studio Community) >>???? >???? > >>???? >???? > Commit: xamarin-android/d16-9/877f572 >>???? >???? > >>???? >???? > Android SDK: /Users/ec2-user/Library/Developer/Xamarin/android-sdk-macosx >>???? >???? > >>???? >???? > Supported Android versions: >>???? >???? > >>???? >???? > None installed >>???? >???? > >>???? >???? > SDK Tools Version: 26.1.1 >>???? >???? > >>???? >???? > SDK Platform Tools Version: 30.0.4 >>???? >???? > >>???? >???? > SDK Build Tools Version: 30.0.2 >>???? >???? > >>???? >???? > Build Information: >>???? >???? > >>???? >???? > Mono: 5e9cb6d >>???? >???? > >>???? >???? > Java.Interop: xamarin/java.interop/d16-9 at 54f8c24 >>???? >???? > >>???? >???? > ProGuard: Guardsquare/proguard/v7.0.1 at 912d149 >>???? >???? > >>???? >???? > SQLite: xamarin/sqlite/3.34.1 at daff8f4 >>???? >???? > >>???? >???? > Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-9 at d210f11 >>???? >???? > >>???? >???? > === Microsoft OpenJDK for Mobile === >>???? >???? > >>???? >???? > Java SDK: /Users/ec2-user/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_1.8.0.25 >>???? >???? > >>???? >???? > 1.8.0-25 >>???? >???? > >>???? >???? > Android Designer EPL code available here: >>???? >???? > >>???? >???? > https://github.com/xamarin/AndroidDesigner.EPL > >>???? >???? > >>???? >???? > === Android SDK Manager === >>???? >???? > >>???? >???? > Version: 16.9.0.22 >>???? >???? > >>???? >???? > Hash: a391de2 >>???? >???? > >>???? >???? > Branch: remotes/origin/d16-9~2 >>???? >???? > >>???? >???? > Build date: 2021-03-24 08:30:26 UTC >>???? >???? > >>???? >???? > === Android Device Manager === >>???? >???? > >>???? >???? > Version: 16.9.0.17 >>???? >???? > >>???? >???? > Hash: fc2b3db >>???? >???? > >>???? >???? > Branch: remotes/origin/dev/jmt/d16-9bump~1 >>???? >???? > >>???? >???? > Build date: 2021-03-24 08:30:44 UTC >>???? >???? > >>???? >???? > === Build Information === >>???? >???? > >>???? >???? > Release ID: 809070008 >>???? >???? > >>???? >???? > Git revision: 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>???? >???? > >>???? >???? > Build date: 2021-04-16 07:38:03-04 >>???? >???? > >>???? >???? > Build branch: release-8.9 >>???? >???? > >>???? >???? > Xamarin extensions: 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>???? >???? > >>???? >???? > === Operating System === >>???? >???? > >>???? >???? > Mac OS X 10.16.0 >>???? >???? > >>???? >???? > Darwin 20.3.0 Darwin Kernel Version 20.3.0 >>???? >???? > >>???? >???? > Thu Jan 21 00:07:06 PST 2021 >>???? >???? > >>???? >???? > root:xnu-7195.81.3~1/RELEASE_X86_64 x86_64 >>???? >???? > >>???? >???? > Best, >>???? >???? > >>???? >???? > Niv >>???? >???? > >>???? >???? > From: Richard Levitte >>???? >???? > Date: Monday, May 3, 2021 at 4:54 AM >>???? >???? > To: Nivedita Chevvakula >>???? >???? > Cc: levitte at openssl.org , Tim Champagne , Kevin Fox >>???? >???? > >>???? >???? > Subject: Re: [fips-sponsors] Buildbot workers >>???? >???? > >>???? >???? > Hi, >>???? >???? > >>???? >???? > Thank you for offering workers to us! >>???? >???? > >>???? >???? > To be able to set up your worker, you must use version 2.6.0 or >>???? >???? > higher.? Older version do not support TLS-protected connections. >>???? >???? > >>???? >???? > Please see these instructions for installing the buildbot worker >>???? >???? > software: >>???? >???? > >>???? >???? > http://docs.buildbot.net/latest/manual/installation/worker.html > >>???? >???? > >>???? >???? > When buildbot has been installed on the platform where the buildbot >>???? >???? > worker is to be run, this is how a worker is created: >>???? >???? > >>???? >???? >???? $ buildbot-worker create-worker --use-tls BASEDIR \ >>???? >???? >???????? buildbot.openssl.org:9989 'bluecedar-01' 'Rak;osErfabOn5' >>???? >???? > >>???? >???? > where BASEDIR is determined by you.? See further down for a few notes >>???? >???? > on TLS. >>???? >???? > >>???? >???? > To run a buildbot worker, you do this: >>???? >???? > >>???? >???? >???? $ buildbot-worker start BASEDIR >>???? >???? > >>???? >???? > Apart from the software needed to run a buildbot worker, and the >>???? >???? > utilities that are the normal part of the operating system, you also >>???? >???? > need to ensure that the following components are available: >>???? >???? > >>???? >???? > -?? toolchains, i.e. C compiler, linker, make.? If you have specified >>???? >???? >???? toolchains in the worker request form, you need to ensure that all >>???? >???? >???? of them are installed. >>???? >???? > >>???? >???? > -?? git >>???? >???? > >>???? >???? > Regarding TLS, it may be that the buildbot worker platform doesn't >>???? >???? > have the appropriate certification verification roots set up.? In that >>???? >???? > case, you may need to apply the attached buildbot.tac patch, and store >>???? >???? > the attached PEM files in a directory of your choice.? Finish up by >>???? >???? > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with >>???? >???? > the path of directory where you stored the PEM files. >>???? >???? > >>???? >???? > >>???? >???? -- >>???? >???? Richard Levitte???????? levitte at openssl.org >>???? >???? OpenSSL Project http://www.openssl.org/~levitte/ >>???? -- >>???? Richard Levitte???????? levitte at openssl.org >>???? OpenSSL Project http://www.openssl.org/~levitte/ > -- > Richard Levitte???????? levitte at openssl.org > OpenSSL Project http://www.openssl.org/~levitte/ > > > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://mta.openssl.org/mailman/listinfo/buildbot-admin > From waliam at vmware.com Wed May 19 08:46:51 2021 From: waliam at vmware.com (Madhur Walia) Date: Wed, 19 May 2021 08:46:51 +0000 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <1FE019AC-49B6-4737-A1DF-E11B3345D82A@vmware.com> <87zgxcmczy.wl-levitte@openssl.org> <87zgx0qrda.wl-levitte@openssl.org> <82879104-4de9-a21b-62b7-2f2f7f8f4b70@openssl.org> , <871raaaxmx.wl-levitte@openssl.org>, Message-ID: Hi Richard, Please let us know if we need to run additional tests. Thanks & Regards, Madhur From: Madhur Walia Date: Friday, 14 May 2021 at 3:02 PM To: Richard Levitte Cc: Matt Caswell , Tim Hudson , Sunil Kumar Yadav , Manoj Maskara , Bishakha Banerjee , buildbot-admin at openssl.org Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers Hi Richard, If I set the configuration as below with correct indentation, I get an error as shown below for execfile, which in a sense means include function is successfully being called but execfile is failing, |def include(filename): | if os.path.exists(filename): | execfile(filename) | |include('env.py') Error, [Text Description automatically generated] I did some research and found that execfile function was removed in Python 3 and we are using 3.7.1. So, I used the below exec instead, which didn?t produce any execfile error. I think include and exec functions are being called now. [Graphical user interface, text, application Description automatically generated] Please let me know if this is fine. I can make the modifications you propose. Thanks & Regards, Madhur From: Richard Levitte Date: Friday, 14 May 2021 at 7:24 AM To: Madhur Walia Cc: Matt Caswell , Tim Hudson , Sunil Kumar Yadav , Manoj Maskara , Bishakha Banerjee , buildbot-admin at openssl.org Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers I can see that you have the paths set correctly in your env.py. I can also see that you've added the lines to have it included by buildbot.tac. However, there's a slight syntax error; an extra space before the 'include' call: |def include(filename): | if os.path.exists(filename): | execfile(filename) | | include('env.py') ^ Here is the extra space That extra space makes that include call part of the function definition, because it's at the same indentation level as the 'if' statement 3 lines above. This means that the include function is never actually called. Python is an annoying language in that sense, that indentation is syntactically significant. Now, unfortuantely, I don't know of any command line text editor on Windows, so I can't safely edit buildbot.tac for you. You will have to make that change. Cheers, Richard On Thu, 13 May 2021 18:16:47 +0200, Madhur Walia wrote: > > Hi Matt, > > Yes, we installed it after you emailed us which means after the test you?re referring to. New test > should be able to pick up NASM Path, > > Screenshot from Windows 2019, > > Graphical user interface, textDescription automatically generated > > Thanks & Regards, > > Madhur > > From: Matt Caswell > Date: Thursday, 13 May 2021 at 9:27 PM > To: Madhur Walia , Tim Hudson > Cc: Sunil Kumar Yadav , buildbot-admin at openssl.org > , Bishakha Banerjee , Manoj Maskara > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > On 13/05/2021 15:11, Madhur Walia wrote: > > Hi Matt, > > > > We have installed it and it?s set in %PATH% as well. > > Hmmm. Are you sure about that? > > I can see that in this build: > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F15&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538571016%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=8WKgVKhE0j13MKWM1sIy7B4PlZ4htmE9kdCMfqGju7A%3D&reserved=0 > > The Configure step is failing with: > > "NASM not found - make sure it's installed and available on %PATH%" > > Earlier the Configure step dumps out its %PATH%. Which shows it as: > > c:\users\administrator\appdata\local\programs\python\python37\lib\site-packages\pywin32_system32; > C:\Perl64\bin;C:\Users\Administrator\AppData\Roaming\ActiveState\bin;C:\Program > Files (x86)\Common > Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\ > System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\fips\fips_testing\bc\SW\Gradle_SW > \gradle-4.10.1\bin;C:\fips\fips_testing\bc\SW\Ant_SW\apache-ant-1.10.7\bin;C:\Program > Files\Java\jdk1.8.0_211\bin;C:\Program > Files\dotnet\;C:\ProgramData\Microsoft\VisualStudio\Packages;C:\Program > Files (x86)\Microsoft Visual Studio\2017\Community;C:\Program > Files\Git;C:\Program > Files\Git\bin;C:\Users\Administrator\AppData\Local\Programs\Python\Python37\Scripts\;C:\Users\ > Administrator\AppData\Local\Programs\Python\Python37\;C:\Users\Administrator\AppData\Local\ > Microsoft\WindowsApps;C:\Users\Administrator\.dotnet\tools;C:\Program > Files (x86)\Microsoft Visual > Studio\2017\Community;C:\ProgramData\Microsoft\VisualStudio\Packages;C:\Program > Files\OpenSSL-Win64\bin;C:\Program Files (x86)\Microsoft Visual > Studio\2017\Community\VC\Tools\MSVC\14.13.26128\bin\;C:\Program Files > (x86)\Microsoft Visual > Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin;C:\Program > Files (x86)\Microsoft Visual > Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja; > > I don't see anything in that %PATH% which looks like it would hold NASM > in it? > > Matt > > > > > Thanks & Regards, > > > > Madhur > > > > *From: *Matt Caswell > > *Date: *Thursday, 13 May 2021 at 7:24 PM > > *To: *Madhur Walia , Tim Hudson > > *Cc: *Sunil Kumar Yadav , > > buildbot-admin at openssl.org , Bishakha > > Banerjee , Manoj Maskara > > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > NASM is a pre-requisite for building OpenSSL. > > > > Have you installed it and is it on your %PATH%? > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.nasm.us%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538580971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=aAv6kzS2JMfvgcxbFhIgHc%2FTZpuWsjjL5huv8gKrl68%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.nasm.us%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538580971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=aAv6kzS2JMfvgcxbFhIgHc%2FTZpuWsjjL5huv8gKrl68%3D&reserved=0 > > > > > > Matt > > > > On 13/05/2021 14:02, Madhur Walia wrote: > > > Hi Tim, > > > > > > We followed your steps and seems to be hitting an error as shown, > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F13&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538580971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=X0Yl7Mnj8K5s3uZbQUeSoFtzQcBeiGjlXb1l1IHxR%2FA%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F13&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538580971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=X0Yl7Mnj8K5s3uZbQUeSoFtzQcBeiGjlXb1l1IHxR%2FA%3D&reserved=0 > > > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F13&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538580971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=X0Yl7Mnj8K5s3uZbQUeSoFtzQcBeiGjlXb1l1IHxR%2FA%3D&reserved=0 > >>. > > > > > > Our buildbot-worker location in Windows is > > > C:\Users\Administrator\Desktop\Test_buildbot. So, you will be able to > > > see the changes in buildbot.tac and env.py script as well. > > > > > > Nmake output shows as, > > > Text Description automatically generated > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > *From: *Tim Hudson > > > *Date: *Thursday, 13 May 2021 at 7:12 AM > > > *To: *Madhur Walia > > > *Cc: *Richard Levitte , Sunil Kumar Yadav > > > , Manoj Maskara , > > > buildbot-admin at openssl.org , Bishakha > > > Banerjee > > > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > You can see the current issue is that nmake isn't in the path. > > > > > > See > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F3&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538580971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=9EgwIlzgbWheMap09LZZi39imUjH9FRJ6mt2ufdL3Us%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F3&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538580971%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=9EgwIlzgbWheMap09LZZi39imUjH9FRJ6mt2ufdL3Us%3D&reserved=0 > > > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F31%2Fbuilds%2F3&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538590936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=P8VgucIzKYuJxPweJb%2FTGbyo0SFLKWijqvKa6y8QDmA%3D&reserved=0 > >> > > > > > > You need to have that setup for the buildbot worker to actually work. > > > > > > i.e. logged in as the user in windows running cmd you need to have it so > > > that "nmake" is accessible and operating correctly. > > > > > > Have you completed that step? > > > > > > There are multiple ways to set that up - and the approach I took was to > > > run the vcvars64.bat setup script from Microsoft and then dump the > > > environment and include setting a matching environment in buildbot.tac. > > > > > > You can of course copy all the environment variables into the users > > > environment. > > > > > > eng at DESKTOP-75K0EME C:\buildbot\tjh-win10-1-tls>type make-env.py > > > /import os > > > for k, v in os.environ.items(): > > > > > > print('os.environ[\''+str(k)+'\']=\''+str(v).replace('\\','\\\\')+'\'')/ > > > > > > I run that script (in a window that has had vcvars64.bat run) and > > > changed into the buildbot worker directory (where buildbot.tac exists) > > > > > > python make-env.py > env.py > > > > > > And I modified buildbot.tac to have: > > > > > > /def include(filename): > > > if os.path.exists(filename): > > > execfile(filename) > > > > > > include('env.py')/ > > > > > > That is how I setup a windows based worker configuration - the one you > > > see at > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fworkers%2F6&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538590936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ah7AZUg4pbCgyNv%2FABEeVt0TbspNu3Ou%2FSh4CDdZ2g8%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fworkers%2F6&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538590936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ah7AZUg4pbCgyNv%2FABEeVt0TbspNu3Ou%2FSh4CDdZ2g8%3D&reserved=0 > > > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fworkers%2F6&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538590936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ah7AZUg4pbCgyNv%2FABEeVt0TbspNu3Ou%2FSh4CDdZ2g8%3D&reserved=0 > >> > > > > > > Tim. > > > > > > On Wed, May 12, 2021 at 9:41 PM Madhur Walia > > >> wrote: > > > > > > Hi Richard, > > > > > > We restarted buildbot-worker in Windows 2019 and it seems to be > > > connecting now. We could see files under Base Directory as shown > > below. > > > > > > We could see couple of errors related to absence of Perl and cmake > > > in build Master Dashboard. So, we have installed them as well. > > > > > > Table Description automatically generated > > > > > > Yes, when you SSH, you will be connected to cmd.exe. One of the > > > screenshots we shared had PowerShell utility but you should be able > > > to run the commands through cmd.exe as well. We are using the same. > > > > > > Please let us know if you face any issues. > > > > > > Thanks & Regards, > > > > > > Madhur > > > > > > *From: *Richard Levitte > > >> > > > *Date: *Wednesday, 12 May 2021 at 2:08 PM > > > *To: *Madhur Walia > >> > > > *Cc: *Richard Levitte > > >>, Sunil > > Kumar Yadav > > > > >>, Manoj > > > Maskara > >>, Tim > > > Hudson > >>, > > > buildbot-admin at openssl.org > > > > > > > > >>, Bishakha Banerjee > > > > >> > > > *Subject: *Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > The winserver2019 worker did show up once! At the time, you hadn't > > > installed the python package pywin32, but when I went in looking, it > > > looked like you had. However, the winserver2019 worker isn't showing > > > up now, could it be that it needs to be restarted? > > > > > > Do note that when we SSH to the machine, we end up with a cmd.exe > > > prompt. However, the images you've sent us suggest that you run from > > > a Mingw64 prompt, and I do not know how to get there from cmd.exe, so > > > it's will need instructions to do restarts for you. > > > > > > Cheers, > > > Richard > > > > > > Right now, it looks like you need to get the winserver2019 worker > > > started. I hope it's problem free at this point. > > > > > > On Fri, 07 May 2021 09:51:22 +0200, > > > Madhur Walia wrote: > > > > > > > > Hi Richard, > > > > > > > > We are able to connect to Buildbot Master from Windows 2019 as > > > well now. To our surprise, > > > > Buildbot-worker/ Python was searching for Certificate directory > > > in base directory. > > > > > > > > After pointing ssl-root-dir to a directory hosted in base > > > directory, it was able to connect. > > > > > > > > Please confirm the connection. > > > > > > > > Also, What are the next steps for Photon 4 and Windows 2019 now? > > > > > > > > Thank you for your inputs. > > > > > > > > Regards, > > > > > > > > Madhur > > > > > > > > From: Madhur Walia > >> > > > > Date: Thursday, 6 May 2021 at 10:04 PM > > > > To: Richard Levitte > > >>, Sunil > > Kumar Yadav > > > > >> > > > > Cc: Richard Levitte > > >>, Manoj > > Maskara > > >>, Tim > > Hudson > > > > > >>, > > > buildbot-admin at openssl.org > > > > > > >> > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > Thank you Richard. So, Photon 4.0 seems to be okay for now and > > > next update would be from your > > > > development team. > > > > > > > > We captured a wireshark trace keeping default buildbot.tac and > > > could see ?Unknown CA? error. We > > > > then pointed the trustroots/ ssl-root-dir to a custom path (to > > > pem files), and encountered another > > > > error which points to failure in trusting CA certificate filepath. > > > > > > > > TextDescription automatically generated > > > > > > > > We tried pointing trustroots directory to absolute certificate > > > directory path but no luck. > > > > > > > > Other debugging steps involves, > > > > > > > > ? Running ?openssl s_client -state -debug -connect > > > buildbot.openssl.org:9989? which gives > > > > Verification: OK if we point the -CAfile to Hashed CA pem file > > > names/ location. > > > > > > > > ? Executing, a python code to verify against CA file > > > path, which shows a successful CA > > > > trust in Wireshark, > > > > > > > > import os > > > > > > > > import requests > > > > > > > > > > > > > r=requests.get(' > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538590936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=WdumwLeuN1YqFDuITV3E2EftBZGF9cIFar2bi6D%2FOhw%3D&reserved=0 > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538590936%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=WdumwLeuN1YqFDuITV3E2EftBZGF9cIFar2bi6D%2FOhw%3D&reserved=0 > >>') > > > > > > > > Graphical user interface, text, applicationDescription > > > automatically generat > > > > > > > > This either seems to be a platform, (Windows) specific issue or > > > something related to twisted OR > > > > something very miniscule that @Sunil Kumar Yadav and I are unable > > > to catch. > > > > > > > > I can schedule a call to discuss this in more depth keeping in > > > mind we are almost near to > > > > completion of 3~4 weeks window. > > > > > > > > Please let me know, Sunil and I are based out of India, IST time > > > zone. We can talk during IST > > > > evening, Your Morning. > > > > > > > > Thanks & Regards, > > > > > > > > Madhur > > > > > > > > From: Richard Levitte > > >> > > > > Date: Wednesday, 5 May 2021 at 8:37 PM > > > > To: Madhur Walia > >> > > > > Cc: Richard Levitte > > >>, Manoj > > Maskara > > >>, Tim > > Hudson > > > > > >>, Sunil Kumar Yadav > > > > >>, > > > buildbot-admin at openssl.org > > > > > > > >> > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > As far as I can tell, The Photon 4 worker is good. The fact that > > > > "make test" currently fails isn't a problem with the worker as > > far as > > > > I can see... our development team will have to look at it. > > > > > > > > As for the Windows worker, it doesn't seem to connect. Have you > > > > verified that the two .pem files are in the directory that's > > > specified > > > > in buildbot.tac? > > > > > > > > Cheers, > > > > Richard > > > > > > > > On Wed, 05 May 2021 12:11:46 +0200, > > > > Madhur Walia wrote: > > > > > > > > > > > > > > > Hi Richard, Tim, > > > > > > > > > > Awaiting further updates. Please assist. > > > > > > > > > > Thanks & Regards, > > > > > > > > > > Madhur > > > > > > > > > > From: Madhur Walia > >> > > > > > Date: Monday, 3 May 2021 at 8:18 PM > > > > > To: Richard Levitte > > >> > > > > > Cc: Manoj Maskara > > >>, Tim > > Hudson > > >>, Sunil Kumar Yadav > > > > > > >>, > > > buildbot-admin at openssl.org > > > > > > >> > > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > > > Hi Richard, > > > > > > > > > > We have installed git on Photon, please let us know next steps. > > > > > > > > > > Installed buildbot and VS2017 on Windows 2019 as shown below > > > but the connection seems to be > > > > > dropping, > > > > > > > > > > Versions installed on Windows 2019, > > > > > > > > > > TextDescription automatically generated > > > > > > > > > > Win2019: Connection Failing, going in a loop, > > > > > > > > > > Graphical user interface, textDescription automatically > > generated > > > > > > > > > > Thanks & Regards, > > > > > > > > > > Madhur > > > > > > > > > > From: Madhur Walia > >> > > > > > Date: Monday, 3 May 2021 at 2:37 PM > > > > > To: Richard Levitte > > >> > > > > > Cc: Manoj Maskara > > >>, Tim > > Hudson > > >>, Sunil Kumar Yadav > > > > > > >>, > > > buildbot-admin at openssl.org > > > > > > >> > > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > > > Hi Richard, > > > > > > > > > > Thank you for the help. We had only installed buildbot-worker > > > on Photon4 and Windows 2019. After > > > > > installing Buildbot (master) on Photon4, the worker could start. > > > > > > > > > > We are now working on installing git on Photon4 and then > > > troubleshooting Windows 2019. I will > > > > keep > > > > > you updated. > > > > > > > > > > Regards, > > > > > > > > > > Madhur > > > > > > > > > > From: Richard Levitte > > >> > > > > > Date: Monday, 3 May 2021 at 2:33 PM > > > > > To: Madhur Walia > >> > > > > > Cc: Manoj Maskara > > >>, Tim > > Hudson > > >>, Sunil Kumar Yadav > > > > > > >>, > > > buildbot-admin at openssl.org > > > > > > >> > > > > > Subject: Re: [buildbot-admin] [fips-sponsors] Buildbot workers > > > > > > > > > > I now noticed that the Photon 4 workers have connected, so I > > assume > > > > > the 'optionsForClientTLS' is a thing of the past. > > > > > > > > > > Looking at one of the builds, > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538600882%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YQhAksX0G%2BC8rm8lFYba9jhEonqbNg%2BZSNUqCgijvhI%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538600882%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YQhAksX0G%2BC8rm8lFYba9jhEonqbNg%2BZSNUqCgijvhI%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffips.buildbot.openssl.org%2F%23%2Fbuilders%2F33%2Fbuilds%2F1&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538600882%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YQhAksX0G%2BC8rm8lFYba9jhEonqbNg%2BZSNUqCgijvhI%3D&reserved=0 > >> > > > > > , > > > > > it looks like git isn't installed on the worker... > > > > > > > > > > Cheers, > > > > > Richard > > > > > > > > > > On Mon, 03 May 2021 10:34:57 +0200, > > > > > Richard Levitte wrote: > > > > > > > > > > > > On Mon, 26 Apr 2021 20:25:34 +0200, > > > > > > Madhur Walia wrote: > > > > > > > > > > > > > > Hi Matt, > > > > > > > > > > > > > > Thank you for the instructions. However, we are facing > > > couple of issues while starting > > > > > buildbot-worker, > > > > > > > > > > > > > > For both platforms, we pointed Certificate/SSL settings to > > > a custom directory in > > > > buildbot.tac > > > > > as per your recommendation. We also tried importing both > > > certs, isrg-root-xi & lets-encrypt-r3 > > > > to > > > > > trust store of OS but no luck. > > > > > > > > > > > > > > Photon, > > > > > > > Getting error, " builtins.NameError: name > > > 'optionsForClientTLS' is not defined" as > > > > shown > > > > > in Photon1 screenshot attached. > > > > > > > Also ran a curl command to check SSL connectivity, > > > seems to be failing, attached > > > > > screenshot Photon2. > > > > > > > > > > > > Please check your versions of the following packages: > > > > > > > > > > > > - buildbot (should be at least version 2.6.0) > > > > > > - twisted (should be at least version 17.9.0 according to > > > buildbot > > > > > > 2.6.0 requirements) > > > > > > > > > > > > 'optionsForClientTLS' is a method that appeared in twisted > > > version 14.0. > > > > > > > > > > > > > Windows, > > > > > > > Getting, "Unicode error" as shown in Windows1 > > > screenshot attached. > > > > > > > Also ran a curl command to check SSL connectivity, > > > seems to be failing, attached > > > > > screenshot Windows2. > > > > > > > > > > > > From the error message at the end of Windows1.png, you have > > > an invalid > > > > > > unicode character on line 30. Could it be a character with > > > diacritics > > > > > > not encoded with UTF-8? > > > > > > > > > > > > Cheers, > > > > > > Richard > > > > > > > > > > > > > Do you have any pointers on these errors? Please let us > > know. > > > > > > > > > > > > > > Thanks & Regards, > > > > > > > Madhur > > > > > > > > > > > > > > > > > ------------------------------------------------------------------ > > > > > > > > > > > > > > On 21/04/21, 4:47 PM, "Matt Caswell" > > >> wrote: > > > > > > > > > > > > > > Thanks Manoj. > > > > > > > > > > > > > > To be able to set up your worker, you must use version > > > 2.6.0 or > > > > > > > higher. Older version do not support TLS-protected > > > connections. > > > > > > > > > > > > > > Please see these instructions for installing the > > > buildbot worker > > > > > > > software: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538600882%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fGqRW2%2BtI4BXq0kmHvqd%2Fo010dNxSu%2FLBm5isMAHe3g%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538600882%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fGqRW2%2BtI4BXq0kmHvqd%2Fo010dNxSu%2FLBm5isMAHe3g%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdocs.buildbot.net%2Flatest%2Fmanual%2Finstallation%2Fworker.html&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538600882%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fGqRW2%2BtI4BXq0kmHvqd%2Fo010dNxSu%2FLBm5isMAHe3g%3D&reserved=0 > >> > > > > > > > > > > > > > > When buildbot has been installed on the platform where > > > the buildbot > > > > > > > worker is to be run, this is how a worker is created > > > (for your PhotonOS > > > > > > > worker): > > > > > > > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > > > buildbot.openssl.org:9989 > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538610838%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Mnt45BCwWJR%2B606DvDroCq19wRb0VRvYLii1rg6hK1M%3D&reserved=0 > >> > > > vmware-photonos40 nifs0Tweex_ > > > > > > > > > > > > > > And for your Windows server: > > > > > > > > > > > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ > > > > > > > buildbot.openssl.org:9989 > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbuildbot.openssl.org%3A9989%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538610838%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Mnt45BCwWJR%2B606DvDroCq19wRb0VRvYLii1rg6hK1M%3D&reserved=0 > >> > > > vmware-winserver2019 Efyin.Freg0 > > > > > > > > > > > > > > > > > > > > > where BASEDIR is determined by you. See further down > > > for a few notes > > > > > > > on TLS. > > > > > > > > > > > > > > To run a buildbot worker, you do this: > > > > > > > > > > > > > > $ buildbot-worker start BASEDIR > > > > > > > > > > > > > > Apart from the software needed to run a buildbot > > > worker, and the > > > > > > > utilities that are the normal part of the operating > > > system, you also > > > > > > > need to ensure that the following components are > > available: > > > > > > > > > > > > > > - toolchains, i.e. C compiler, linker, make. If you > > > have specified > > > > > > > toolchains in the worker request form, you need to > > > ensure that all > > > > > > > of them are installed. > > > > > > > > > > > > > > - git > > > > > > > > > > > > > > Regarding TLS, it may be that the buildbot worker > > > platform doesn't > > > > > > > have the appropriate certification verification roots > > > set up. In that > > > > > > > case, you may need to apply the attached buildbot.tac > > > patch, and store > > > > > > > the attached PEM files in a directory of your choice. > > > Finish up by > > > > > > > find the string '/PATH/TO/ssl-roots-dir' and replace > > > its contents with > > > > > > > the path of directory where you stored the PEM files. > > > > > > > > > > > > > > Matt > > > > > > > > > > > > > > On 21/04/2021 00:56, Manoj Maskara wrote: > > > > > > > > Hi Tim & Richard, > > > > > > > > > > > > > > > > We have filled out the worker-request-form for 2 of > > > our platforms, one unix type and > > > > > other Windows. Also, the platforms, for your convenience am > > > listing here: > > > > > > > > > > > > > > > > 1) Photon OS 4.0 running on ESXi 7.0 on Intel Xeon > > > Gold 6230R on Dell PowerEdge R740 > > > > > (Platform type: Unix, x86_64, build+test, gcc) > > > > > > > > 2) Windows Server 2019 running on ESXi 7.0 on Intel > > > Xeon Gold 6230R on Dell PowerEdge > > > > > R740 (Platform type: Windows, x86_64, build+test, vs2017) > > > > > > > > > > > > > > > > Please provide the credentials and instruction on > > > setting up the buildbot worker. > > > > > > > > > > > > > > > > Thanks, > > > > > > > > Manoj > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > From: fips-sponsors > > > > > > >> On Behalf Of Richard Levitte > > > > > > > > Sent: Monday, April 12, 2021 12:20 AM > > > > > > > > To: fips-sponsors at openssl.org > > > > > > > > > > > > Subject: [fips-sponsors] Buildbot workers > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > We are finally ready to start getting buildbot worker > > > requests. > > > > > > > > > > > > > > > > The way this will work is that we're asking you to > > > answer a form with details for each > > > > > worker you want to set up for us, such as what platform, what > > > architecture, and where relevant, > > > > > what toolchains are installed. > > > > > > > > > > > > > > > > The form is attached below, and include explanations > > > for all the fields to fill in. > > > > > Please send it to buildbot-admin at openssl.org > > > > >. > > > > > > > > > > > > > > > > In response, you will receive an email with the name > > > and password we assign your > > > > worker > > > > > (s), and instructions how to set the worker up. > > > > > > > > > > > > > > > > > > > > > > [2 Photon1.png ] > > > > > > > > > > > > > > [3 Photon2.png ] > > > > > > > > > > > > > > [4 Windows1.png ] > > > > > > > > > > > > > > [5 Windows2.png ] > > > > > > > > > > > > > > [6 ] > > > > > > > _______________________________________________ > > > > > > > buildbot-admin mailing list > > > > > > > buildbot-admin at openssl.org > > > > > > > > > > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538610838%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=T0y3ND%2BZhEhj6hGJ%2FUpAvy9IccJv2prps%2Faw1NRKL7M%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538610838%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=T0y3ND%2BZhEhj6hGJ%2FUpAvy9IccJv2prps%2Faw1NRKL7M%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538610838%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=T0y3ND%2BZhEhj6hGJ%2FUpAvy9IccJv2prps%2Faw1NRKL7M%3D&reserved=0 > >> > > > > > > -- > > > > > > Richard Levitte levitte at openssl.org > > > > > > > > > OpenSSL Project > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538610838%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=UkWboZ7D9Aq%2FCLovXp5cQg8DAqmOF2oF4PKJXbTCfNs%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538620796%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=f29xdRdAP%2FRfkDlnohVEmnfJfhqXgW0z4zhu6SksiAg%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538620796%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=f29xdRdAP%2FRfkDlnohVEmnfJfhqXgW0z4zhu6SksiAg%3D&reserved=0 > >> > > > > > > _______________________________________________ > > > > > > buildbot-admin mailing list > > > > > > buildbot-admin at openssl.org > > > > > > > > > > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538620796%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=mp9eetQUKRYzXB4U5ePOBGSTydZJbhdIu9Wl3gR5ZgY%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538620796%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=mp9eetQUKRYzXB4U5ePOBGSTydZJbhdIu9Wl3gR5ZgY%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538620796%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=mp9eetQUKRYzXB4U5ePOBGSTydZJbhdIu9Wl3gR5ZgY%3D&reserved=0 > >> > > > > > -- > > > > > Richard Levitte levitte at openssl.org > > > > > > > > OpenSSL Project > > > > > > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538620796%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=f29xdRdAP%2FRfkDlnohVEmnfJfhqXgW0z4zhu6SksiAg%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538630752%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ug2PAMTL%2F0EMfGFTR4iIdmzbQCW9ylOoN9E11D9uh1g%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538630752%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ug2PAMTL%2F0EMfGFTR4iIdmzbQCW9ylOoN9E11D9uh1g%3D&reserved=0 > >> > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Richard Levitte levitte at openssl.org > > > > > > > OpenSSL Project > > > > > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538630752%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ug2PAMTL%2F0EMfGFTR4iIdmzbQCW9ylOoN9E11D9uh1g%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538630752%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ug2PAMTL%2F0EMfGFTR4iIdmzbQCW9ylOoN9E11D9uh1g%3D&reserved=0 > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538630752%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ug2PAMTL%2F0EMfGFTR4iIdmzbQCW9ylOoN9E11D9uh1g%3D&reserved=0 > > > > > -- > > > Richard Levitte levitte at openssl.org > > > > > OpenSSL Project > > > > > > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538630752%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ug2PAMTL%2F0EMfGFTR4iIdmzbQCW9ylOoN9E11D9uh1g%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538630752%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=ug2PAMTL%2F0EMfGFTR4iIdmzbQCW9ylOoN9E11D9uh1g%3D&reserved=0 > > > > > > > > > > < > https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538640708%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=nx6%2FUlbYjAVKGtQOTExbwRJIImJyIo42ALV%2F5pkdwWw%3D&reserved=0 > >> > > > > > > > > > _______________________________________________ > > > buildbot-admin mailing list > > > buildbot-admin at openssl.org > > > > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538640708%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=gRgrl8FlujFp3FyaShjRLbifc7XoYR0HbauVg8tY%2BxI%3D&reserved=0 > > > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538640708%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=gRgrl8FlujFp3FyaShjRLbifc7XoYR0HbauVg8tY%2BxI%3D&reserved=0 > > > > > > > > > > [1.2 image001.png ] > [2 ] > _______________________________________________ > buildbot-admin mailing list > buildbot-admin at openssl.org > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmta.openssl.org%2Fmailman%2Flistinfo%2Fbuildbot-admin&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538640708%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=gRgrl8FlujFp3FyaShjRLbifc7XoYR0HbauVg8tY%2BxI%3D&reserved=0 -- Richard Levitte levitte at openssl.org OpenSSL Project https://nam04.safelinks.protection.outlook.com/?url=http:%2F%2Fwww.openssl.org%2F~levitte%2F&data=04%7C01%7Cwaliam%40vmware.com%7C96e09de3d7aa458528a608d9167b29ee%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637565540538640708%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=nx6%2FUlbYjAVKGtQOTExbwRJIImJyIo42ALV%2F5pkdwWw%3D&reserved=0 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1735259 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 466164 bytes Desc: image002.png URL: From ckelley at bluecedar.com Wed May 19 14:43:16 2021 From: ckelley at bluecedar.com (Connor Kelley) Date: Wed, 19 May 2021 10:43:16 -0400 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <87y2cwmc3h.wl-levitte@openssl.org> <87mttbm1gf.wl-levitte@openssl.org> <87o8dfqbwh.wl-levitte@openssl.org> <87h7iz95a2.wl-levitte@openssl.org> Message-ID: <7CC6990D-7F93-4E61-BE46-116A635AC1FA@bluecedar.com> Hi Matt, I think the PR is trivial based on what you?re talking about but I?ll be happy to fill out one of those forms if you need it. The PR for the changes is here: https://github.com/openssl/openssl/pull/15352 Thanks, -Connor > On May 19, 2021, at 3:57 AM, Matt Caswell wrote: > > Hi Connor, > > Please submit them as a pull request on our public github site: > > https://github.com/openssl/openssl/pulls > > If you email the PR number here once created then we will know to give it the attention it deserves. > > If the changes are anything other than very trivial then we will also need an ICLA from you individually, as well as a CCLA from Blue Cedar. See: > > https://www.openssl.org/policies/cla.html > > Matt > > > On 19/05/2021 01:54, Connor Kelley wrote: >> Hi Richard, >> I?ve got a working build that required a couple of updates to the 15-iOS.conf file to get it current. With those changes plus the configure invocation the build seemingly completes successfully. What is the process for submitting a PR to get those changes in and usable? >> Thanks, >> -Connor >> Get Outlook for iOS >> ------------------------------------------------------------------------ >> *From:* Richard Levitte >> *Sent:* Tuesday, May 18, 2021 4:05:25 PM >> *To:* Nivedita Chevvakula >> *Cc:* Richard Levitte ; Tim Champagne ; Connor Kelley ; buildbot-admin at openssl.org >> *Subject:* Re: [fips-sponsors] Buildbot workers >> [ Also adding buildbot-admin at openssl.org (I should have done that long ago) ] >> Yes, some technical details is what I'm trying to get. >> Right now, that worker is building, sure, but that's a MacOS build, >> which wasn't what you wanted. >> So Tim, Connor, if you have something to share, I can hopefully do >> better progress on our end. >> Cheers, >> Richard >> On Mon, 17 May 2021 15:28:50 +0200, >> Nivedita Chevvakula wrote: >>> On this buildbot slave we don't run any our projects, we have set this slave only for buildbot worker. Please let me know if I give ssh creds it will expedite the process. >>> Also adding Connor and Timmy, hopefully they can clarify on how we build OpenSSL project. >>> Best, >>> Niv >>> ?On 5/13/21, 4:24 AM, "Richard Levitte" wrote: >>> What we expect to do is this at a minimum: >>> perl Configure {args...} >>> make >>> In the form that you filled in, there was the option to specify >>> necessary environment variables (which can affect the configuration >>> step) and configuration options. I was hoping that would be enough to >>> get something going. >>> I do not know what you're talking about regarding a .conf file created >>> by the Configure step. I understand that you have some sort of super >>> project that involves building OpenSSL as a component, though, so I >>> can only assume that somewhere in there, it should be possible to find >>> how the OpenSSL part is configured, i.e. I assume that there is a run >>> of Configure hiding in there somewhere, and that it should be possible >>> to see what arguments are used, as well as any relevant environment >>> variables. >>> Does this answer your question? >>> Cheers, >>> Richard >>> On Fri, 07 May 2021 15:12:11 +0200, >>> Nivedita Chevvakula wrote: >>> > > We generate a project using cmake that gets built as a dependency of other components in our project. If you are trying to do - build everything using make, which requires a .conf file created with ./Configure step. If so should have one of those somewhere that satisfies what you are looking to produce for iOS, as well as a >> different one for Android, please provide that we can put it in place on the build bot and just use that? >>> > > Please advise. >>> > > Best, >>> > Niv >>> > > ?On 5/4/21, 2:56 AM, "Richard Levitte" wrote: >>> > > Hi, >>> > > The worker is connecting fine, so far so good. >>> > > However, I realised that there are things missing, where we need >>> > information from you! >>> > > This worker is meant to build for iOS, is it not? That should require >>> > extra OpenSSL configuration options. So let me ask you this, when you >>> > usually build OpenSSL for iOS, exactly how do you usually configure >>> > OpenSSL? >>> > > Cheers, >>> > Richard >>> > > On Tue, 04 May 2021 03:46:17 +0200, >>> > Nivedita Chevvakula wrote: >>> > > > > Richard, >>> > > > > You can ignore my last mail with error starting buildbot. It is seems to work now after editing >>> > > syntax for python2.7. Also we have created user ?buildbot? for this mac as recommended. Please let >>> > > me know if we need to pass those credentials or need to setup anything else for the build bot. >>> > > > > Best, >>> > > > > Niv >>> > > > > From: Nivedita Chevvakula >>> > > Date: Monday, May 3, 2021 at 6:44 PM >>> > > To: Richard Levitte >>> > > Subject: Re: [fips-sponsors] Buildbot workers >>> > > > > Richard, >>> > > > > Buildbot has now installed with linker, make, c compilers. >>> > > > > While starting the worker to connect to master after editing tac file as you mentioned getting >>> > > syntax error . not able to pin point why. Attaching the error log and the tac file here. Could you >>> > > please help. >>> > > > > Best, >>> > > > > Niv >>> > > > > From: Nivedita Chevvakula >>> > > Date: Monday, May 3, 2021 at 9:22 AM >>> > > To: Richard Levitte >>> > > Cc: "levitte at openssl.org" , Tim Champagne , Kevin >>> > > Fox >>> > > Subject: Re: [fips-sponsors] Buildbot workers >>> > > > > Hi Richard, >>> > > > > Thank you for sending the worker bot setup requirements, I will go thru and will set up the >>> > > workerbot and will install the rest. Do you have any deadline for this setup please share so that >>> > > it will help me prioritize. >>> > > > > So far these tools are installed over the mac : >>> > > > > 1. Android Studio 4.1.3 >>> > > 2. Xcode 12.5 >>> > > 3. clang version 12.0.5 > > 4. Gcc >>> > > 5. Visual Studio Community 2019 for Mac >>> > > > > === Visual Studio Community 2019 for Mac === >>> > > > > Version 8.9.7 (build 8) >>> > > > > Installation UUID: f1ca8dad-7314-419a-8a39-880ba8a71230 >>> > > > > GTK+ 2.24.23 (Raleigh theme) >>> > > > > Xamarin.Mac 6.18.0.23 (d16-6 / 088c73638) >>> > > > > Package version: 612000125 >>> > > > > === Mono Framework MDK === >>> > > > > Runtime: >>> > > > > Mono 6.12.0.125 (2020-02/8c552e98bd6) (64-bit) >>> > > > > Package version: 612000125 >>> > > > > === Roslyn (Language Service) === >>> > > > > 3.9.0-6.21152.10+c10f884b30737542ddd84ca889a4aad9281ce210 >>> > > > > === NuGet === >>> > > > > Version: 5.8.0.6860 >>> > > > > === .NET Core SDK === >>> > > > > SDK: /usr/local/share/dotnet/sdk/5.0.202/Sdks >>> > > > > SDK Versions: >>> > > > > 5.0.202 >>> > > > > 3.1.408 >>> > > > > 2.1.4 >>> > > > > MSBuild SDKs: /Applications/Visual Studio.app/Contents/Resources/lib/monodevelop/bin/MSBuild/ >>> > > Current/bin/Sdks >>> > > > > === .NET Core Runtime === >>> > > > > Runtime: /usr/local/share/dotnet/dotnet >>> > > > > Runtime Versions: >>> > > > > 5.0.5 >>> > > > > 3.1.14 >>> > > > > 2.0.5 >>> > > > > === .NET Core 3.1 SDK === >>> > > > > SDK: 3.1.408 >>> > > > > === Xamarin.Profiler === >>> > > > > Version: 1.6.15.68 >>> > > > > Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler >>> > > > > === Updater === >>> > > > > Version: 11 >>> > > > > === Apple Developer Tools === >>> > > > > Xcode 12.5 (18205) >>> > > > > Build 12E262 >>> > > > > === Xamarin.Mac === >>> > > > > Xamarin.Mac not installed. Can't find /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/ >>> > > Version. >>> > > > > === Xamarin.iOS === >>> > > > > Xamarin.iOS not installed. >>> > > > > Can't find mtouch or the Version file at /Library/Frameworks/Xamarin.iOS.framework/Versions/ >>> > > Current. >>> > > > > === Xamarin Designer === >>> > > > > Version: 16.9.0.324 >>> > > > > Hash: b1e216c75 >>> > > > > Branch: remotes/origin/d16-9 >>> > > > > Build date: 2021-04-16 00:02:50 UTC >>> > > > > === Xamarin.Android === >>> > > > > Version: 11.2.2.1 (Visual Studio Community) >>> > > > > Commit: xamarin-android/d16-9/877f572 >>> > > > > Android SDK: /Users/ec2-user/Library/Developer/Xamarin/android-sdk-macosx >>> > > > > Supported Android versions: >>> > > > > None installed >>> > > > > SDK Tools Version: 26.1.1 >>> > > > > SDK Platform Tools Version: 30.0.4 >>> > > > > SDK Build Tools Version: 30.0.2 >>> > > > > Build Information: >>> > > > > Mono: 5e9cb6d >>> > > > > Java.Interop: xamarin/java.interop/d16-9 at 54f8c24 >>> > > > > ProGuard: Guardsquare/proguard/v7.0.1 at 912d149 >>> > > > > SQLite: xamarin/sqlite/3.34.1 at daff8f4 >>> > > > > Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-9 at d210f11 >>> > > > > === Microsoft OpenJDK for Mobile === >>> > > > > Java SDK: /Users/ec2-user/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_1.8.0.25 >>> > > > > 1.8.0-25 >>> > > > > Android Designer EPL code available here: >>> > > > > https://github.com/xamarin/AndroidDesigner.EPL >> >>> > > > > === Android SDK Manager === >>> > > > > Version: 16.9.0.22 >>> > > > > Hash: a391de2 >>> > > > > Branch: remotes/origin/d16-9~2 >>> > > > > Build date: 2021-03-24 08:30:26 UTC >>> > > > > === Android Device Manager === >>> > > > > Version: 16.9.0.17 >>> > > > > Hash: fc2b3db >>> > > > > Branch: remotes/origin/dev/jmt/d16-9bump~1 >>> > > > > Build date: 2021-03-24 08:30:44 UTC >>> > > > > === Build Information === >>> > > > > Release ID: 809070008 >>> > > > > Git revision: 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>> > > > > Build date: 2021-04-16 07:38:03-04 >>> > > > > Build branch: release-8.9 >>> > > > > Xamarin extensions: 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>> > > > > === Operating System === >>> > > > > Mac OS X 10.16.0 >>> > > > > Darwin 20.3.0 Darwin Kernel Version 20.3.0 >>> > > > > Thu Jan 21 00:07:06 PST 2021 >>> > > > > root:xnu-7195.81.3~1/RELEASE_X86_64 x86_64 >>> > > > > Best, >>> > > > > Niv >>> > > > > From: Richard Levitte >>> > > Date: Monday, May 3, 2021 at 4:54 AM >>> > > To: Nivedita Chevvakula >>> > > Cc: levitte at openssl.org , Tim Champagne , Kevin Fox >>> > > >>> > > Subject: Re: [fips-sponsors] Buildbot workers >>> > > > > Hi, >>> > > > > Thank you for offering workers to us! >>> > > > > To be able to set up your worker, you must use version 2.6.0 or >>> > > higher. Older version do not support TLS-protected connections. >>> > > > > Please see these instructions for installing the buildbot worker >>> > > software: >>> > > > > http://docs.buildbot.net/latest/manual/installation/worker.html >> >>> > > > > When buildbot has been installed on the platform where the buildbot >>> > > worker is to be run, this is how a worker is created: >>> > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ >>> > > buildbot.openssl.org:9989 'bluecedar-01' 'Rak;osErfabOn5' >>> > > > > where BASEDIR is determined by you. See further down for a few notes >>> > > on TLS. >>> > > > > To run a buildbot worker, you do this: >>> > > > > $ buildbot-worker start BASEDIR >>> > > > > Apart from the software needed to run a buildbot worker, and the >>> > > utilities that are the normal part of the operating system, you also >>> > > need to ensure that the following components are available: >>> > > > > - toolchains, i.e. C compiler, linker, make. If you have specified >>> > > toolchains in the worker request form, you need to ensure that all >>> > > of them are installed. >>> > > > > - git >>> > > > > Regarding TLS, it may be that the buildbot worker platform doesn't >>> > > have the appropriate certification verification roots set up. In that >>> > > case, you may need to apply the attached buildbot.tac patch, and store >>> > > the attached PEM files in a directory of your choice. Finish up by >>> > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with >>> > > the path of directory where you stored the PEM files. >>> > > > > > -- > Richard Levitte levitte at openssl.org >>> > OpenSSL Project http://www.openssl.org/~levitte/ >>> -- Richard Levitte levitte at openssl.org >>> OpenSSL Project http://www.openssl.org/~levitte/ >> -- >> Richard Levitte levitte at openssl.org >> OpenSSL Project http://www.openssl.org/~levitte/ >> _______________________________________________ >> buildbot-admin mailing list >> buildbot-admin at openssl.org >> https://mta.openssl.org/mailman/listinfo/buildbot-admin -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt at openssl.org Wed May 19 14:59:17 2021 From: matt at openssl.org (Matt Caswell) Date: Wed, 19 May 2021 15:59:17 +0100 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: <7CC6990D-7F93-4E61-BE46-116A635AC1FA@bluecedar.com> References: <87k0p89dfr.wl-levitte@openssl.org> <87y2cwmc3h.wl-levitte@openssl.org> <87mttbm1gf.wl-levitte@openssl.org> <87o8dfqbwh.wl-levitte@openssl.org> <87h7iz95a2.wl-levitte@openssl.org> <7CC6990D-7F93-4E61-BE46-116A635AC1FA@bluecedar.com> Message-ID: <2a669cf9-d629-da3c-e386-ac4da9c5677a@openssl.org> Thanks Connor...lets continue the conversation in the PR itself. Matt On 19/05/2021 15:43, Connor Kelley wrote: > Hi Matt, > I think the PR is trivial based on what you?re talking about but I?ll be > happy to fill out one of those forms if you need it. > The PR for the changes is here: > https://github.com/openssl/openssl/pull/15352 > > > Thanks, > -Connor > >> On May 19, 2021, at 3:57 AM, Matt Caswell > > wrote: >> >> Hi Connor, >> >> Please submit them as a pull request on our public github site: >> >> https://github.com/openssl/openssl/pulls >> >> >> If you email the PR number here once created then we will know to give >> it the attention it deserves. >> >> If the changes are anything other than very trivial then we will also >> need an ICLA from you individually, as well as a CCLA from Blue Cedar. >> See: >> >> https://www.openssl.org/policies/cla.html >> >> Matt >> >> >> On 19/05/2021 01:54, Connor Kelley wrote: >>> Hi Richard, >>> I?ve got a working build that required a couple of updates to the >>> 15-iOS.conf file to get it current. With those changes plus the >>> configure invocation the build seemingly completes successfully. What >>> is the process for submitting a PR to get those changes in and usable? >>> Thanks, >>> -Connor >>> Get Outlook for iOS >>> ------------------------------------------------------------------------ >>> *From:* Richard Levitte >>> *Sent:* Tuesday, May 18, 2021 4:05:25 PM >>> *To:* Nivedita Chevvakula >>> *Cc:* Richard Levitte ; Tim Champagne >>> ; Connor Kelley ; >>> buildbot-admin at openssl.org >>> *Subject:* Re: [fips-sponsors] Buildbot workers >>> [ Also adding buildbot-admin at openssl.org (I should have done that >>> long ago) ] >>> Yes, some technical details is what I'm trying to get. >>> Right now, that worker is building, sure, but that's a MacOS build, >>> which wasn't what you wanted. >>> So Tim, Connor, if you have something to share, I can hopefully do >>> better progress on our end. >>> Cheers, >>> Richard >>> On Mon, 17 May 2021 15:28:50 +0200, >>> Nivedita Chevvakula wrote: >>>> On this buildbot slave we don't run any our projects, we have set >>>> this slave only for buildbot worker. Please let me know if I give >>>> ssh creds it will expedite the process. >>>> Also adding Connor and Timmy, hopefully they can clarify on how we >>>> build OpenSSL project. >>>> Best, >>>> Niv >>>> ?On 5/13/21, 4:24 AM, "Richard Levitte" wrote: >>>> ???? What we expect to do is this at a minimum: >>>> ???????? perl Configure {args...} >>>> ???????? make >>>> ???? In the form that you filled in, there was the option to specify >>>> ???? necessary environment variables (which can affect the configuration >>>> ???? step) and configuration options.? I was hoping that would be >>>> enough to >>>> ???? get something going. >>>> ???? I do not know what you're talking about regarding a .conf file >>>> created >>>> ???? by the Configure step.? I understand that you have some sort of >>>> super >>>> ???? project that involves building OpenSSL as a component, though, so I >>>> ???? can only assume that somewhere in there, it should be possible >>>> to find >>>> ???? how the OpenSSL part is configured, i.e. I assume that there is >>>> a run >>>> ???? of Configure hiding in there somewhere, and that it should be >>>> possible >>>> ???? to see what arguments are used, as well as any relevant environment >>>> ???? variables. >>>> ???? Does this answer your question? >>>> ???? Cheers, >>>> ???? Richard >>>> ???? On Fri, 07 May 2021 15:12:11 +0200, >>>> ???? Nivedita Chevvakula wrote: >>>> ???? > ???? > We generate a project using cmake that gets built as a >>>> dependency of other components in our project. If you are trying to >>>> do - build everything using make, which requires a .conf file >>>> created with ./Configure step. If so should have one of those >>>> somewhere ?that satisfies what you are looking to produce for iOS, >>>> as well as a >>> different one for Android, please provide that we can put it in place >>> on the build bot and just use that? >>>> ???? > ???? > Please advise. >>>> ???? > ???? > Best, >>>> ???? > Niv >>>> ???? > ???? > ?On 5/4/21, 2:56 AM, "Richard Levitte" >>>> wrote: >>>> ???? > ???? >???? Hi, >>>> ???? > ???? >???? The worker is connecting fine, so far so good. >>>> ???? > ???? >???? However, I realised that there are things missing, >>>> where we need >>>> ???? >???? information from you! >>>> ???? > ???? >???? This worker is meant to build for iOS, is it not? >>>> That should require >>>> ???? >???? extra OpenSSL configuration options.? So let me ask you >>>> this, when you >>>> ???? >???? usually build OpenSSL for iOS, exactly how do you usually >>>> configure >>>> ???? >???? OpenSSL? >>>> ???? > ???? >???? Cheers, >>>> ???? >???? Richard >>>> ???? > ???? >???? On Tue, 04 May 2021 03:46:17 +0200, >>>> ???? >???? Nivedita Chevvakula wrote: >>>> ???? >???? > ???? >???? > Richard, >>>> ???? >???? > ???? >???? > You can ignore my last mail with error >>>> starting buildbot. It is seems to work now after editing >>>> ???? >???? > syntax for python2.7. Also we have created user >>>> ?buildbot? for this mac as recommended. Please let >>>> ???? >???? > me know if we need to pass those credentials or need to >>>> setup anything else for the build bot. >>>> ???? >???? > ???? >???? > Best, >>>> ???? >???? > ???? >???? > Niv >>>> ???? >???? > ???? >???? > From: Nivedita Chevvakula >>>> >>>> ???? >???? > Date: Monday, May 3, 2021 at 6:44 PM >>>> ???? >???? > To: Richard Levitte >>>> ???? >???? > Subject: Re: [fips-sponsors] Buildbot workers >>>> ???? >???? > ???? >???? > Richard, >>>> ???? >???? > ???? >???? > Buildbot has now installed with linker, >>>> make, c compilers. >>>> ???? >???? > ???? >???? > While starting the worker to connect to >>>> master after editing tac file as you mentioned getting >>>> ???? >???? > syntax error . not able to pin point why. Attaching the >>>> error log and the tac file here. Could you >>>> ???? >???? > please help. >>>> ???? >???? > ???? >???? > Best, >>>> ???? >???? > ???? >???? > Niv >>>> ???? >???? > ???? >???? > From: Nivedita Chevvakula >>>> >>>> ???? >???? > Date: Monday, May 3, 2021 at 9:22 AM >>>> ???? >???? > To: Richard Levitte >>>> ???? >???? > Cc: "levitte at openssl.org" , Tim >>>> Champagne , Kevin >>>> ???? >???? > Fox >>>> ???? >???? > Subject: Re: [fips-sponsors] Buildbot workers >>>> ???? >???? > ???? >???? > Hi Richard, >>>> ???? >???? > ???? >???? > Thank you for sending the worker bot setup >>>> requirements, I will go thru and will set up the >>>> ???? >???? > workerbot and will install the rest. Do you have any >>>> deadline for this setup please share so that >>>> ???? >???? > it will help me prioritize. >>>> ???? >???? > ???? >???? > So far these tools are installed over the >>>> mac : >>>> ???? >???? > ???? >???? >? 1. Android Studio 4.1.3 >>>> ???? >???? >? 2. Xcode 12.5 >>>> ???? >???? >? 3. clang version 12.0.5 ???? >???? >? 4. Gcc >>>> ???? >???? >? 5. Visual Studio Community 2019 for Mac >>>> ???? >???? > ???? >???? > === Visual Studio Community 2019 for Mac === >>>> ???? >???? > ???? >???? > Version 8.9.7 (build 8) >>>> ???? >???? > ???? >???? > Installation UUID: >>>> f1ca8dad-7314-419a-8a39-880ba8a71230 >>>> ???? >???? > ???? >???? > GTK+ 2.24.23 (Raleigh theme) >>>> ???? >???? > ???? >???? > Xamarin.Mac 6.18.0.23 (d16-6 / 088c73638) >>>> ???? >???? > ???? >???? > Package version: 612000125 >>>> ???? >???? > ???? >???? > === Mono Framework MDK === >>>> ???? >???? > ???? >???? > Runtime: >>>> ???? >???? > ???? >???? > Mono 6.12.0.125 (2020-02/8c552e98bd6) (64-bit) >>>> ???? >???? > ???? >???? > Package version: 612000125 >>>> ???? >???? > ???? >???? > === Roslyn (Language Service) === >>>> ???? >???? > ???? >???? > >>>> 3.9.0-6.21152.10+c10f884b30737542ddd84ca889a4aad9281ce210 >>>> ???? >???? > ???? >???? > === NuGet === >>>> ???? >???? > ???? >???? > Version: 5.8.0.6860 >>>> ???? >???? > ???? >???? > === .NET Core SDK === >>>> ???? >???? > ???? >???? > SDK: /usr/local/share/dotnet/sdk/5.0.202/Sdks >>>> ???? >???? > ???? >???? > SDK Versions: >>>> ???? >???? > ???? >???? > 5.0.202 >>>> ???? >???? > ???? >???? > 3.1.408 >>>> ???? >???? > ???? >???? > 2.1.4 >>>> ???? >???? > ???? >???? > MSBuild SDKs: /Applications/Visual >>>> Studio.app/Contents/Resources/lib/monodevelop/bin/MSBuild/ >>>> ???? >???? > Current/bin/Sdks >>>> ???? >???? > ???? >???? > === .NET Core Runtime === >>>> ???? >???? > ???? >???? > Runtime: /usr/local/share/dotnet/dotnet >>>> ???? >???? > ???? >???? > Runtime Versions: >>>> ???? >???? > ???? >???? > 5.0.5 >>>> ???? >???? > ???? >???? > 3.1.14 >>>> ???? >???? > ???? >???? > 2.0.5 >>>> ???? >???? > ???? >???? > === .NET Core 3.1 SDK === >>>> ???? >???? > ???? >???? > SDK: 3.1.408 >>>> ???? >???? > ???? >???? > === Xamarin.Profiler === >>>> ???? >???? > ???? >???? > Version: 1.6.15.68 >>>> ???? >???? > ???? >???? > Location: /Applications/Xamarin >>>> Profiler.app/Contents/MacOS/Xamarin Profiler >>>> ???? >???? > ???? >???? > === Updater === >>>> ???? >???? > ???? >???? > Version: 11 >>>> ???? >???? > ???? >???? > === Apple Developer Tools === >>>> ???? >???? > ???? >???? > Xcode 12.5 (18205) >>>> ???? >???? > ???? >???? > Build 12E262 >>>> ???? >???? > ???? >???? > === Xamarin.Mac === >>>> ???? >???? > ???? >???? > Xamarin.Mac not installed. Can't find >>>> /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/ >>>> ???? >???? > Version. >>>> ???? >???? > ???? >???? > === Xamarin.iOS === >>>> ???? >???? > ???? >???? > Xamarin.iOS not installed. >>>> ???? >???? > ???? >???? > Can't find mtouch or the Version file at >>>> /Library/Frameworks/Xamarin.iOS.framework/Versions/ >>>> ???? >???? > Current. >>>> ???? >???? > ???? >???? > === Xamarin Designer === >>>> ???? >???? > ???? >???? > Version: 16.9.0.324 >>>> ???? >???? > ???? >???? > Hash: b1e216c75 >>>> ???? >???? > ???? >???? > Branch: remotes/origin/d16-9 >>>> ???? >???? > ???? >???? > Build date: 2021-04-16 00:02:50 UTC >>>> ???? >???? > ???? >???? > === Xamarin.Android === >>>> ???? >???? > ???? >???? > Version: 11.2.2.1 (Visual Studio Community) >>>> ???? >???? > ???? >???? > Commit: xamarin-android/d16-9/877f572 >>>> ???? >???? > ???? >???? > Android SDK: >>>> /Users/ec2-user/Library/Developer/Xamarin/android-sdk-macosx >>>> ???? >???? > ???? >???? > Supported Android versions: >>>> ???? >???? > ???? >???? > None installed >>>> ???? >???? > ???? >???? > SDK Tools Version: 26.1.1 >>>> ???? >???? > ???? >???? > SDK Platform Tools Version: 30.0.4 >>>> ???? >???? > ???? >???? > SDK Build Tools Version: 30.0.2 >>>> ???? >???? > ???? >???? > Build Information: >>>> ???? >???? > ???? >???? > Mono: 5e9cb6d >>>> ???? >???? > ???? >???? > Java.Interop: >>>> xamarin/java.interop/d16-9 at 54f8c24 >>>> ???? >???? > ???? >???? > ProGuard: Guardsquare/proguard/v7.0.1 at 912d149 >>>> ???? >???? > ???? >???? > SQLite: xamarin/sqlite/3.34.1 at daff8f4 >>>> ???? >???? > ???? >???? > Xamarin.Android Tools: >>>> xamarin/xamarin-android-tools/d16-9 at d210f11 >>>> ???? >???? > ???? >???? > === Microsoft OpenJDK for Mobile === >>>> ???? >???? > ???? >???? > Java SDK: >>>> /Users/ec2-user/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_1.8.0.25 >>>> ???? >???? > ???? >???? > 1.8.0-25 >>>> ???? >???? > ???? >???? > Android Designer EPL code available here: >>>> ???? >???? > ???? >???? > >>>> https://github.com/xamarin/AndroidDesigner.EPL >>> >>>> ???? >???? > ???? >???? > === Android SDK Manager === >>>> ???? >???? > ???? >???? > Version: 16.9.0.22 >>>> ???? >???? > ???? >???? > Hash: a391de2 >>>> ???? >???? > ???? >???? > Branch: remotes/origin/d16-9~2 >>>> ???? >???? > ???? >???? > Build date: 2021-03-24 08:30:26 UTC >>>> ???? >???? > ???? >???? > === Android Device Manager === >>>> ???? >???? > ???? >???? > Version: 16.9.0.17 >>>> ???? >???? > ???? >???? > Hash: fc2b3db >>>> ???? >???? > ???? >???? > Branch: remotes/origin/dev/jmt/d16-9bump~1 >>>> ???? >???? > ???? >???? > Build date: 2021-03-24 08:30:44 UTC >>>> ???? >???? > ???? >???? > === Build Information === >>>> ???? >???? > ???? >???? > Release ID: 809070008 >>>> ???? >???? > ???? >???? > Git revision: >>>> 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>>> ???? >???? > ???? >???? > Build date: 2021-04-16 07:38:03-04 >>>> ???? >???? > ???? >???? > Build branch: release-8.9 >>>> ???? >???? > ???? >???? > Xamarin extensions: >>>> 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>>> ???? >???? > ???? >???? > === Operating System === >>>> ???? >???? > ???? >???? > Mac OS X 10.16.0 >>>> ???? >???? > ???? >???? > Darwin 20.3.0 Darwin Kernel Version 20.3.0 >>>> ???? >???? > ???? >???? > Thu Jan 21 00:07:06 PST 2021 >>>> ???? >???? > ???? >???? > root:xnu-7195.81.3~1/RELEASE_X86_64 x86_64 >>>> ???? >???? > ???? >???? > Best, >>>> ???? >???? > ???? >???? > Niv >>>> ???? >???? > ???? >???? > From: Richard Levitte >>>> ???? >???? > Date: Monday, May 3, 2021 at 4:54 AM >>>> ???? >???? > To: Nivedita Chevvakula >>>> ???? >???? > Cc: levitte at openssl.org , Tim >>>> Champagne , Kevin Fox >>>> ???? >???? > >>>> ???? >???? > Subject: Re: [fips-sponsors] Buildbot workers >>>> ???? >???? > ???? >???? > Hi, >>>> ???? >???? > ???? >???? > Thank you for offering workers to us! >>>> ???? >???? > ???? >???? > To be able to set up your worker, you must >>>> use version 2.6.0 or >>>> ???? >???? > higher.? Older version do not support TLS-protected >>>> connections. >>>> ???? >???? > ???? >???? > Please see these instructions for >>>> installing the buildbot worker >>>> ???? >???? > software: >>>> ???? >???? > ???? >???? > >>>> ????http://docs.buildbot.net/latest/manual/installation/worker.html >>> >>>> ???? >???? > ???? >???? > When buildbot has been installed on the >>>> platform where the buildbot >>>> ???? >???? > worker is to be run, this is how a worker is created: >>>> ???? >???? > ???? >???? >???? $ buildbot-worker create-worker >>>> --use-tls BASEDIR \ >>>> ???? >???? >???????? buildbot.openssl.org:9989 'bluecedar-01' >>>> 'Rak;osErfabOn5' >>>> ???? >???? > ???? >???? > where BASEDIR is determined by you.? See >>>> further down for a few notes >>>> ???? >???? > on TLS. >>>> ???? >???? > ???? >???? > To run a buildbot worker, you do this: >>>> ???? >???? > ???? >???? >???? $ buildbot-worker start BASEDIR >>>> ???? >???? > ???? >???? > Apart from the software needed to run a >>>> buildbot worker, and the >>>> ???? >???? > utilities that are the normal part of the operating >>>> system, you also >>>> ???? >???? > need to ensure that the following components are available: >>>> ???? >???? > ???? >???? > -?? toolchains, i.e. C compiler, linker, >>>> make.? If you have specified >>>> ???? >???? >???? toolchains in the worker request form, you need to >>>> ensure that all >>>> ???? >???? >???? of them are installed. >>>> ???? >???? > ???? >???? > -?? git >>>> ???? >???? > ???? >???? > Regarding TLS, it may be that the buildbot >>>> worker platform doesn't >>>> ???? >???? > have the appropriate certification verification roots >>>> set up.? In that >>>> ???? >???? > case, you may need to apply the attached buildbot.tac >>>> patch, and store >>>> ???? >???? > the attached PEM files in a directory of your choice. >>>> Finish up by >>>> ???? >???? > find the string '/PATH/TO/ssl-roots-dir' and replace >>>> its contents with >>>> ???? >???? > the path of directory where you stored the PEM files. >>>> ???? >???? > ???? >???? > ???? >???? -- ???? >???? Richard >>>> Levitte???????? levitte at openssl.org >>>> ???? >???? OpenSSL Project ????????http://www.openssl.org/~levitte/ >>>> >>>> ???? -- ???? Richard Levitte???????? levitte at openssl.org >>>> ???? OpenSSL Project ????????http://www.openssl.org/~levitte/ >>>> >>> -- >>> Richard Levitte???????? levitte at openssl.org >>> OpenSSL Project http://www.openssl.org/~levitte/ >>> >>> _______________________________________________ >>> buildbot-admin mailing list >>> buildbot-admin at openssl.org >>> https://mta.openssl.org/mailman/listinfo/buildbot-admin > From ckelley at bluecedar.com Thu May 20 16:48:17 2021 From: ckelley at bluecedar.com (Connor Kelley) Date: Thu, 20 May 2021 12:48:17 -0400 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: <2a669cf9-d629-da3c-e386-ac4da9c5677a@openssl.org> References: <87k0p89dfr.wl-levitte@openssl.org> <87y2cwmc3h.wl-levitte@openssl.org> <87mttbm1gf.wl-levitte@openssl.org> <87o8dfqbwh.wl-levitte@openssl.org> <87h7iz95a2.wl-levitte@openssl.org> <7CC6990D-7F93-4E61-BE46-116A635AC1FA@bluecedar.com> <2a669cf9-d629-da3c-e386-ac4da9c5677a@openssl.org> Message-ID: Hi Matt, After pulling in the fixes for the broken assembly fixes I was able to successfully build without any of the .conf changes so I was able to cancel the PR. Using top of tree I was able to successfully build and arm64 target with ./Configure ios64-xcrun enable-fips enable-fips-securitychecks -mios-version-min=11.0 && make Thanks, -Connor > On May 19, 2021, at 10:59 AM, Matt Caswell wrote: > > Thanks Connor...lets continue the conversation in the PR itself. > > Matt > > On 19/05/2021 15:43, Connor Kelley wrote: >> Hi Matt, >> I think the PR is trivial based on what you?re talking about but I?ll be happy to fill out one of those forms if you need it. >> The PR for the changes is here: https://github.com/openssl/openssl/pull/15352 >> Thanks, >> -Connor >>> On May 19, 2021, at 3:57 AM, Matt Caswell > wrote: >>> >>> Hi Connor, >>> >>> Please submit them as a pull request on our public github site: >>> >>> https://github.com/openssl/openssl/pulls >>> >>> If you email the PR number here once created then we will know to give it the attention it deserves. >>> >>> If the changes are anything other than very trivial then we will also need an ICLA from you individually, as well as a CCLA from Blue Cedar. See: >>> >>> https://www.openssl.org/policies/cla.html >>> >>> Matt >>> >>> >>> On 19/05/2021 01:54, Connor Kelley wrote: >>>> Hi Richard, >>>> I?ve got a working build that required a couple of updates to the 15-iOS.conf file to get it current. With those changes plus the configure invocation the build seemingly completes successfully. What is the process for submitting a PR to get those changes in and usable? >>>> Thanks, >>>> -Connor >>>> Get Outlook for iOS >>>> ------------------------------------------------------------------------ >>>> *From:* Richard Levitte >>>> *Sent:* Tuesday, May 18, 2021 4:05:25 PM >>>> *To:* Nivedita Chevvakula >>>> *Cc:* Richard Levitte ; Tim Champagne ; Connor Kelley ; buildbot-admin at openssl.org >>>> *Subject:* Re: [fips-sponsors] Buildbot workers >>>> [ Also adding buildbot-admin at openssl.org (I should have done that long ago) ] >>>> Yes, some technical details is what I'm trying to get. >>>> Right now, that worker is building, sure, but that's a MacOS build, >>>> which wasn't what you wanted. >>>> So Tim, Connor, if you have something to share, I can hopefully do >>>> better progress on our end. >>>> Cheers, >>>> Richard >>>> On Mon, 17 May 2021 15:28:50 +0200, >>>> Nivedita Chevvakula wrote: >>>>> On this buildbot slave we don't run any our projects, we have set this slave only for buildbot worker. Please let me know if I give ssh creds it will expedite the process. >>>>> Also adding Connor and Timmy, hopefully they can clarify on how we build OpenSSL project. >>>>> Best, >>>>> Niv >>>>> ?On 5/13/21, 4:24 AM, "Richard Levitte" wrote: >>>>> What we expect to do is this at a minimum: >>>>> perl Configure {args...} >>>>> make >>>>> In the form that you filled in, there was the option to specify >>>>> necessary environment variables (which can affect the configuration >>>>> step) and configuration options. I was hoping that would be enough to >>>>> get something going. >>>>> I do not know what you're talking about regarding a .conf file created >>>>> by the Configure step. I understand that you have some sort of super >>>>> project that involves building OpenSSL as a component, though, so I >>>>> can only assume that somewhere in there, it should be possible to find >>>>> how the OpenSSL part is configured, i.e. I assume that there is a run >>>>> of Configure hiding in there somewhere, and that it should be possible >>>>> to see what arguments are used, as well as any relevant environment >>>>> variables. >>>>> Does this answer your question? >>>>> Cheers, >>>>> Richard >>>>> On Fri, 07 May 2021 15:12:11 +0200, >>>>> Nivedita Chevvakula wrote: >>>>> > > We generate a project using cmake that gets built as a dependency of other components in our project. If you are trying to do - build everything using make, which requires a .conf file created with ./Configure step. If so should have one of those somewhere that satisfies what you are looking to produce for iOS, as well as a >>>> different one for Android, please provide that we can put it in place on the build bot and just use that? >>>>> > > Please advise. >>>>> > > Best, >>>>> > Niv >>>>> > > ?On 5/4/21, 2:56 AM, "Richard Levitte" wrote: >>>>> > > Hi, >>>>> > > The worker is connecting fine, so far so good. >>>>> > > However, I realised that there are things missing, where we need >>>>> > information from you! >>>>> > > This worker is meant to build for iOS, is it not? That should require >>>>> > extra OpenSSL configuration options. So let me ask you this, when you >>>>> > usually build OpenSSL for iOS, exactly how do you usually configure >>>>> > OpenSSL? >>>>> > > Cheers, >>>>> > Richard >>>>> > > On Tue, 04 May 2021 03:46:17 +0200, >>>>> > Nivedita Chevvakula wrote: >>>>> > > > > Richard, >>>>> > > > > You can ignore my last mail with error starting buildbot. It is seems to work now after editing >>>>> > > syntax for python2.7. Also we have created user ?buildbot? for this mac as recommended. Please let >>>>> > > me know if we need to pass those credentials or need to setup anything else for the build bot. >>>>> > > > > Best, >>>>> > > > > Niv >>>>> > > > > From: Nivedita Chevvakula >>>>> > > Date: Monday, May 3, 2021 at 6:44 PM >>>>> > > To: Richard Levitte >>>>> > > Subject: Re: [fips-sponsors] Buildbot workers >>>>> > > > > Richard, >>>>> > > > > Buildbot has now installed with linker, make, c compilers. >>>>> > > > > While starting the worker to connect to master after editing tac file as you mentioned getting >>>>> > > syntax error . not able to pin point why. Attaching the error log and the tac file here. Could you >>>>> > > please help. >>>>> > > > > Best, >>>>> > > > > Niv >>>>> > > > > From: Nivedita Chevvakula >>>>> > > Date: Monday, May 3, 2021 at 9:22 AM >>>>> > > To: Richard Levitte >>>>> > > Cc: "levitte at openssl.org" , Tim Champagne , Kevin >>>>> > > Fox >>>>> > > Subject: Re: [fips-sponsors] Buildbot workers >>>>> > > > > Hi Richard, >>>>> > > > > Thank you for sending the worker bot setup requirements, I will go thru and will set up the >>>>> > > workerbot and will install the rest. Do you have any deadline for this setup please share so that >>>>> > > it will help me prioritize. >>>>> > > > > So far these tools are installed over the mac : >>>>> > > > > 1. Android Studio 4.1.3 >>>>> > > 2. Xcode 12.5 >>>>> > > 3. clang version 12.0.5 > > 4. Gcc >>>>> > > 5. Visual Studio Community 2019 for Mac >>>>> > > > > === Visual Studio Community 2019 for Mac === >>>>> > > > > Version 8.9.7 (build 8) >>>>> > > > > Installation UUID: f1ca8dad-7314-419a-8a39-880ba8a71230 >>>>> > > > > GTK+ 2.24.23 (Raleigh theme) >>>>> > > > > Xamarin.Mac 6.18.0.23 (d16-6 / 088c73638) >>>>> > > > > Package version: 612000125 >>>>> > > > > === Mono Framework MDK === >>>>> > > > > Runtime: >>>>> > > > > Mono 6.12.0.125 (2020-02/8c552e98bd6) (64-bit) >>>>> > > > > Package version: 612000125 >>>>> > > > > === Roslyn (Language Service) === >>>>> > > > > 3.9.0-6.21152.10+c10f884b30737542ddd84ca889a4aad9281ce210 >>>>> > > > > === NuGet === >>>>> > > > > Version: 5.8.0.6860 >>>>> > > > > === .NET Core SDK === >>>>> > > > > SDK: /usr/local/share/dotnet/sdk/5.0.202/Sdks >>>>> > > > > SDK Versions: >>>>> > > > > 5.0.202 >>>>> > > > > 3.1.408 >>>>> > > > > 2.1.4 >>>>> > > > > MSBuild SDKs: /Applications/Visual Studio.app/Contents/Resources/lib/monodevelop/bin/MSBuild/ >>>>> > > Current/bin/Sdks >>>>> > > > > === .NET Core Runtime === >>>>> > > > > Runtime: /usr/local/share/dotnet/dotnet >>>>> > > > > Runtime Versions: >>>>> > > > > 5.0.5 >>>>> > > > > 3.1.14 >>>>> > > > > 2.0.5 >>>>> > > > > === .NET Core 3.1 SDK === >>>>> > > > > SDK: 3.1.408 >>>>> > > > > === Xamarin.Profiler === >>>>> > > > > Version: 1.6.15.68 >>>>> > > > > Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler >>>>> > > > > === Updater === >>>>> > > > > Version: 11 >>>>> > > > > === Apple Developer Tools === >>>>> > > > > Xcode 12.5 (18205) >>>>> > > > > Build 12E262 >>>>> > > > > === Xamarin.Mac === >>>>> > > > > Xamarin.Mac not installed. Can't find /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/ >>>>> > > Version. >>>>> > > > > === Xamarin.iOS === >>>>> > > > > Xamarin.iOS not installed. >>>>> > > > > Can't find mtouch or the Version file at /Library/Frameworks/Xamarin.iOS.framework/Versions/ >>>>> > > Current. >>>>> > > > > === Xamarin Designer === >>>>> > > > > Version: 16.9.0.324 >>>>> > > > > Hash: b1e216c75 >>>>> > > > > Branch: remotes/origin/d16-9 >>>>> > > > > Build date: 2021-04-16 00:02:50 UTC >>>>> > > > > === Xamarin.Android === >>>>> > > > > Version: 11.2.2.1 (Visual Studio Community) >>>>> > > > > Commit: xamarin-android/d16-9/877f572 >>>>> > > > > Android SDK: /Users/ec2-user/Library/Developer/Xamarin/android-sdk-macosx >>>>> > > > > Supported Android versions: >>>>> > > > > None installed >>>>> > > > > SDK Tools Version: 26.1.1 >>>>> > > > > SDK Platform Tools Version: 30.0.4 >>>>> > > > > SDK Build Tools Version: 30.0.2 >>>>> > > > > Build Information: >>>>> > > > > Mono: 5e9cb6d >>>>> > > > > Java.Interop: xamarin/java.interop/d16-9 at 54f8c24 >>>>> > > > > ProGuard: Guardsquare/proguard/v7.0.1 at 912d149 >>>>> > > > > SQLite: xamarin/sqlite/3.34.1 at daff8f4 >>>>> > > > > Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-9 at d210f11 >>>>> > > > > === Microsoft OpenJDK for Mobile === >>>>> > > > > Java SDK: /Users/ec2-user/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_1.8.0.25 >>>>> > > > > 1.8.0-25 >>>>> > > > > Android Designer EPL code available here: >>>>> > > > > https://github.com/xamarin/AndroidDesigner.EPL >>>> >>>>> > > > > === Android SDK Manager === >>>>> > > > > Version: 16.9.0.22 >>>>> > > > > Hash: a391de2 >>>>> > > > > Branch: remotes/origin/d16-9~2 >>>>> > > > > Build date: 2021-03-24 08:30:26 UTC >>>>> > > > > === Android Device Manager === >>>>> > > > > Version: 16.9.0.17 >>>>> > > > > Hash: fc2b3db >>>>> > > > > Branch: remotes/origin/dev/jmt/d16-9bump~1 >>>>> > > > > Build date: 2021-03-24 08:30:44 UTC >>>>> > > > > === Build Information === >>>>> > > > > Release ID: 809070008 >>>>> > > > > Git revision: 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>>>> > > > > Build date: 2021-04-16 07:38:03-04 >>>>> > > > > Build branch: release-8.9 >>>>> > > > > Xamarin extensions: 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>>>> > > > > === Operating System === >>>>> > > > > Mac OS X 10.16.0 >>>>> > > > > Darwin 20.3.0 Darwin Kernel Version 20.3.0 >>>>> > > > > Thu Jan 21 00:07:06 PST 2021 >>>>> > > > > root:xnu-7195.81.3~1/RELEASE_X86_64 x86_64 >>>>> > > > > Best, >>>>> > > > > Niv >>>>> > > > > From: Richard Levitte >>>>> > > Date: Monday, May 3, 2021 at 4:54 AM >>>>> > > To: Nivedita Chevvakula >>>>> > > Cc: levitte at openssl.org , Tim Champagne , Kevin Fox >>>>> > > >>>>> > > Subject: Re: [fips-sponsors] Buildbot workers >>>>> > > > > Hi, >>>>> > > > > Thank you for offering workers to us! >>>>> > > > > To be able to set up your worker, you must use version 2.6.0 or >>>>> > > higher. Older version do not support TLS-protected connections. >>>>> > > > > Please see these instructions for installing the buildbot worker >>>>> > > software: >>>>> > > > > http://docs.buildbot.net/latest/manual/installation/worker.html >>>> >>>>> > > > > When buildbot has been installed on the platform where the buildbot >>>>> > > worker is to be run, this is how a worker is created: >>>>> > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ >>>>> > > buildbot.openssl.org:9989 'bluecedar-01' 'Rak;osErfabOn5' >>>>> > > > > where BASEDIR is determined by you. See further down for a few notes >>>>> > > on TLS. >>>>> > > > > To run a buildbot worker, you do this: >>>>> > > > > $ buildbot-worker start BASEDIR >>>>> > > > > Apart from the software needed to run a buildbot worker, and the >>>>> > > utilities that are the normal part of the operating system, you also >>>>> > > need to ensure that the following components are available: >>>>> > > > > - toolchains, i.e. C compiler, linker, make. If you have specified >>>>> > > toolchains in the worker request form, you need to ensure that all >>>>> > > of them are installed. >>>>> > > > > - git >>>>> > > > > Regarding TLS, it may be that the buildbot worker platform doesn't >>>>> > > have the appropriate certification verification roots set up. In that >>>>> > > case, you may need to apply the attached buildbot.tac patch, and store >>>>> > > the attached PEM files in a directory of your choice. Finish up by >>>>> > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with >>>>> > > the path of directory where you stored the PEM files. >>>>> > > > > > -- > Richard Levitte levitte at openssl.org >>>>> > OpenSSL Project http://www.openssl.org/~levitte/ >>>>> -- Richard Levitte levitte at openssl.org >>>>> OpenSSL Project http://www.openssl.org/~levitte/ >>>> -- >>>> Richard Levitte levitte at openssl.org >>>> OpenSSL Project http://www.openssl.org/~levitte/ >>>> _______________________________________________ >>>> buildbot-admin mailing list >>>> buildbot-admin at openssl.org >>>> https://mta.openssl.org/mailman/listinfo/buildbot-admin -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt at openssl.org Thu May 20 18:11:51 2021 From: matt at openssl.org (Matt Caswell) Date: Thu, 20 May 2021 19:11:51 +0100 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <87y2cwmc3h.wl-levitte@openssl.org> <87mttbm1gf.wl-levitte@openssl.org> <87o8dfqbwh.wl-levitte@openssl.org> <87h7iz95a2.wl-levitte@openssl.org> <7CC6990D-7F93-4E61-BE46-116A635AC1FA@bluecedar.com> <2a669cf9-d629-da3c-e386-ac4da9c5677a@openssl.org> Message-ID: Great news! Are you able to run the test suite? Matt On 20/05/2021 17:48, Connor Kelley wrote: > Hi Matt, > After pulling in the fixes for the broken assembly fixes I was able to > successfully build without any of the .conf changes so I was able to > cancel the PR. > Using top of tree I was able to successfully build and arm64 target with > ./Configure ios64-xcrun enable-fips enable-fips-securitychecks > -mios-version-min=11.0 && make > > Thanks, > -Connor >> On May 19, 2021, at 10:59 AM, Matt Caswell > > wrote: >> >> Thanks Connor...lets continue the conversation in the PR itself. >> >> Matt >> >> On 19/05/2021 15:43, Connor Kelley wrote: >>> Hi Matt, >>> I think the PR is trivial based on what you?re talking about but I?ll >>> be happy to fill out one of those forms if you need it. >>> The PR for the changes is here: >>> https://github.com/openssl/openssl/pull/15352 >>> >>> >> > >>> Thanks, >>> -Connor >>>> On May 19, 2021, at 3:57 AM, Matt Caswell >>> >>> >> wrote: >>>> >>>> Hi Connor, >>>> >>>> Please submit them as a pull request on our public github site: >>>> >>>> https://github.com/openssl/openssl/pulls >>>> >>>> >>> > >>>> >>>> If you email the PR number here once created then we will know to >>>> give it the attention it deserves. >>>> >>>> If the changes are anything other than very trivial then we will >>>> also need an ICLA from you individually, as well as a CCLA from Blue >>>> Cedar. See: >>>> >>>> https://www.openssl.org/policies/cla.html >>>> >>>> >>>> Matt >>>> >>>> >>>> On 19/05/2021 01:54, Connor Kelley wrote: >>>>> Hi Richard, >>>>> I?ve got a working build that required a couple of updates to the >>>>> 15-iOS.conf file to get it current. With those changes plus the >>>>> configure invocation the build seemingly completes successfully. >>>>> What is the process for submitting a PR to get those changes in and >>>>> usable? >>>>> Thanks, >>>>> -Connor >>>>> Get Outlook for iOS >>>>> ------------------------------------------------------------------------ >>>>> *From:* Richard Levitte >>>>> *Sent:* Tuesday, May 18, 2021 4:05:25 PM >>>>> *To:* Nivedita Chevvakula >>>>> *Cc:* Richard Levitte ; Tim Champagne >>>>> ; Connor Kelley >>>>> ; buildbot-admin at openssl.org >>>>> >>>>> *Subject:* Re: [fips-sponsors] Buildbot workers >>>>> [ Also adding buildbot-admin at openssl.org (I should have done that >>>>> long ago) ] >>>>> Yes, some technical details is what I'm trying to get. >>>>> Right now, that worker is building, sure, but that's a MacOS build, >>>>> which wasn't what you wanted. >>>>> So Tim, Connor, if you have something to share, I can hopefully do >>>>> better progress on our end. >>>>> Cheers, >>>>> Richard >>>>> On Mon, 17 May 2021 15:28:50 +0200, >>>>> Nivedita Chevvakula wrote: >>>>>> On this buildbot slave we don't run any our projects, we have set >>>>>> this slave only for buildbot worker. Please let me know if I give >>>>>> ssh creds it will expedite the process. >>>>>> Also adding Connor and Timmy, hopefully they can clarify on how we >>>>>> build OpenSSL project. >>>>>> Best, >>>>>> Niv >>>>>> ?On 5/13/21, 4:24 AM, "Richard Levitte" wrote: >>>>>> ???? What we expect to do is this at a minimum: >>>>>> ???????? perl Configure {args...} >>>>>> ???????? make >>>>>> ???? In the form that you filled in, there was the option to specify >>>>>> ???? necessary environment variables (which can affect the >>>>>> configuration >>>>>> ???? step) and configuration options.? I was hoping that would be >>>>>> enough to >>>>>> ???? get something going. >>>>>> ???? I do not know what you're talking about regarding a .conf >>>>>> file created >>>>>> ???? by the Configure step.? I understand that you have some sort >>>>>> of super >>>>>> ???? project that involves building OpenSSL as a component, >>>>>> though, so I >>>>>> ???? can only assume that somewhere in there, it should be >>>>>> possible to find >>>>>> ???? how the OpenSSL part is configured, i.e. I assume that there >>>>>> is a run >>>>>> ???? of Configure hiding in there somewhere, and that it should be >>>>>> possible >>>>>> ???? to see what arguments are used, as well as any relevant >>>>>> environment >>>>>> ???? variables. >>>>>> ???? Does this answer your question? >>>>>> ???? Cheers, >>>>>> ???? Richard >>>>>> ???? On Fri, 07 May 2021 15:12:11 +0200, >>>>>> ???? Nivedita Chevvakula wrote: >>>>>> ???? > ???? > We generate a project using cmake that gets built as >>>>>> a dependency of other components in our project. If you are trying >>>>>> to do - build everything using make, which requires a .conf file >>>>>> created with ./Configure step. If so should have one of those >>>>>> somewhere ?that satisfies what you are looking to produce for iOS, >>>>>> as well as a >>>>> different one for Android, please provide that we can put it in >>>>> place on the build bot and just use that? >>>>>> ???? > ???? > Please advise. >>>>>> ???? > ???? > Best, >>>>>> ???? > Niv >>>>>> ???? > ???? > ?On 5/4/21, 2:56 AM, "Richard Levitte" >>>>>> wrote: >>>>>> ???? > ???? >???? Hi, >>>>>> ???? > ???? >???? The worker is connecting fine, so far so good. >>>>>> ???? > ???? >???? However, I realised that there are things >>>>>> missing, where we need >>>>>> ???? >???? information from you! >>>>>> ???? > ???? >???? This worker is meant to build for iOS, is it >>>>>> not? ?That should require >>>>>> ???? >???? extra OpenSSL configuration options.? So let me ask you >>>>>> this, when you >>>>>> ???? >???? usually build OpenSSL for iOS, exactly how do you >>>>>> usually configure >>>>>> ???? >???? OpenSSL? >>>>>> ???? > ???? >???? Cheers, >>>>>> ???? >???? Richard >>>>>> ???? > ???? >???? On Tue, 04 May 2021 03:46:17 +0200, >>>>>> ???? >???? Nivedita Chevvakula wrote: >>>>>> ???? >???? > ???? >???? > Richard, >>>>>> ???? >???? > ???? >???? > You can ignore my last mail with error >>>>>> starting buildbot. It is seems to work now after editing >>>>>> ???? >???? > syntax for python2.7. Also we have created user >>>>>> ?buildbot? for this mac as recommended. Please let >>>>>> ???? >???? > me know if we need to pass those credentials or need >>>>>> to setup anything else for the build bot. >>>>>> ???? >???? > ???? >???? > Best, >>>>>> ???? >???? > ???? >???? > Niv >>>>>> ???? >???? > ???? >???? > From: Nivedita Chevvakula >>>>>> >>>>>> ???? >???? > Date: Monday, May 3, 2021 at 6:44 PM >>>>>> ???? >???? > To: Richard Levitte >>>>>> ???? >???? > Subject: Re: [fips-sponsors] Buildbot workers >>>>>> ???? >???? > ???? >???? > Richard, >>>>>> ???? >???? > ???? >???? > Buildbot has now installed with linker, >>>>>> make, c compilers. >>>>>> ???? >???? > ???? >???? > While starting the worker to connect to >>>>>> master after editing tac file as you mentioned getting >>>>>> ???? >???? > syntax error . not able to pin point why. Attaching >>>>>> the error log and the tac file here. Could you >>>>>> ???? >???? > please help. >>>>>> ???? >???? > ???? >???? > Best, >>>>>> ???? >???? > ???? >???? > Niv >>>>>> ???? >???? > ???? >???? > From: Nivedita Chevvakula >>>>>> >>>>>> ???? >???? > Date: Monday, May 3, 2021 at 9:22 AM >>>>>> ???? >???? > To: Richard Levitte >>>>>> ???? >???? > Cc: "levitte at openssl.org" , Tim >>>>>> Champagne , Kevin >>>>>> ???? >???? > Fox >>>>>> ???? >???? > Subject: Re: [fips-sponsors] Buildbot workers >>>>>> ???? >???? > ???? >???? > Hi Richard, >>>>>> ???? >???? > ???? >???? > Thank you for sending the worker bot >>>>>> setup requirements, I will go thru and will set up the >>>>>> ???? >???? > workerbot and will install the rest. Do you have any >>>>>> deadline for this setup please share so that >>>>>> ???? >???? > it will help me prioritize. >>>>>> ???? >???? > ???? >???? > So far these tools are installed over >>>>>> the mac : >>>>>> ???? >???? > ???? >???? >? 1. Android Studio 4.1.3 >>>>>> ???? >???? >? 2. Xcode 12.5 >>>>>> ???? >???? >? 3. clang version 12.0.5 ???? >???? >? 4. Gcc >>>>>> ???? >???? >? 5. Visual Studio Community 2019 for Mac >>>>>> ???? >???? > ???? >???? > === Visual Studio Community 2019 for Mac === >>>>>> ???? >???? > ???? >???? > Version 8.9.7 (build 8) >>>>>> ???? >???? > ???? >???? > Installation UUID: >>>>>> f1ca8dad-7314-419a-8a39-880ba8a71230 >>>>>> ???? >???? > ???? >???? > GTK+ 2.24.23 (Raleigh theme) >>>>>> ???? >???? > ???? >???? > Xamarin.Mac 6.18.0.23 (d16-6 / 088c73638) >>>>>> ???? >???? > ???? >???? > Package version: 612000125 >>>>>> ???? >???? > ???? >???? > === Mono Framework MDK === >>>>>> ???? >???? > ???? >???? > Runtime: >>>>>> ???? >???? > ???? >???? > Mono 6.12.0.125 (2020-02/8c552e98bd6) >>>>>> (64-bit) >>>>>> ???? >???? > ???? >???? > Package version: 612000125 >>>>>> ???? >???? > ???? >???? > === Roslyn (Language Service) === >>>>>> ???? >???? > ???? >???? > >>>>>> 3.9.0-6.21152.10+c10f884b30737542ddd84ca889a4aad9281ce210 >>>>>> ???? >???? > ???? >???? > === NuGet === >>>>>> ???? >???? > ???? >???? > Version: 5.8.0.6860 >>>>>> ???? >???? > ???? >???? > === .NET Core SDK === >>>>>> ???? >???? > ???? >???? > SDK: >>>>>> /usr/local/share/dotnet/sdk/5.0.202/Sdks >>>>>> ???? >???? > ???? >???? > SDK Versions: >>>>>> ???? >???? > ???? >???? > 5.0.202 >>>>>> ???? >???? > ???? >???? > 3.1.408 >>>>>> ???? >???? > ???? >???? > 2.1.4 >>>>>> ???? >???? > ???? >???? > MSBuild SDKs: /Applications/Visual >>>>>> Studio.app/Contents/Resources/lib/monodevelop/bin/MSBuild/ >>>>>> ???? >???? > Current/bin/Sdks >>>>>> ???? >???? > ???? >???? > === .NET Core Runtime === >>>>>> ???? >???? > ???? >???? > Runtime: /usr/local/share/dotnet/dotnet >>>>>> ???? >???? > ???? >???? > Runtime Versions: >>>>>> ???? >???? > ???? >???? > 5.0.5 >>>>>> ???? >???? > ???? >???? > 3.1.14 >>>>>> ???? >???? > ???? >???? > 2.0.5 >>>>>> ???? >???? > ???? >???? > === .NET Core 3.1 SDK === >>>>>> ???? >???? > ???? >???? > SDK: 3.1.408 >>>>>> ???? >???? > ???? >???? > === Xamarin.Profiler === >>>>>> ???? >???? > ???? >???? > Version: 1.6.15.68 >>>>>> ???? >???? > ???? >???? > Location: /Applications/Xamarin >>>>>> Profiler.app/Contents/MacOS/Xamarin Profiler >>>>>> ???? >???? > ???? >???? > === Updater === >>>>>> ???? >???? > ???? >???? > Version: 11 >>>>>> ???? >???? > ???? >???? > === Apple Developer Tools === >>>>>> ???? >???? > ???? >???? > Xcode 12.5 (18205) >>>>>> ???? >???? > ???? >???? > Build 12E262 >>>>>> ???? >???? > ???? >???? > === Xamarin.Mac === >>>>>> ???? >???? > ???? >???? > Xamarin.Mac not installed. Can't find >>>>>> /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/ >>>>>> ???? >???? > Version. >>>>>> ???? >???? > ???? >???? > === Xamarin.iOS === >>>>>> ???? >???? > ???? >???? > Xamarin.iOS not installed. >>>>>> ???? >???? > ???? >???? > Can't find mtouch or the Version file at >>>>>> /Library/Frameworks/Xamarin.iOS.framework/Versions/ >>>>>> ???? >???? > Current. >>>>>> ???? >???? > ???? >???? > === Xamarin Designer === >>>>>> ???? >???? > ???? >???? > Version: 16.9.0.324 >>>>>> ???? >???? > ???? >???? > Hash: b1e216c75 >>>>>> ???? >???? > ???? >???? > Branch: remotes/origin/d16-9 >>>>>> ???? >???? > ???? >???? > Build date: 2021-04-16 00:02:50 UTC >>>>>> ???? >???? > ???? >???? > === Xamarin.Android === >>>>>> ???? >???? > ???? >???? > Version: 11.2.2.1 (Visual Studio Community) >>>>>> ???? >???? > ???? >???? > Commit: xamarin-android/d16-9/877f572 >>>>>> ???? >???? > ???? >???? > Android SDK: >>>>>> /Users/ec2-user/Library/Developer/Xamarin/android-sdk-macosx >>>>>> ???? >???? > ???? >???? > Supported Android versions: >>>>>> ???? >???? > ???? >???? > None installed >>>>>> ???? >???? > ???? >???? > SDK Tools Version: 26.1.1 >>>>>> ???? >???? > ???? >???? > SDK Platform Tools Version: 30.0.4 >>>>>> ???? >???? > ???? >???? > SDK Build Tools Version: 30.0.2 >>>>>> ???? >???? > ???? >???? > Build Information: >>>>>> ???? >???? > ???? >???? > Mono: 5e9cb6d >>>>>> ???? >???? > ???? >???? > Java.Interop: >>>>>> xamarin/java.interop/d16-9 at 54f8c24 >>>>>> ???? >???? > ???? >???? > ProGuard: >>>>>> Guardsquare/proguard/v7.0.1 at 912d149 >>>>>> ???? >???? > ???? >???? > SQLite: xamarin/sqlite/3.34.1 at daff8f4 >>>>>> ???? >???? > ???? >???? > Xamarin.Android Tools: >>>>>> xamarin/xamarin-android-tools/d16-9 at d210f11 >>>>>> ???? >???? > ???? >???? > === Microsoft OpenJDK for Mobile === >>>>>> ???? >???? > ???? >???? > Java SDK: >>>>>> /Users/ec2-user/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_1.8.0.25 >>>>>> ???? >???? > ???? >???? > 1.8.0-25 >>>>>> ???? >???? > ???? >???? > Android Designer EPL code available here: >>>>>> ???? >???? > ???? >???? > >>>>>> https://github.com/xamarin/AndroidDesigner.EPL >>>>> >>>>>> ???? >???? > ???? >???? > === Android SDK Manager === >>>>>> ???? >???? > ???? >???? > Version: 16.9.0.22 >>>>>> ???? >???? > ???? >???? > Hash: a391de2 >>>>>> ???? >???? > ???? >???? > Branch: remotes/origin/d16-9~2 >>>>>> ???? >???? > ???? >???? > Build date: 2021-03-24 08:30:26 UTC >>>>>> ???? >???? > ???? >???? > === Android Device Manager === >>>>>> ???? >???? > ???? >???? > Version: 16.9.0.17 >>>>>> ???? >???? > ???? >???? > Hash: fc2b3db >>>>>> ???? >???? > ???? >???? > Branch: remotes/origin/dev/jmt/d16-9bump~1 >>>>>> ???? >???? > ???? >???? > Build date: 2021-03-24 08:30:44 UTC >>>>>> ???? >???? > ???? >???? > === Build Information === >>>>>> ???? >???? > ???? >???? > Release ID: 809070008 >>>>>> ???? >???? > ???? >???? > Git revision: >>>>>> 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>>>>> ???? >???? > ???? >???? > Build date: 2021-04-16 07:38:03-04 >>>>>> ???? >???? > ???? >???? > Build branch: release-8.9 >>>>>> ???? >???? > ???? >???? > Xamarin extensions: >>>>>> 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>>>>> ???? >???? > ???? >???? > === Operating System === >>>>>> ???? >???? > ???? >???? > Mac OS X 10.16.0 >>>>>> ???? >???? > ???? >???? > Darwin 20.3.0 Darwin Kernel Version 20.3.0 >>>>>> ???? >???? > ???? >???? > Thu Jan 21 00:07:06 PST 2021 >>>>>> ???? >???? > ???? >???? > root:xnu-7195.81.3~1/RELEASE_X86_64 x86_64 >>>>>> ???? >???? > ???? >???? > Best, >>>>>> ???? >???? > ???? >???? > Niv >>>>>> ???? >???? > ???? >???? > From: Richard Levitte >>>>>> ???? >???? > Date: Monday, May 3, 2021 at 4:54 AM >>>>>> ???? >???? > To: Nivedita Chevvakula >>>>>> ???? >???? > Cc: levitte at openssl.org , Tim >>>>>> Champagne , Kevin Fox >>>>>> ???? >???? > >>>>>> ???? >???? > Subject: Re: [fips-sponsors] Buildbot workers >>>>>> ???? >???? > ???? >???? > Hi, >>>>>> ???? >???? > ???? >???? > Thank you for offering workers to us! >>>>>> ???? >???? > ???? >???? > To be able to set up your worker, you >>>>>> must use version 2.6.0 or >>>>>> ???? >???? > higher.? Older version do not support TLS-protected >>>>>> connections. >>>>>> ???? >???? > ???? >???? > Please see these instructions for >>>>>> installing the buildbot worker >>>>>> ???? >???? > software: >>>>>> ???? >???? > ???? >???? > >>>>>> ????http://docs.buildbot.net/latest/manual/installation/worker.html >>>>> >>>>>> ???? >???? > ???? >???? > When buildbot has been installed on the >>>>>> platform where the buildbot >>>>>> ???? >???? > worker is to be run, this is how a worker is created: >>>>>> ???? >???? > ???? >???? >???? $ buildbot-worker create-worker >>>>>> --use-tls BASEDIR \ >>>>>> ???? >???? >???????? buildbot.openssl.org:9989 'bluecedar-01' >>>>>> 'Rak;osErfabOn5' >>>>>> ???? >???? > ???? >???? > where BASEDIR is determined by you.? See >>>>>> further down for a few notes >>>>>> ???? >???? > on TLS. >>>>>> ???? >???? > ???? >???? > To run a buildbot worker, you do this: >>>>>> ???? >???? > ???? >???? >???? $ buildbot-worker start BASEDIR >>>>>> ???? >???? > ???? >???? > Apart from the software needed to run a >>>>>> buildbot worker, and the >>>>>> ???? >???? > utilities that are the normal part of the operating >>>>>> system, you also >>>>>> ???? >???? > need to ensure that the following components are >>>>>> available: >>>>>> ???? >???? > ???? >???? > -?? toolchains, i.e. C compiler, linker, >>>>>> make.? If you have specified >>>>>> ???? >???? >???? toolchains in the worker request form, you need >>>>>> to ensure that all >>>>>> ???? >???? >???? of them are installed. >>>>>> ???? >???? > ???? >???? > -?? git >>>>>> ???? >???? > ???? >???? > Regarding TLS, it may be that the >>>>>> buildbot worker platform doesn't >>>>>> ???? >???? > have the appropriate certification verification roots >>>>>> set up.? In that >>>>>> ???? >???? > case, you may need to apply the attached buildbot.tac >>>>>> patch, and store >>>>>> ???? >???? > the attached PEM files in a directory of your choice. >>>>>> ?Finish up by >>>>>> ???? >???? > find the string '/PATH/TO/ssl-roots-dir' and replace >>>>>> its contents with >>>>>> ???? >???? > the path of directory where you stored the PEM files. >>>>>> ???? >???? > ???? >???? > ???? >???? -- ???? >???? Richard >>>>>> Levitte???????? levitte at openssl.org >>>>>> ???? >???? OpenSSL Project >>>>>> ????????http://www.openssl.org/~levitte/ >>>>>> >>>>>> ???? -- ???? Richard Levitte???????? levitte at openssl.org >>>>>> ???? OpenSSL Project ????????http://www.openssl.org/~levitte/ >>>>>> >>>>> -- >>>>> Richard Levitte???????? levitte at openssl.org >>>>> OpenSSL Project http://www.openssl.org/~levitte/ >>>>> >>>>> _______________________________________________ >>>>> buildbot-admin mailing list >>>>> buildbot-admin at openssl.org >>>>> https://mta.openssl.org/mailman/listinfo/buildbot-admin > From ckelley at bluecedar.com Thu May 20 18:15:30 2021 From: ckelley at bluecedar.com (Connor Kelley) Date: Thu, 20 May 2021 14:15:30 -0400 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <87y2cwmc3h.wl-levitte@openssl.org> <87mttbm1gf.wl-levitte@openssl.org> <87o8dfqbwh.wl-levitte@openssl.org> <87h7iz95a2.wl-levitte@openssl.org> <7CC6990D-7F93-4E61-BE46-116A635AC1FA@bluecedar.com> <2a669cf9-d629-da3c-e386-ac4da9c5677a@openssl.org> Message-ID: <84BD88CC-9ACB-4C86-AA77-762DC8F996F7@bluecedar.com> Hi Matt, I did not see any suite to run for arm64, and got the following error: MacBook-Pro:openssl ckelley$ make test make depend && make _tests make[1]: Entering directory '/Users/ckelley/openssl' make[1]: Leaving directory '/Users/ckelley/openssl' make[1]: Entering directory '/Users/ckelley/openssl' perl ./util/wrap.pl apps/openssl fipsinstall -module providers/fips.dylib -provider_name fips -mac_name HMAC -section_name fips_sect > providers/fipsmodule.cnf util/../util/shlib_wrap.sh: line 113: /Users/ckelley/openssl/apps/openssl: Bad CPU type in executable util/../util/shlib_wrap.sh: line 113: /Users/ckelley/openssl/apps/openssl: Undefined error: 0 Are there arm64 tests that can be run for a cross-compiled target like we are attempting to build? I did not see anything specific or applicable, but will be happy to run whatever if something exists. Outside of that I was considering swapping out the existing FIPS library that we have and see what happens, but that version is much older, so it might not be immediately applicable. Thanks, -Connor > On May 20, 2021, at 2:11 PM, Matt Caswell wrote: > > Great news! Are you able to run the test suite? > > Matt > > On 20/05/2021 17:48, Connor Kelley wrote: >> Hi Matt, >> After pulling in the fixes for the broken assembly fixes I was able to successfully build without any of the .conf changes so I was able to cancel the PR. >> Using top of tree I was able to successfully build and arm64 target with ./Configure ios64-xcrun enable-fips enable-fips-securitychecks -mios-version-min=11.0 && make >> Thanks, >> -Connor >>> On May 19, 2021, at 10:59 AM, Matt Caswell > wrote: >>> >>> Thanks Connor...lets continue the conversation in the PR itself. >>> >>> Matt >>> >>> On 19/05/2021 15:43, Connor Kelley wrote: >>>> Hi Matt, >>>> I think the PR is trivial based on what you?re talking about but I?ll be happy to fill out one of those forms if you need it. >>>> The PR for the changes is here: https://github.com/openssl/openssl/pull/15352 > >>>> Thanks, >>>> -Connor >>>>> On May 19, 2021, at 3:57 AM, Matt Caswell >> wrote: >>>>> >>>>> Hi Connor, >>>>> >>>>> Please submit them as a pull request on our public github site: >>>>> >>>>> https://github.com/openssl/openssl/pulls > >>>>> >>>>> If you email the PR number here once created then we will know to give it the attention it deserves. >>>>> >>>>> If the changes are anything other than very trivial then we will also need an ICLA from you individually, as well as a CCLA from Blue Cedar. See: >>>>> >>>>> https://www.openssl.org/policies/cla.html >>>>> >>>>> Matt >>>>> >>>>> >>>>> On 19/05/2021 01:54, Connor Kelley wrote: >>>>>> Hi Richard, >>>>>> I?ve got a working build that required a couple of updates to the 15-iOS.conf file to get it current. With those changes plus the configure invocation the build seemingly completes successfully. What is the process for submitting a PR to get those changes in and usable? >>>>>> Thanks, >>>>>> -Connor >>>>>> Get Outlook for iOS >>>>>> ------------------------------------------------------------------------ >>>>>> *From:* Richard Levitte >>>>>> *Sent:* Tuesday, May 18, 2021 4:05:25 PM >>>>>> *To:* Nivedita Chevvakula >>>>>> *Cc:* Richard Levitte ; Tim Champagne ; Connor Kelley ; buildbot-admin at openssl.org >>>>>> *Subject:* Re: [fips-sponsors] Buildbot workers >>>>>> [ Also adding buildbot-admin at openssl.org (I should have done that long ago) ] >>>>>> Yes, some technical details is what I'm trying to get. >>>>>> Right now, that worker is building, sure, but that's a MacOS build, >>>>>> which wasn't what you wanted. >>>>>> So Tim, Connor, if you have something to share, I can hopefully do >>>>>> better progress on our end. >>>>>> Cheers, >>>>>> Richard >>>>>> On Mon, 17 May 2021 15:28:50 +0200, >>>>>> Nivedita Chevvakula wrote: >>>>>>> On this buildbot slave we don't run any our projects, we have set this slave only for buildbot worker. Please let me know if I give ssh creds it will expedite the process. >>>>>>> Also adding Connor and Timmy, hopefully they can clarify on how we build OpenSSL project. >>>>>>> Best, >>>>>>> Niv >>>>>>> ?On 5/13/21, 4:24 AM, "Richard Levitte" wrote: >>>>>>> What we expect to do is this at a minimum: >>>>>>> perl Configure {args...} >>>>>>> make >>>>>>> In the form that you filled in, there was the option to specify >>>>>>> necessary environment variables (which can affect the configuration >>>>>>> step) and configuration options. I was hoping that would be enough to >>>>>>> get something going. >>>>>>> I do not know what you're talking about regarding a .conf file created >>>>>>> by the Configure step. I understand that you have some sort of super >>>>>>> project that involves building OpenSSL as a component, though, so I >>>>>>> can only assume that somewhere in there, it should be possible to find >>>>>>> how the OpenSSL part is configured, i.e. I assume that there is a run >>>>>>> of Configure hiding in there somewhere, and that it should be possible >>>>>>> to see what arguments are used, as well as any relevant environment >>>>>>> variables. >>>>>>> Does this answer your question? >>>>>>> Cheers, >>>>>>> Richard >>>>>>> On Fri, 07 May 2021 15:12:11 +0200, >>>>>>> Nivedita Chevvakula wrote: >>>>>>> > > We generate a project using cmake that gets built as a dependency of other components in our project. If you are trying to do - build everything using make, which requires a .conf file created with ./Configure step. If so should have one of those somewhere that satisfies what you are looking to produce for iOS, as well as a >>>>>> different one for Android, please provide that we can put it in place on the build bot and just use that? >>>>>>> > > Please advise. >>>>>>> > > Best, >>>>>>> > Niv >>>>>>> > > ?On 5/4/21, 2:56 AM, "Richard Levitte" wrote: >>>>>>> > > Hi, >>>>>>> > > The worker is connecting fine, so far so good. >>>>>>> > > However, I realised that there are things missing, where we need >>>>>>> > information from you! >>>>>>> > > This worker is meant to build for iOS, is it not? That should require >>>>>>> > extra OpenSSL configuration options. So let me ask you this, when you >>>>>>> > usually build OpenSSL for iOS, exactly how do you usually configure >>>>>>> > OpenSSL? >>>>>>> > > Cheers, >>>>>>> > Richard >>>>>>> > > On Tue, 04 May 2021 03:46:17 +0200, >>>>>>> > Nivedita Chevvakula wrote: >>>>>>> > > > > Richard, >>>>>>> > > > > You can ignore my last mail with error starting buildbot. It is seems to work now after editing >>>>>>> > > syntax for python2.7. Also we have created user ?buildbot? for this mac as recommended. Please let >>>>>>> > > me know if we need to pass those credentials or need to setup anything else for the build bot. >>>>>>> > > > > Best, >>>>>>> > > > > Niv >>>>>>> > > > > From: Nivedita Chevvakula >>>>>>> > > Date: Monday, May 3, 2021 at 6:44 PM >>>>>>> > > To: Richard Levitte >>>>>>> > > Subject: Re: [fips-sponsors] Buildbot workers >>>>>>> > > > > Richard, >>>>>>> > > > > Buildbot has now installed with linker, make, c compilers. >>>>>>> > > > > While starting the worker to connect to master after editing tac file as you mentioned getting >>>>>>> > > syntax error . not able to pin point why. Attaching the error log and the tac file here. Could you >>>>>>> > > please help. >>>>>>> > > > > Best, >>>>>>> > > > > Niv >>>>>>> > > > > From: Nivedita Chevvakula >>>>>>> > > Date: Monday, May 3, 2021 at 9:22 AM >>>>>>> > > To: Richard Levitte >>>>>>> > > Cc: "levitte at openssl.org" , Tim Champagne , Kevin >>>>>>> > > Fox >>>>>>> > > Subject: Re: [fips-sponsors] Buildbot workers >>>>>>> > > > > Hi Richard, >>>>>>> > > > > Thank you for sending the worker bot setup requirements, I will go thru and will set up the >>>>>>> > > workerbot and will install the rest. Do you have any deadline for this setup please share so that >>>>>>> > > it will help me prioritize. >>>>>>> > > > > So far these tools are installed over the mac : >>>>>>> > > > > 1. Android Studio 4.1.3 >>>>>>> > > 2. Xcode 12.5 >>>>>>> > > 3. clang version 12.0.5 > > 4. Gcc >>>>>>> > > 5. Visual Studio Community 2019 for Mac >>>>>>> > > > > === Visual Studio Community 2019 for Mac === >>>>>>> > > > > Version 8.9.7 (build 8) >>>>>>> > > > > Installation UUID: f1ca8dad-7314-419a-8a39-880ba8a71230 >>>>>>> > > > > GTK+ 2.24.23 (Raleigh theme) >>>>>>> > > > > Xamarin.Mac 6.18.0.23 (d16-6 / 088c73638) >>>>>>> > > > > Package version: 612000125 >>>>>>> > > > > === Mono Framework MDK === >>>>>>> > > > > Runtime: >>>>>>> > > > > Mono 6.12.0.125 (2020-02/8c552e98bd6) (64-bit) >>>>>>> > > > > Package version: 612000125 >>>>>>> > > > > === Roslyn (Language Service) === >>>>>>> > > > > 3.9.0-6.21152.10+c10f884b30737542ddd84ca889a4aad9281ce210 >>>>>>> > > > > === NuGet === >>>>>>> > > > > Version: 5.8.0.6860 >>>>>>> > > > > === .NET Core SDK === >>>>>>> > > > > SDK: /usr/local/share/dotnet/sdk/5.0.202/Sdks >>>>>>> > > > > SDK Versions: >>>>>>> > > > > 5.0.202 >>>>>>> > > > > 3.1.408 >>>>>>> > > > > 2.1.4 >>>>>>> > > > > MSBuild SDKs: /Applications/Visual Studio.app/Contents/Resources/lib/monodevelop/bin/MSBuild/ >>>>>>> > > Current/bin/Sdks >>>>>>> > > > > === .NET Core Runtime === >>>>>>> > > > > Runtime: /usr/local/share/dotnet/dotnet >>>>>>> > > > > Runtime Versions: >>>>>>> > > > > 5.0.5 >>>>>>> > > > > 3.1.14 >>>>>>> > > > > 2.0.5 >>>>>>> > > > > === .NET Core 3.1 SDK === >>>>>>> > > > > SDK: 3.1.408 >>>>>>> > > > > === Xamarin.Profiler === >>>>>>> > > > > Version: 1.6.15.68 >>>>>>> > > > > Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler >>>>>>> > > > > === Updater === >>>>>>> > > > > Version: 11 >>>>>>> > > > > === Apple Developer Tools === >>>>>>> > > > > Xcode 12.5 (18205) >>>>>>> > > > > Build 12E262 >>>>>>> > > > > === Xamarin.Mac === >>>>>>> > > > > Xamarin.Mac not installed. Can't find /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/ >>>>>>> > > Version. >>>>>>> > > > > === Xamarin.iOS === >>>>>>> > > > > Xamarin.iOS not installed. >>>>>>> > > > > Can't find mtouch or the Version file at /Library/Frameworks/Xamarin.iOS.framework/Versions/ >>>>>>> > > Current. >>>>>>> > > > > === Xamarin Designer === >>>>>>> > > > > Version: 16.9.0.324 >>>>>>> > > > > Hash: b1e216c75 >>>>>>> > > > > Branch: remotes/origin/d16-9 >>>>>>> > > > > Build date: 2021-04-16 00:02:50 UTC >>>>>>> > > > > === Xamarin.Android === >>>>>>> > > > > Version: 11.2.2.1 (Visual Studio Community) >>>>>>> > > > > Commit: xamarin-android/d16-9/877f572 >>>>>>> > > > > Android SDK: /Users/ec2-user/Library/Developer/Xamarin/android-sdk-macosx >>>>>>> > > > > Supported Android versions: >>>>>>> > > > > None installed >>>>>>> > > > > SDK Tools Version: 26.1.1 >>>>>>> > > > > SDK Platform Tools Version: 30.0.4 >>>>>>> > > > > SDK Build Tools Version: 30.0.2 >>>>>>> > > > > Build Information: >>>>>>> > > > > Mono: 5e9cb6d >>>>>>> > > > > Java.Interop: xamarin/java.interop/d16-9 at 54f8c24 >>>>>>> > > > > ProGuard: Guardsquare/proguard/v7.0.1 at 912d149 >>>>>>> > > > > SQLite: xamarin/sqlite/3.34.1 at daff8f4 >>>>>>> > > > > Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-9 at d210f11 >>>>>>> > > > > === Microsoft OpenJDK for Mobile === >>>>>>> > > > > Java SDK: /Users/ec2-user/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_1.8.0.25 >>>>>>> > > > > 1.8.0-25 >>>>>>> > > > > Android Designer EPL code available here: >>>>>>> > > > > https://github.com/xamarin/AndroidDesigner.EPL >>>>>> >>>>>>> > > > > === Android SDK Manager === >>>>>>> > > > > Version: 16.9.0.22 >>>>>>> > > > > Hash: a391de2 >>>>>>> > > > > Branch: remotes/origin/d16-9~2 >>>>>>> > > > > Build date: 2021-03-24 08:30:26 UTC >>>>>>> > > > > === Android Device Manager === >>>>>>> > > > > Version: 16.9.0.17 >>>>>>> > > > > Hash: fc2b3db >>>>>>> > > > > Branch: remotes/origin/dev/jmt/d16-9bump~1 >>>>>>> > > > > Build date: 2021-03-24 08:30:44 UTC >>>>>>> > > > > === Build Information === >>>>>>> > > > > Release ID: 809070008 >>>>>>> > > > > Git revision: 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>>>>>> > > > > Build date: 2021-04-16 07:38:03-04 >>>>>>> > > > > Build branch: release-8.9 >>>>>>> > > > > Xamarin extensions: 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>>>>>> > > > > === Operating System === >>>>>>> > > > > Mac OS X 10.16.0 >>>>>>> > > > > Darwin 20.3.0 Darwin Kernel Version 20.3.0 >>>>>>> > > > > Thu Jan 21 00:07:06 PST 2021 >>>>>>> > > > > root:xnu-7195.81.3~1/RELEASE_X86_64 x86_64 >>>>>>> > > > > Best, >>>>>>> > > > > Niv >>>>>>> > > > > From: Richard Levitte >>>>>>> > > Date: Monday, May 3, 2021 at 4:54 AM >>>>>>> > > To: Nivedita Chevvakula >>>>>>> > > Cc: levitte at openssl.org , Tim Champagne , Kevin Fox >>>>>>> > > >>>>>>> > > Subject: Re: [fips-sponsors] Buildbot workers >>>>>>> > > > > Hi, >>>>>>> > > > > Thank you for offering workers to us! >>>>>>> > > > > To be able to set up your worker, you must use version 2.6.0 or >>>>>>> > > higher. Older version do not support TLS-protected connections. >>>>>>> > > > > Please see these instructions for installing the buildbot worker >>>>>>> > > software: >>>>>>> > > > > http://docs.buildbot.net/latest/manual/installation/worker.html >>>>>> >>>>>>> > > > > When buildbot has been installed on the platform where the buildbot >>>>>>> > > worker is to be run, this is how a worker is created: >>>>>>> > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ >>>>>>> > > buildbot.openssl.org:9989 'bluecedar-01' 'Rak;osErfabOn5' >>>>>>> > > > > where BASEDIR is determined by you. See further down for a few notes >>>>>>> > > on TLS. >>>>>>> > > > > To run a buildbot worker, you do this: >>>>>>> > > > > $ buildbot-worker start BASEDIR >>>>>>> > > > > Apart from the software needed to run a buildbot worker, and the >>>>>>> > > utilities that are the normal part of the operating system, you also >>>>>>> > > need to ensure that the following components are available: >>>>>>> > > > > - toolchains, i.e. C compiler, linker, make. If you have specified >>>>>>> > > toolchains in the worker request form, you need to ensure that all >>>>>>> > > of them are installed. >>>>>>> > > > > - git >>>>>>> > > > > Regarding TLS, it may be that the buildbot worker platform doesn't >>>>>>> > > have the appropriate certification verification roots set up. In that >>>>>>> > > case, you may need to apply the attached buildbot.tac patch, and store >>>>>>> > > the attached PEM files in a directory of your choice. Finish up by >>>>>>> > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with >>>>>>> > > the path of directory where you stored the PEM files. >>>>>>> > > > > > -- > Richard Levitte levitte at openssl.org >>>>>>> > OpenSSL Project http://www.openssl.org/~levitte/ >>>>>>> -- Richard Levitte levitte at openssl.org >>>>>>> OpenSSL Project http://www.openssl.org/~levitte/ >>>>>> -- >>>>>> Richard Levitte levitte at openssl.org >>>>>> OpenSSL Project http://www.openssl.org/~levitte/ >>>>>> _______________________________________________ >>>>>> buildbot-admin mailing list >>>>>> buildbot-admin at openssl.org >>>>>> https://mta.openssl.org/mailman/listinfo/buildbot-admin -------------- next part -------------- An HTML attachment was scrubbed... URL: From matt at openssl.org Fri May 21 07:25:03 2021 From: matt at openssl.org (Matt Caswell) Date: Fri, 21 May 2021 08:25:03 +0100 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: <84BD88CC-9ACB-4C86-AA77-762DC8F996F7@bluecedar.com> References: <87k0p89dfr.wl-levitte@openssl.org> <87y2cwmc3h.wl-levitte@openssl.org> <87mttbm1gf.wl-levitte@openssl.org> <87o8dfqbwh.wl-levitte@openssl.org> <87h7iz95a2.wl-levitte@openssl.org> <7CC6990D-7F93-4E61-BE46-116A635AC1FA@bluecedar.com> <2a669cf9-d629-da3c-e386-ac4da9c5677a@openssl.org> <84BD88CC-9ACB-4C86-AA77-762DC8F996F7@bluecedar.com> Message-ID: <7831e130-1e9b-79f3-3248-2df93d71e342@openssl.org> Hi Connor I'm not familiar with iOS so I don't know the specific issues and challenges that you might have running the test suite on that platform. You won't be able to just run "make test" since you are cross-compiling so the generated executables aren't suitable for running on the host platform. There are probably 3 main approaches I can think of for getting the tests to run that have been employed for other platforms: 1) Transfer the build directory to the target platform and run them there. This would assume you can run command line tools on the target and have access to perl and make etc there. I have no idea whether this is feasible for iOS. 2) Using qemu. For Android I know it is theoretically possible to run Android binaries on Linux using the qemu emulator. Of course Android is fundamentally Linux "under the hood" which potentially makes this possible. I don't know if something similar could be done for iOS. There are some notes on this approach at the end of the NOTES-ANDROID.md file in the root directory of the OpenSSL source. 3) Using EXE_SHELL. We have previously been able to cross compile for a windows target and run the tests on Linux using the wine emulator. To do this we set the environment variable "EXE_SHELL" to "wine" before running the tests. This invokes the EXE_SHELL command every time you want to run an application and passes the application name and parameters as arguments to the EXE_SHELL command. Its then the responsibility of the EXE_SHELL command to run the code. I really have no idea if any of these approaches are viable for iOS. Perhaps Richard may have other ideas. Matt On 20/05/2021 19:15, Connor Kelley wrote: > Hi Matt, > I did not see any suite to run for arm64, and got the following error: > MacBook-Pro:openssl ckelley$ make test > make depend && make _tests > make[1]: Entering directory '/Users/ckelley/openssl' > make[1]: Leaving directory '/Users/ckelley/openssl' > make[1]: Entering directory '/Users/ckelley/openssl' > perl ./util/wrap.pl apps/openssl fipsinstall -module > providers/fips.dylib -provider_name fips -mac_name HMAC -section_name > fips_sect > providers/fipsmodule.cnf > util/../util/shlib_wrap.sh: line 113: > /Users/ckelley/openssl/apps/openssl: Bad CPU type in executable > util/../util/shlib_wrap.sh: line 113: > /Users/ckelley/openssl/apps/openssl: Undefined error: 0 > > > Are there arm64 tests that can be run for a cross-compiled target like > we are attempting to build? I did not see anything specific or > applicable, but will be happy to run whatever if something exists. > Outside of that I was considering swapping out the existing FIPS library > that we have and see what happens, but that version is much older, so it > might not be immediately applicable. > > Thanks, > -Connor >> On May 20, 2021, at 2:11 PM, Matt Caswell > > wrote: >> >> Great news! Are you able to run the test suite? >> >> Matt >> >> On 20/05/2021 17:48, Connor Kelley wrote: >>> Hi Matt, >>> After pulling in the fixes for the broken assembly fixes I was able >>> to successfully build without any of the .conf changes so I was able >>> to cancel the PR. >>> Using top of tree I was able to successfully build and arm64 target >>> with ./Configure ios64-xcrun enable-fips enable-fips-securitychecks >>> -mios-version-min=11.0 && make >>> Thanks, >>> -Connor >>>> On May 19, 2021, at 10:59 AM, Matt Caswell >>> >>> >> wrote: >>>> >>>> Thanks Connor...lets continue the conversation in the PR itself. >>>> >>>> Matt >>>> >>>> On 19/05/2021 15:43, Connor Kelley wrote: >>>>> Hi Matt, >>>>> I think the PR is trivial based on what you?re talking about but >>>>> I?ll be happy to fill out one of those forms if you need it. >>>>> The PR for the changes is here: >>>>> https://github.com/openssl/openssl/pull/15352 >>>>> >>>>> >>>> > >>>>> >>>> >>>>> >>>> >> >>>>> Thanks, >>>>> -Connor >>>>>> On May 19, 2021, at 3:57 AM, Matt Caswell >>>>> >>>>> > >>>>> >>>>> >>> wrote: >>>>>> >>>>>> Hi Connor, >>>>>> >>>>>> Please submit them as a pull request on our public github site: >>>>>> >>>>>> https://github.com/openssl/openssl/pulls >>>>>> >>>>>> >>>>> > >>>>>> >>>>> >>>>>> >>>>> >> >>>>>> >>>>>> If you email the PR number here once created then we will know to >>>>>> give it the attention it deserves. >>>>>> >>>>>> If the changes are anything other than very trivial then we will >>>>>> also need an ICLA from you individually, as well as a CCLA from >>>>>> Blue Cedar. See: >>>>>> >>>>>> https://www.openssl.org/policies/cla.html >>>>>> >>>>>> >>>>> > >>>>>> >>>>>> Matt >>>>>> >>>>>> >>>>>> On 19/05/2021 01:54, Connor Kelley wrote: >>>>>>> Hi Richard, >>>>>>> I?ve got a working build that required a couple of updates to the >>>>>>> 15-iOS.conf file to get it current. With those changes plus the >>>>>>> configure invocation the build seemingly completes successfully. >>>>>>> What is the process for submitting a PR to get those changes in >>>>>>> and usable? >>>>>>> Thanks, >>>>>>> -Connor >>>>>>> Get Outlook for iOS > >>>>>>> ------------------------------------------------------------------------ >>>>>>> *From:* Richard Levitte >>>>>> > >>>>>>> *Sent:* Tuesday, May 18, 2021 4:05:25 PM >>>>>>> *To:* Nivedita Chevvakula >>>>>> > >>>>>>> *Cc:* Richard Levitte >>>>>> >; Tim Champagne >>>>>>> >; >>>>>>> Connor Kelley >>>>>> >; buildbot-admin at openssl.org >>>>>>> >>>>>> > >>>>>>> *Subject:* Re: [fips-sponsors] Buildbot workers >>>>>>> [ Also adding buildbot-admin at openssl.org >>>>>>> (I should have done that long >>>>>>> ago) ] >>>>>>> Yes, some technical details is what I'm trying to get. >>>>>>> Right now, that worker is building, sure, but that's a MacOS build, >>>>>>> which wasn't what you wanted. >>>>>>> So Tim, Connor, if you have something to share, I can hopefully do >>>>>>> better progress on our end. >>>>>>> Cheers, >>>>>>> Richard >>>>>>> On Mon, 17 May 2021 15:28:50 +0200, >>>>>>> Nivedita Chevvakula wrote: >>>>>>>> On this buildbot slave we don't run any our projects, we have >>>>>>>> set this slave only for buildbot worker. Please let me know if I >>>>>>>> give ssh creds it will expedite the process. >>>>>>>> Also adding Connor and Timmy, hopefully they can clarify on how >>>>>>>> we build OpenSSL project. >>>>>>>> Best, >>>>>>>> Niv >>>>>>>> ?On 5/13/21, 4:24 AM, "Richard Levitte" >>>>>>> > wrote: >>>>>>>> ???? What we expect to do is this at a minimum: >>>>>>>> ???????? perl Configure {args...} >>>>>>>> ???????? make >>>>>>>> ???? In the form that you filled in, there was the option to specify >>>>>>>> ???? necessary environment variables (which can affect the >>>>>>>> configuration >>>>>>>> ???? step) and configuration options.? I was hoping that would >>>>>>>> be enough to >>>>>>>> ???? get something going. >>>>>>>> ???? I do not know what you're talking about regarding a .conf >>>>>>>> file created >>>>>>>> ???? by the Configure step.? I understand that you have some >>>>>>>> sort of super >>>>>>>> ???? project that involves building OpenSSL as a component, >>>>>>>> though, so I >>>>>>>> ???? can only assume that somewhere in there, it should be >>>>>>>> possible to find >>>>>>>> ???? how the OpenSSL part is configured, i.e. I assume that >>>>>>>> there is a run >>>>>>>> ???? of Configure hiding in there somewhere, and that it should >>>>>>>> be possible >>>>>>>> ???? to see what arguments are used, as well as any relevant >>>>>>>> environment >>>>>>>> ???? variables. >>>>>>>> ???? Does this answer your question? >>>>>>>> ???? Cheers, >>>>>>>> ???? Richard >>>>>>>> ???? On Fri, 07 May 2021 15:12:11 +0200, >>>>>>>> ???? Nivedita Chevvakula wrote: >>>>>>>> ???? > ???? > We generate a project using cmake that gets built >>>>>>>> as a dependency of other components in our project. If you are >>>>>>>> trying to do - build everything using make, which requires a >>>>>>>> .conf file created with ./Configure step. If so should have one >>>>>>>> of those somewhere ?that satisfies what you are looking to >>>>>>>> produce for iOS, as well as a >>>>>>> different one for Android, please provide that we can put it in >>>>>>> place on the build bot and just use that? >>>>>>>> ???? > ???? > Please advise. >>>>>>>> ???? > ???? > Best, >>>>>>>> ???? > Niv >>>>>>>> ???? > ???? > ?On 5/4/21, 2:56 AM, "Richard Levitte" >>>>>>>> > wrote: >>>>>>>> ???? > ???? >???? Hi, >>>>>>>> ???? > ???? >???? The worker is connecting fine, so far so good. >>>>>>>> ???? > ???? >???? However, I realised that there are things >>>>>>>> missing, where we need >>>>>>>> ???? >???? information from you! >>>>>>>> ???? > ???? >???? This worker is meant to build for iOS, is it >>>>>>>> not? ?That should require >>>>>>>> ???? >???? extra OpenSSL configuration options.? So let me ask >>>>>>>> you this, when you >>>>>>>> ???? >???? usually build OpenSSL for iOS, exactly how do you >>>>>>>> usually configure >>>>>>>> ???? >???? OpenSSL? >>>>>>>> ???? > ???? >???? Cheers, >>>>>>>> ???? >???? Richard >>>>>>>> ???? > ???? >???? On Tue, 04 May 2021 03:46:17 +0200, >>>>>>>> ???? >???? Nivedita Chevvakula wrote: >>>>>>>> ???? >???? > ???? >???? > Richard, >>>>>>>> ???? >???? > ???? >???? > You can ignore my last mail with error >>>>>>>> starting buildbot. It is seems to work now after editing >>>>>>>> ???? >???? > syntax for python2.7. Also we have created user >>>>>>>> ?buildbot? for this mac as recommended. Please let >>>>>>>> ???? >???? > me know if we need to pass those credentials or >>>>>>>> need to setup anything else for the build bot. >>>>>>>> ???? >???? > ???? >???? > Best, >>>>>>>> ???? >???? > ???? >???? > Niv >>>>>>>> ???? >???? > ???? >???? > From: Nivedita Chevvakula >>>>>>>> > >>>>>>>> ???? >???? > Date: Monday, May 3, 2021 at 6:44 PM >>>>>>>> ???? >???? > To: Richard Levitte >>>>>>> > >>>>>>>> ???? >???? > Subject: Re: [fips-sponsors] Buildbot workers >>>>>>>> ???? >???? > ???? >???? > Richard, >>>>>>>> ???? >???? > ???? >???? > Buildbot has now installed with >>>>>>>> linker, make, c compilers. >>>>>>>> ???? >???? > ???? >???? > While starting the worker to connect >>>>>>>> to master after editing tac file as you mentioned getting >>>>>>>> ???? >???? > syntax error . not able to pin point why. Attaching >>>>>>>> the error log and the tac file here. Could you >>>>>>>> ???? >???? > please help. >>>>>>>> ???? >???? > ???? >???? > Best, >>>>>>>> ???? >???? > ???? >???? > Niv >>>>>>>> ???? >???? > ???? >???? > From: Nivedita Chevvakula >>>>>>>> > >>>>>>>> ???? >???? > Date: Monday, May 3, 2021 at 9:22 AM >>>>>>>> ???? >???? > To: Richard Levitte >>>>>>> > >>>>>>>> ???? >???? > Cc: "levitte at openssl.org >>>>>>>> " >>>>>>> >, Tim Champagne >>>>>>>> >, Kevin >>>>>>>> ???? >???? > Fox > >>>>>>>> ???? >???? > Subject: Re: [fips-sponsors] Buildbot workers >>>>>>>> ???? >???? > ???? >???? > Hi Richard, >>>>>>>> ???? >???? > ???? >???? > Thank you for sending the worker bot >>>>>>>> setup requirements, I will go thru and will set up the >>>>>>>> ???? >???? > workerbot and will install the rest. Do you have >>>>>>>> any deadline for this setup please share so that >>>>>>>> ???? >???? > it will help me prioritize. >>>>>>>> ???? >???? > ???? >???? > So far these tools are installed over >>>>>>>> the mac : >>>>>>>> ???? >???? > ???? >???? >? 1. Android Studio 4.1.3 >>>>>>>> ???? >???? >? 2. Xcode 12.5 >>>>>>>> ???? >???? >? 3. clang version 12.0.5 ???? >???? >? 4. Gcc >>>>>>>> ???? >???? >? 5. Visual Studio Community 2019 for Mac >>>>>>>> ???? >???? > ???? >???? > === Visual Studio Community 2019 for >>>>>>>> Mac === >>>>>>>> ???? >???? > ???? >???? > Version 8.9.7 (build 8) >>>>>>>> ???? >???? > ???? >???? > Installation UUID: >>>>>>>> f1ca8dad-7314-419a-8a39-880ba8a71230 >>>>>>>> ???? >???? > ???? >???? > GTK+ 2.24.23 (Raleigh theme) >>>>>>>> ???? >???? > ???? >???? > Xamarin.Mac 6.18.0.23 (d16-6 / 088c73638) >>>>>>>> ???? >???? > ???? >???? > Package version: 612000125 >>>>>>>> ???? >???? > ???? >???? > === Mono Framework MDK === >>>>>>>> ???? >???? > ???? >???? > Runtime: >>>>>>>> ???? >???? > ???? >???? > Mono 6.12.0.125 (2020-02/8c552e98bd6) >>>>>>>> (64-bit) >>>>>>>> ???? >???? > ???? >???? > Package version: 612000125 >>>>>>>> ???? >???? > ???? >???? > === Roslyn (Language Service) === >>>>>>>> ???? >???? > ???? >???? > >>>>>>>> 3.9.0-6.21152.10+c10f884b30737542ddd84ca889a4aad9281ce210 >>>>>>>> ???? >???? > ???? >???? > === NuGet === >>>>>>>> ???? >???? > ???? >???? > Version: 5.8.0.6860 >>>>>>>> ???? >???? > ???? >???? > === .NET Core SDK === >>>>>>>> ???? >???? > ???? >???? > SDK: >>>>>>>> /usr/local/share/dotnet/sdk/5.0.202/Sdks >>>>>>>> ???? >???? > ???? >???? > SDK Versions: >>>>>>>> ???? >???? > ???? >???? > 5.0.202 >>>>>>>> ???? >???? > ???? >???? > 3.1.408 >>>>>>>> ???? >???? > ???? >???? > 2.1.4 >>>>>>>> ???? >???? > ???? >???? > MSBuild SDKs: /Applications/Visual >>>>>>>> Studio.app/Contents/Resources/lib/monodevelop/bin/MSBuild/ >>>>>>>> ???? >???? > Current/bin/Sdks >>>>>>>> ???? >???? > ???? >???? > === .NET Core Runtime === >>>>>>>> ???? >???? > ???? >???? > Runtime: /usr/local/share/dotnet/dotnet >>>>>>>> ???? >???? > ???? >???? > Runtime Versions: >>>>>>>> ???? >???? > ???? >???? > 5.0.5 >>>>>>>> ???? >???? > ???? >???? > 3.1.14 >>>>>>>> ???? >???? > ???? >???? > 2.0.5 >>>>>>>> ???? >???? > ???? >???? > === .NET Core 3.1 SDK === >>>>>>>> ???? >???? > ???? >???? > SDK: 3.1.408 >>>>>>>> ???? >???? > ???? >???? > === Xamarin.Profiler === >>>>>>>> ???? >???? > ???? >???? > Version: 1.6.15.68 >>>>>>>> ???? >???? > ???? >???? > Location: /Applications/Xamarin >>>>>>>> Profiler.app/Contents/MacOS/Xamarin Profiler >>>>>>>> ???? >???? > ???? >???? > === Updater === >>>>>>>> ???? >???? > ???? >???? > Version: 11 >>>>>>>> ???? >???? > ???? >???? > === Apple Developer Tools === >>>>>>>> ???? >???? > ???? >???? > Xcode 12.5 (18205) >>>>>>>> ???? >???? > ???? >???? > Build 12E262 >>>>>>>> ???? >???? > ???? >???? > === Xamarin.Mac === >>>>>>>> ???? >???? > ???? >???? > Xamarin.Mac not installed. Can't find >>>>>>>> /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/ >>>>>>>> ???? >???? > Version. >>>>>>>> ???? >???? > ???? >???? > === Xamarin.iOS === >>>>>>>> ???? >???? > ???? >???? > Xamarin.iOS not installed. >>>>>>>> ???? >???? > ???? >???? > Can't find mtouch or the Version file >>>>>>>> at /Library/Frameworks/Xamarin.iOS.framework/Versions/ >>>>>>>> ???? >???? > Current. >>>>>>>> ???? >???? > ???? >???? > === Xamarin Designer === >>>>>>>> ???? >???? > ???? >???? > Version: 16.9.0.324 >>>>>>>> ???? >???? > ???? >???? > Hash: b1e216c75 >>>>>>>> ???? >???? > ???? >???? > Branch: remotes/origin/d16-9 >>>>>>>> ???? >???? > ???? >???? > Build date: 2021-04-16 00:02:50 UTC >>>>>>>> ???? >???? > ???? >???? > === Xamarin.Android === >>>>>>>> ???? >???? > ???? >???? > Version: 11.2.2.1 (Visual Studio >>>>>>>> Community) >>>>>>>> ???? >???? > ???? >???? > Commit: xamarin-android/d16-9/877f572 >>>>>>>> ???? >???? > ???? >???? > Android SDK: >>>>>>>> /Users/ec2-user/Library/Developer/Xamarin/android-sdk-macosx >>>>>>>> ???? >???? > ???? >???? > Supported Android versions: >>>>>>>> ???? >???? > ???? >???? > None installed >>>>>>>> ???? >???? > ???? >???? > SDK Tools Version: 26.1.1 >>>>>>>> ???? >???? > ???? >???? > SDK Platform Tools Version: 30.0.4 >>>>>>>> ???? >???? > ???? >???? > SDK Build Tools Version: 30.0.2 >>>>>>>> ???? >???? > ???? >???? > Build Information: >>>>>>>> ???? >???? > ???? >???? > Mono: 5e9cb6d >>>>>>>> ???? >???? > ???? >???? > Java.Interop: >>>>>>>> xamarin/java.interop/d16-9 at 54f8c24 >>>>>>>> ???? >???? > ???? >???? > ProGuard: >>>>>>>> Guardsquare/proguard/v7.0.1 at 912d149 >>>>>>>> ???? >???? > ???? >???? > SQLite: xamarin/sqlite/3.34.1 at daff8f4 >>>>>>>> ???? >???? > ???? >???? > Xamarin.Android Tools: >>>>>>>> xamarin/xamarin-android-tools/d16-9 at d210f11 >>>>>>>> ???? >???? > ???? >???? > === Microsoft OpenJDK for Mobile === >>>>>>>> ???? >???? > ???? >???? > Java SDK: >>>>>>>> /Users/ec2-user/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_1.8.0.25 >>>>>>>> ???? >???? > ???? >???? > 1.8.0-25 >>>>>>>> ???? >???? > ???? >???? > Android Designer EPL code available here: >>>>>>>> ???? >???? > ???? >???? > >>>>>>>> https://github.com/xamarin/AndroidDesigner.EPL >>>>>>>> >>>>>>> >>>>>> > >>>>>>>> ???? >???? > ???? >???? > === Android SDK Manager === >>>>>>>> ???? >???? > ???? >???? > Version: 16.9.0.22 >>>>>>>> ???? >???? > ???? >???? > Hash: a391de2 >>>>>>>> ???? >???? > ???? >???? > Branch: remotes/origin/d16-9~2 >>>>>>>> ???? >???? > ???? >???? > Build date: 2021-03-24 08:30:26 UTC >>>>>>>> ???? >???? > ???? >???? > === Android Device Manager === >>>>>>>> ???? >???? > ???? >???? > Version: 16.9.0.17 >>>>>>>> ???? >???? > ???? >???? > Hash: fc2b3db >>>>>>>> ???? >???? > ???? >???? > Branch: remotes/origin/dev/jmt/d16-9bump~1 >>>>>>>> ???? >???? > ???? >???? > Build date: 2021-03-24 08:30:44 UTC >>>>>>>> ???? >???? > ???? >???? > === Build Information === >>>>>>>> ???? >???? > ???? >???? > Release ID: 809070008 >>>>>>>> ???? >???? > ???? >???? > Git revision: >>>>>>>> 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>>>>>>> ???? >???? > ???? >???? > Build date: 2021-04-16 07:38:03-04 >>>>>>>> ???? >???? > ???? >???? > Build branch: release-8.9 >>>>>>>> ???? >???? > ???? >???? > Xamarin extensions: >>>>>>>> 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>>>>>>> ???? >???? > ???? >???? > === Operating System === >>>>>>>> ???? >???? > ???? >???? > Mac OS X 10.16.0 >>>>>>>> ???? >???? > ???? >???? > Darwin 20.3.0 Darwin Kernel Version 20.3.0 >>>>>>>> ???? >???? > ???? >???? > Thu Jan 21 00:07:06 PST 2021 >>>>>>>> ???? >???? > ???? >???? > root:xnu-7195.81.3~1/RELEASE_X86_64 x86_64 >>>>>>>> ???? >???? > ???? >???? > Best, >>>>>>>> ???? >???? > ???? >???? > Niv >>>>>>>> ???? >???? > ???? >???? > From: Richard Levitte >>>>>>>> > >>>>>>>> ???? >???? > Date: Monday, May 3, 2021 at 4:54 AM >>>>>>>> ???? >???? > To: Nivedita Chevvakula >>>>>>> > >>>>>>>> ???? >???? > Cc: levitte at openssl.org >>>>>>>> >>>>>>> >, Tim Champagne >>>>>>>> >, >>>>>>>> Kevin Fox >>>>>>>> ???? >???? > > >>>>>>>> ???? >???? > Subject: Re: [fips-sponsors] Buildbot workers >>>>>>>> ???? >???? > ???? >???? > Hi, >>>>>>>> ???? >???? > ???? >???? > Thank you for offering workers to us! >>>>>>>> ???? >???? > ???? >???? > To be able to set up your worker, you >>>>>>>> must use version 2.6.0 or >>>>>>>> ???? >???? > higher.? Older version do not support TLS-protected >>>>>>>> connections. >>>>>>>> ???? >???? > ???? >???? > Please see these instructions for >>>>>>>> installing the buildbot worker >>>>>>>> ???? >???? > software: >>>>>>>> ???? >???? > ???? >???? > >>>>>>>> http://docs.buildbot.net/latest/manual/installation/worker.html >>>>>>>> >>>>>>> >>>>>> > >>>>>>>> ???? >???? > ???? >???? > When buildbot has been installed on >>>>>>>> the platform where the buildbot >>>>>>>> ???? >???? > worker is to be run, this is how a worker is created: >>>>>>>> ???? >???? > ???? >???? >???? $ buildbot-worker create-worker >>>>>>>> --use-tls BASEDIR \ >>>>>>>> ???? >???? > buildbot.openssl.org:9989 >>>>>>>> 'bluecedar-01' 'Rak;osErfabOn5' >>>>>>>> ???? >???? > ???? >???? > where BASEDIR is determined by you. >>>>>>>> See further down for a few notes >>>>>>>> ???? >???? > on TLS. >>>>>>>> ???? >???? > ???? >???? > To run a buildbot worker, you do this: >>>>>>>> ???? >???? > ???? >???? >???? $ buildbot-worker start BASEDIR >>>>>>>> ???? >???? > ???? >???? > Apart from the software needed to run >>>>>>>> a buildbot worker, and the >>>>>>>> ???? >???? > utilities that are the normal part of the operating >>>>>>>> system, you also >>>>>>>> ???? >???? > need to ensure that the following components are >>>>>>>> available: >>>>>>>> ???? >???? > ???? >???? > -?? toolchains, i.e. C compiler, >>>>>>>> linker, make.? If you have specified >>>>>>>> ???? >???? >???? toolchains in the worker request form, you need >>>>>>>> to ensure that all >>>>>>>> ???? >???? >???? of them are installed. >>>>>>>> ???? >???? > ???? >???? > -?? git >>>>>>>> ???? >???? > ???? >???? > Regarding TLS, it may be that the >>>>>>>> buildbot worker platform doesn't >>>>>>>> ???? >???? > have the appropriate certification verification >>>>>>>> roots set up.? In that >>>>>>>> ???? >???? > case, you may need to apply the attached >>>>>>>> buildbot.tac patch, and store >>>>>>>> ???? >???? > the attached PEM files in a directory of your >>>>>>>> choice. ?Finish up by >>>>>>>> ???? >???? > find the string '/PATH/TO/ssl-roots-dir' and >>>>>>>> replace its contents with >>>>>>>> ???? >???? > the path of directory where you stored the PEM files. >>>>>>>> ???? >???? > ???? >???? > ???? >???? -- ???? >???? Richard >>>>>>>> Levitte levitte at openssl.org >>>>>>>> ???? >???? OpenSSL Project http://www.openssl.org/~levitte/ >>>>>>>> >>>>>>>> >>>>>>> > >>>>>>>> ???? -- ???? Richard Levitte levitte at openssl.org >>>>>>>> >>>>>>>> ???? OpenSSL Project http://www.openssl.org/~levitte/ >>>>>>>> >>>>>>>> >>>>>>> > >>>>>>> -- >>>>>>> Richard Levitte levitte at openssl.org >>>>>>> OpenSSL Project http://www.openssl.org/~levitte/ >>>>>>> >>>>>>> > >>>>>>> _______________________________________________ >>>>>>> buildbot-admin mailing list >>>>>>> buildbot-admin at openssl.org >>>>>>> https://mta.openssl.org/mailman/listinfo/buildbot-admin > From ckelley at bluecedar.com Tue May 25 15:12:14 2021 From: ckelley at bluecedar.com (Connor Kelley) Date: Tue, 25 May 2021 11:12:14 -0400 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: <7831e130-1e9b-79f3-3248-2df93d71e342@openssl.org> References: <87k0p89dfr.wl-levitte@openssl.org> <87y2cwmc3h.wl-levitte@openssl.org> <87mttbm1gf.wl-levitte@openssl.org> <87o8dfqbwh.wl-levitte@openssl.org> <87h7iz95a2.wl-levitte@openssl.org> <7CC6990D-7F93-4E61-BE46-116A635AC1FA@bluecedar.com> <2a669cf9-d629-da3c-e386-ac4da9c5677a@openssl.org> <84BD88CC-9ACB-4C86-AA77-762DC8F996F7@bluecedar.com> <7831e130-1e9b-79f3-3248-2df93d71e342@openssl.org> Message-ID: <15D64FB6-775C-4907-A6BF-17FC1B4CF8E6@bluecedar.com> Hi Matt, That?s what I was thinking as well. None of those three options are applicable on iOS, so it sounds like in order to test this in any meaningful way on iOS I?m going to need to link against that library with our product, replacing the current version of our FIPS library. I?m open to other options though, as I?m sure there?s some defined test harness for the final FIPS validation, unless I?m mistaken. Thanks, -Connr > On May 21, 2021, at 3:25 AM, Matt Caswell wrote: > > Hi Connor > > I'm not familiar with iOS so I don't know the specific issues and challenges that you might have running the test suite on that platform. You won't be able to just run "make test" since you are cross-compiling so the generated executables aren't suitable for running on the host platform. > > There are probably 3 main approaches I can think of for getting the tests to run that have been employed for other platforms: > > 1) Transfer the build directory to the target platform and run them there. This would assume you can run command line tools on the target and have access to perl and make etc there. I have no idea whether this is feasible for iOS. > > 2) Using qemu. For Android I know it is theoretically possible to run Android binaries on Linux using the qemu emulator. Of course Android is fundamentally Linux "under the hood" which potentially makes this possible. I don't know if something similar could be done for iOS. There are some notes on this approach at the end of the NOTES-ANDROID.md file in the root directory of the OpenSSL source. > > 3) Using EXE_SHELL. We have previously been able to cross compile for a windows target and run the tests on Linux using the wine emulator. To do this we set the environment variable "EXE_SHELL" to "wine" before running the tests. This invokes the EXE_SHELL command every time you want to run an application and passes the application name and parameters as arguments to the EXE_SHELL command. Its then the responsibility of the EXE_SHELL command to run the code. > > I really have no idea if any of these approaches are viable for iOS. Perhaps Richard may have other ideas. > > Matt > > > On 20/05/2021 19:15, Connor Kelley wrote: >> Hi Matt, >> I did not see any suite to run for arm64, and got the following error: >> MacBook-Pro:openssl ckelley$ make test >> make depend && make _tests >> make[1]: Entering directory '/Users/ckelley/openssl' >> make[1]: Leaving directory '/Users/ckelley/openssl' >> make[1]: Entering directory '/Users/ckelley/openssl' >> perl ./util/wrap.pl apps/openssl fipsinstall -module providers/fips.dylib -provider_name fips -mac_name HMAC -section_name fips_sect > providers/fipsmodule.cnf >> util/../util/shlib_wrap.sh: line 113: /Users/ckelley/openssl/apps/openssl: Bad CPU type in executable >> util/../util/shlib_wrap.sh: line 113: /Users/ckelley/openssl/apps/openssl: Undefined error: 0 >> Are there arm64 tests that can be run for a cross-compiled target like we are attempting to build? I did not see anything specific or applicable, but will be happy to run whatever if something exists. >> Outside of that I was considering swapping out the existing FIPS library that we have and see what happens, but that version is much older, so it might not be immediately applicable. >> Thanks, >> -Connor >>> On May 20, 2021, at 2:11 PM, Matt Caswell > wrote: >>> >>> Great news! Are you able to run the test suite? >>> >>> Matt >>> >>> On 20/05/2021 17:48, Connor Kelley wrote: >>>> Hi Matt, >>>> After pulling in the fixes for the broken assembly fixes I was able to successfully build without any of the .conf changes so I was able to cancel the PR. >>>> Using top of tree I was able to successfully build and arm64 target with ./Configure ios64-xcrun enable-fips enable-fips-securitychecks -mios-version-min=11.0 && make >>>> Thanks, >>>> -Connor >>>>> On May 19, 2021, at 10:59 AM, Matt Caswell >> wrote: >>>>> >>>>> Thanks Connor...lets continue the conversation in the PR itself. >>>>> >>>>> Matt >>>>> >>>>> On 19/05/2021 15:43, Connor Kelley wrote: >>>>>> Hi Matt, >>>>>> I think the PR is trivial based on what you?re talking about but I?ll be happy to fill out one of those forms if you need it. >>>>>> The PR for the changes is here: https://github.com/openssl/openssl/pull/15352 > >> >>>>>> Thanks, >>>>>> -Connor >>>>>>> On May 19, 2021, at 3:57 AM, Matt Caswell > >>> wrote: >>>>>>> >>>>>>> Hi Connor, >>>>>>> >>>>>>> Please submit them as a pull request on our public github site: >>>>>>> >>>>>>> https://github.com/openssl/openssl/pulls > >> >>>>>>> >>>>>>> If you email the PR number here once created then we will know to give it the attention it deserves. >>>>>>> >>>>>>> If the changes are anything other than very trivial then we will also need an ICLA from you individually, as well as a CCLA from Blue Cedar. See: >>>>>>> >>>>>>> https://www.openssl.org/policies/cla.html > >>>>>>> >>>>>>> Matt >>>>>>> >>>>>>> >>>>>>> On 19/05/2021 01:54, Connor Kelley wrote: >>>>>>>> Hi Richard, >>>>>>>> I?ve got a working build that required a couple of updates to the 15-iOS.conf file to get it current. With those changes plus the configure invocation the build seemingly completes successfully. What is the process for submitting a PR to get those changes in and usable? >>>>>>>> Thanks, >>>>>>>> -Connor >>>>>>>> Get Outlook for iOS > >>>>>>>> ------------------------------------------------------------------------ >>>>>>>> *From:* Richard Levitte > >>>>>>>> *Sent:* Tuesday, May 18, 2021 4:05:25 PM >>>>>>>> *To:* Nivedita Chevvakula > >>>>>>>> *Cc:* Richard Levitte >; Tim Champagne >; Connor Kelley >; buildbot-admin at openssl.org > >>>>>>>> *Subject:* Re: [fips-sponsors] Buildbot workers >>>>>>>> [ Also adding buildbot-admin at openssl.org (I should have done that long ago) ] >>>>>>>> Yes, some technical details is what I'm trying to get. >>>>>>>> Right now, that worker is building, sure, but that's a MacOS build, >>>>>>>> which wasn't what you wanted. >>>>>>>> So Tim, Connor, if you have something to share, I can hopefully do >>>>>>>> better progress on our end. >>>>>>>> Cheers, >>>>>>>> Richard >>>>>>>> On Mon, 17 May 2021 15:28:50 +0200, >>>>>>>> Nivedita Chevvakula wrote: >>>>>>>>> On this buildbot slave we don't run any our projects, we have set this slave only for buildbot worker. Please let me know if I give ssh creds it will expedite the process. >>>>>>>>> Also adding Connor and Timmy, hopefully they can clarify on how we build OpenSSL project. >>>>>>>>> Best, >>>>>>>>> Niv >>>>>>>>> ?On 5/13/21, 4:24 AM, "Richard Levitte" > wrote: >>>>>>>>> What we expect to do is this at a minimum: >>>>>>>>> perl Configure {args...} >>>>>>>>> make >>>>>>>>> In the form that you filled in, there was the option to specify >>>>>>>>> necessary environment variables (which can affect the configuration >>>>>>>>> step) and configuration options. I was hoping that would be enough to >>>>>>>>> get something going. >>>>>>>>> I do not know what you're talking about regarding a .conf file created >>>>>>>>> by the Configure step. I understand that you have some sort of super >>>>>>>>> project that involves building OpenSSL as a component, though, so I >>>>>>>>> can only assume that somewhere in there, it should be possible to find >>>>>>>>> how the OpenSSL part is configured, i.e. I assume that there is a run >>>>>>>>> of Configure hiding in there somewhere, and that it should be possible >>>>>>>>> to see what arguments are used, as well as any relevant environment >>>>>>>>> variables. >>>>>>>>> Does this answer your question? >>>>>>>>> Cheers, >>>>>>>>> Richard >>>>>>>>> On Fri, 07 May 2021 15:12:11 +0200, >>>>>>>>> Nivedita Chevvakula wrote: >>>>>>>>> > > We generate a project using cmake that gets built as a dependency of other components in our project. If you are trying to do - build everything using make, which requires a .conf file created with ./Configure step. If so should have one of those somewhere that satisfies what you are looking to produce for iOS, as well as a >>>>>>>> different one for Android, please provide that we can put it in place on the build bot and just use that? >>>>>>>>> > > Please advise. >>>>>>>>> > > Best, >>>>>>>>> > Niv >>>>>>>>> > > ?On 5/4/21, 2:56 AM, "Richard Levitte" > wrote: >>>>>>>>> > > Hi, >>>>>>>>> > > The worker is connecting fine, so far so good. >>>>>>>>> > > However, I realised that there are things missing, where we need >>>>>>>>> > information from you! >>>>>>>>> > > This worker is meant to build for iOS, is it not? That should require >>>>>>>>> > extra OpenSSL configuration options. So let me ask you this, when you >>>>>>>>> > usually build OpenSSL for iOS, exactly how do you usually configure >>>>>>>>> > OpenSSL? >>>>>>>>> > > Cheers, >>>>>>>>> > Richard >>>>>>>>> > > On Tue, 04 May 2021 03:46:17 +0200, >>>>>>>>> > Nivedita Chevvakula wrote: >>>>>>>>> > > > > Richard, >>>>>>>>> > > > > You can ignore my last mail with error starting buildbot. It is seems to work now after editing >>>>>>>>> > > syntax for python2.7. Also we have created user ?buildbot? for this mac as recommended. Please let >>>>>>>>> > > me know if we need to pass those credentials or need to setup anything else for the build bot. >>>>>>>>> > > > > Best, >>>>>>>>> > > > > Niv >>>>>>>>> > > > > From: Nivedita Chevvakula > >>>>>>>>> > > Date: Monday, May 3, 2021 at 6:44 PM >>>>>>>>> > > To: Richard Levitte > >>>>>>>>> > > Subject: Re: [fips-sponsors] Buildbot workers >>>>>>>>> > > > > Richard, >>>>>>>>> > > > > Buildbot has now installed with linker, make, c compilers. >>>>>>>>> > > > > While starting the worker to connect to master after editing tac file as you mentioned getting >>>>>>>>> > > syntax error . not able to pin point why. Attaching the error log and the tac file here. Could you >>>>>>>>> > > please help. >>>>>>>>> > > > > Best, >>>>>>>>> > > > > Niv >>>>>>>>> > > > > From: Nivedita Chevvakula > >>>>>>>>> > > Date: Monday, May 3, 2021 at 9:22 AM >>>>>>>>> > > To: Richard Levitte > >>>>>>>>> > > Cc: "levitte at openssl.org " >, Tim Champagne >, Kevin >>>>>>>>> > > Fox > >>>>>>>>> > > Subject: Re: [fips-sponsors] Buildbot workers >>>>>>>>> > > > > Hi Richard, >>>>>>>>> > > > > Thank you for sending the worker bot setup requirements, I will go thru and will set up the >>>>>>>>> > > workerbot and will install the rest. Do you have any deadline for this setup please share so that >>>>>>>>> > > it will help me prioritize. >>>>>>>>> > > > > So far these tools are installed over the mac : >>>>>>>>> > > > > 1. Android Studio 4.1.3 >>>>>>>>> > > 2. Xcode 12.5 >>>>>>>>> > > 3. clang version 12.0.5 > > 4. Gcc >>>>>>>>> > > 5. Visual Studio Community 2019 for Mac >>>>>>>>> > > > > === Visual Studio Community 2019 for Mac === >>>>>>>>> > > > > Version 8.9.7 (build 8) >>>>>>>>> > > > > Installation UUID: f1ca8dad-7314-419a-8a39-880ba8a71230 >>>>>>>>> > > > > GTK+ 2.24.23 (Raleigh theme) >>>>>>>>> > > > > Xamarin.Mac 6.18.0.23 (d16-6 / 088c73638) >>>>>>>>> > > > > Package version: 612000125 >>>>>>>>> > > > > === Mono Framework MDK === >>>>>>>>> > > > > Runtime: >>>>>>>>> > > > > Mono 6.12.0.125 (2020-02/8c552e98bd6) (64-bit) >>>>>>>>> > > > > Package version: 612000125 >>>>>>>>> > > > > === Roslyn (Language Service) === >>>>>>>>> > > > > 3.9.0-6.21152.10+c10f884b30737542ddd84ca889a4aad9281ce210 >>>>>>>>> > > > > === NuGet === >>>>>>>>> > > > > Version: 5.8.0.6860 >>>>>>>>> > > > > === .NET Core SDK === >>>>>>>>> > > > > SDK: /usr/local/share/dotnet/sdk/5.0.202/Sdks >>>>>>>>> > > > > SDK Versions: >>>>>>>>> > > > > 5.0.202 >>>>>>>>> > > > > 3.1.408 >>>>>>>>> > > > > 2.1.4 >>>>>>>>> > > > > MSBuild SDKs: /Applications/Visual Studio.app/Contents/Resources/lib/monodevelop/bin/MSBuild/ >>>>>>>>> > > Current/bin/Sdks >>>>>>>>> > > > > === .NET Core Runtime === >>>>>>>>> > > > > Runtime: /usr/local/share/dotnet/dotnet >>>>>>>>> > > > > Runtime Versions: >>>>>>>>> > > > > 5.0.5 >>>>>>>>> > > > > 3.1.14 >>>>>>>>> > > > > 2.0.5 >>>>>>>>> > > > > === .NET Core 3.1 SDK === >>>>>>>>> > > > > SDK: 3.1.408 >>>>>>>>> > > > > === Xamarin.Profiler === >>>>>>>>> > > > > Version: 1.6.15.68 >>>>>>>>> > > > > Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler >>>>>>>>> > > > > === Updater === >>>>>>>>> > > > > Version: 11 >>>>>>>>> > > > > === Apple Developer Tools === >>>>>>>>> > > > > Xcode 12.5 (18205) >>>>>>>>> > > > > Build 12E262 >>>>>>>>> > > > > === Xamarin.Mac === >>>>>>>>> > > > > Xamarin.Mac not installed. Can't find /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/ >>>>>>>>> > > Version. >>>>>>>>> > > > > === Xamarin.iOS === >>>>>>>>> > > > > Xamarin.iOS not installed. >>>>>>>>> > > > > Can't find mtouch or the Version file at /Library/Frameworks/Xamarin.iOS.framework/Versions/ >>>>>>>>> > > Current. >>>>>>>>> > > > > === Xamarin Designer === >>>>>>>>> > > > > Version: 16.9.0.324 >>>>>>>>> > > > > Hash: b1e216c75 >>>>>>>>> > > > > Branch: remotes/origin/d16-9 >>>>>>>>> > > > > Build date: 2021-04-16 00:02:50 UTC >>>>>>>>> > > > > === Xamarin.Android === >>>>>>>>> > > > > Version: 11.2.2.1 (Visual Studio Community) >>>>>>>>> > > > > Commit: xamarin-android/d16-9/877f572 >>>>>>>>> > > > > Android SDK: /Users/ec2-user/Library/Developer/Xamarin/android-sdk-macosx >>>>>>>>> > > > > Supported Android versions: >>>>>>>>> > > > > None installed >>>>>>>>> > > > > SDK Tools Version: 26.1.1 >>>>>>>>> > > > > SDK Platform Tools Version: 30.0.4 >>>>>>>>> > > > > SDK Build Tools Version: 30.0.2 >>>>>>>>> > > > > Build Information: >>>>>>>>> > > > > Mono: 5e9cb6d >>>>>>>>> > > > > Java.Interop: xamarin/java.interop/d16-9 at 54f8c24 >>>>>>>>> > > > > ProGuard: Guardsquare/proguard/v7.0.1 at 912d149 >>>>>>>>> > > > > SQLite: xamarin/sqlite/3.34.1 at daff8f4 >>>>>>>>> > > > > Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-9 at d210f11 >>>>>>>>> > > > > === Microsoft OpenJDK for Mobile === >>>>>>>>> > > > > Java SDK: /Users/ec2-user/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_1.8.0.25 >>>>>>>>> > > > > 1.8.0-25 >>>>>>>>> > > > > Android Designer EPL code available here: >>>>>>>>> > > > > https://github.com/xamarin/AndroidDesigner.EPL >>>>>>>> > >>>>>>>>> > > > > === Android SDK Manager === >>>>>>>>> > > > > Version: 16.9.0.22 >>>>>>>>> > > > > Hash: a391de2 >>>>>>>>> > > > > Branch: remotes/origin/d16-9~2 >>>>>>>>> > > > > Build date: 2021-03-24 08:30:26 UTC >>>>>>>>> > > > > === Android Device Manager === >>>>>>>>> > > > > Version: 16.9.0.17 >>>>>>>>> > > > > Hash: fc2b3db >>>>>>>>> > > > > Branch: remotes/origin/dev/jmt/d16-9bump~1 >>>>>>>>> > > > > Build date: 2021-03-24 08:30:44 UTC >>>>>>>>> > > > > === Build Information === >>>>>>>>> > > > > Release ID: 809070008 >>>>>>>>> > > > > Git revision: 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>>>>>>>> > > > > Build date: 2021-04-16 07:38:03-04 >>>>>>>>> > > > > Build branch: release-8.9 >>>>>>>>> > > > > Xamarin extensions: 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>>>>>>>> > > > > === Operating System === >>>>>>>>> > > > > Mac OS X 10.16.0 >>>>>>>>> > > > > Darwin 20.3.0 Darwin Kernel Version 20.3.0 >>>>>>>>> > > > > Thu Jan 21 00:07:06 PST 2021 >>>>>>>>> > > > > root:xnu-7195.81.3~1/RELEASE_X86_64 x86_64 >>>>>>>>> > > > > Best, >>>>>>>>> > > > > Niv >>>>>>>>> > > > > From: Richard Levitte > >>>>>>>>> > > Date: Monday, May 3, 2021 at 4:54 AM >>>>>>>>> > > To: Nivedita Chevvakula > >>>>>>>>> > > Cc: levitte at openssl.org >, Tim Champagne >, Kevin Fox >>>>>>>>> > > > >>>>>>>>> > > Subject: Re: [fips-sponsors] Buildbot workers >>>>>>>>> > > > > Hi, >>>>>>>>> > > > > Thank you for offering workers to us! >>>>>>>>> > > > > To be able to set up your worker, you must use version 2.6.0 or >>>>>>>>> > > higher. Older version do not support TLS-protected connections. >>>>>>>>> > > > > Please see these instructions for installing the buildbot worker >>>>>>>>> > > software: >>>>>>>>> > > > > http://docs.buildbot.net/latest/manual/installation/worker.html >>>>>>>> > >>>>>>>>> > > > > When buildbot has been installed on the platform where the buildbot >>>>>>>>> > > worker is to be run, this is how a worker is created: >>>>>>>>> > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ >>>>>>>>> > > buildbot.openssl.org:9989 'bluecedar-01' 'Rak;osErfabOn5' >>>>>>>>> > > > > where BASEDIR is determined by you. See further down for a few notes >>>>>>>>> > > on TLS. >>>>>>>>> > > > > To run a buildbot worker, you do this: >>>>>>>>> > > > > $ buildbot-worker start BASEDIR >>>>>>>>> > > > > Apart from the software needed to run a buildbot worker, and the >>>>>>>>> > > utilities that are the normal part of the operating system, you also >>>>>>>>> > > need to ensure that the following components are available: >>>>>>>>> > > > > - toolchains, i.e. C compiler, linker, make. If you have specified >>>>>>>>> > > toolchains in the worker request form, you need to ensure that all >>>>>>>>> > > of them are installed. >>>>>>>>> > > > > - git >>>>>>>>> > > > > Regarding TLS, it may be that the buildbot worker platform doesn't >>>>>>>>> > > have the appropriate certification verification roots set up. In that >>>>>>>>> > > case, you may need to apply the attached buildbot.tac patch, and store >>>>>>>>> > > the attached PEM files in a directory of your choice. Finish up by >>>>>>>>> > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with >>>>>>>>> > > the path of directory where you stored the PEM files. >>>>>>>>> > > > > > -- > Richard Levitte levitte at openssl.org >>>>>>>>> > OpenSSL Project http://www.openssl.org/~levitte/ > >>>>>>>>> -- Richard Levitte levitte at openssl.org >>>>>>>>> OpenSSL Project http://www.openssl.org/~levitte/ > >>>>>>>> -- >>>>>>>> Richard Levitte levitte at openssl.org >>>>>>>> OpenSSL Project http://www.openssl.org/~levitte/ > >>>>>>>> _______________________________________________ >>>>>>>> buildbot-admin mailing list >>>>>>>> buildbot-admin at openssl.org >>>>>>>> https://mta.openssl.org/mailman/listinfo/buildbot-admin From matt at openssl.org Wed May 26 10:05:24 2021 From: matt at openssl.org (Matt Caswell) Date: Wed, 26 May 2021 11:05:24 +0100 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: <15D64FB6-775C-4907-A6BF-17FC1B4CF8E6@bluecedar.com> References: <87k0p89dfr.wl-levitte@openssl.org> <87mttbm1gf.wl-levitte@openssl.org> <87o8dfqbwh.wl-levitte@openssl.org> <87h7iz95a2.wl-levitte@openssl.org> <7CC6990D-7F93-4E61-BE46-116A635AC1FA@bluecedar.com> <2a669cf9-d629-da3c-e386-ac4da9c5677a@openssl.org> <84BD88CC-9ACB-4C86-AA77-762DC8F996F7@bluecedar.com> <7831e130-1e9b-79f3-3248-2df93d71e342@openssl.org> <15D64FB6-775C-4907-A6BF-17FC1B4CF8E6@bluecedar.com> Message-ID: Unfortunately that's not going to work for us. It's a requirement for us that "make test" works - and without using Blue Cedar proprietary code. :-( Matt On 25/05/2021 16:12, Connor Kelley wrote: > Hi Matt, > That?s what I was thinking as well. None of those three options are applicable on iOS, so it sounds like in order to test this in any meaningful way on iOS I?m going to need to link against that library with our product, replacing the current version of our FIPS library. I?m open to other options though, as I?m sure there?s some defined test harness for the final FIPS validation, unless I?m mistaken. > > Thanks, > -Connr > >> On May 21, 2021, at 3:25 AM, Matt Caswell wrote: >> >> Hi Connor >> >> I'm not familiar with iOS so I don't know the specific issues and challenges that you might have running the test suite on that platform. You won't be able to just run "make test" since you are cross-compiling so the generated executables aren't suitable for running on the host platform. >> >> There are probably 3 main approaches I can think of for getting the tests to run that have been employed for other platforms: >> >> 1) Transfer the build directory to the target platform and run them there. This would assume you can run command line tools on the target and have access to perl and make etc there. I have no idea whether this is feasible for iOS. >> >> 2) Using qemu. For Android I know it is theoretically possible to run Android binaries on Linux using the qemu emulator. Of course Android is fundamentally Linux "under the hood" which potentially makes this possible. I don't know if something similar could be done for iOS. There are some notes on this approach at the end of the NOTES-ANDROID.md file in the root directory of the OpenSSL source. >> >> 3) Using EXE_SHELL. We have previously been able to cross compile for a windows target and run the tests on Linux using the wine emulator. To do this we set the environment variable "EXE_SHELL" to "wine" before running the tests. This invokes the EXE_SHELL command every time you want to run an application and passes the application name and parameters as arguments to the EXE_SHELL command. Its then the responsibility of the EXE_SHELL command to run the code. >> >> I really have no idea if any of these approaches are viable for iOS. Perhaps Richard may have other ideas. >> >> Matt >> >> >> On 20/05/2021 19:15, Connor Kelley wrote: >>> Hi Matt, >>> I did not see any suite to run for arm64, and got the following error: >>> MacBook-Pro:openssl ckelley$ make test >>> make depend && make _tests >>> make[1]: Entering directory '/Users/ckelley/openssl' >>> make[1]: Leaving directory '/Users/ckelley/openssl' >>> make[1]: Entering directory '/Users/ckelley/openssl' >>> perl ./util/wrap.pl apps/openssl fipsinstall -module providers/fips.dylib -provider_name fips -mac_name HMAC -section_name fips_sect > providers/fipsmodule.cnf >>> util/../util/shlib_wrap.sh: line 113: /Users/ckelley/openssl/apps/openssl: Bad CPU type in executable >>> util/../util/shlib_wrap.sh: line 113: /Users/ckelley/openssl/apps/openssl: Undefined error: 0 >>> Are there arm64 tests that can be run for a cross-compiled target like we are attempting to build? I did not see anything specific or applicable, but will be happy to run whatever if something exists. >>> Outside of that I was considering swapping out the existing FIPS library that we have and see what happens, but that version is much older, so it might not be immediately applicable. >>> Thanks, >>> -Connor >>>> On May 20, 2021, at 2:11 PM, Matt Caswell > wrote: >>>> >>>> Great news! Are you able to run the test suite? >>>> >>>> Matt >>>> >>>> On 20/05/2021 17:48, Connor Kelley wrote: >>>>> Hi Matt, >>>>> After pulling in the fixes for the broken assembly fixes I was able to successfully build without any of the .conf changes so I was able to cancel the PR. >>>>> Using top of tree I was able to successfully build and arm64 target with ./Configure ios64-xcrun enable-fips enable-fips-securitychecks -mios-version-min=11.0 && make >>>>> Thanks, >>>>> -Connor >>>>>> On May 19, 2021, at 10:59 AM, Matt Caswell >> wrote: >>>>>> >>>>>> Thanks Connor...lets continue the conversation in the PR itself. >>>>>> >>>>>> Matt >>>>>> >>>>>> On 19/05/2021 15:43, Connor Kelley wrote: >>>>>>> Hi Matt, >>>>>>> I think the PR is trivial based on what you?re talking about but I?ll be happy to fill out one of those forms if you need it. >>>>>>> The PR for the changes is here: https://github.com/openssl/openssl/pull/15352 > >> >>>>>>> Thanks, >>>>>>> -Connor >>>>>>>> On May 19, 2021, at 3:57 AM, Matt Caswell > >>> wrote: >>>>>>>> >>>>>>>> Hi Connor, >>>>>>>> >>>>>>>> Please submit them as a pull request on our public github site: >>>>>>>> >>>>>>>> https://github.com/openssl/openssl/pulls > >> >>>>>>>> >>>>>>>> If you email the PR number here once created then we will know to give it the attention it deserves. >>>>>>>> >>>>>>>> If the changes are anything other than very trivial then we will also need an ICLA from you individually, as well as a CCLA from Blue Cedar. See: >>>>>>>> >>>>>>>> https://www.openssl.org/policies/cla.html > >>>>>>>> >>>>>>>> Matt >>>>>>>> >>>>>>>> >>>>>>>> On 19/05/2021 01:54, Connor Kelley wrote: >>>>>>>>> Hi Richard, >>>>>>>>> I?ve got a working build that required a couple of updates to the 15-iOS.conf file to get it current. With those changes plus the configure invocation the build seemingly completes successfully. What is the process for submitting a PR to get those changes in and usable? >>>>>>>>> Thanks, >>>>>>>>> -Connor >>>>>>>>> Get Outlook for iOS > >>>>>>>>> ------------------------------------------------------------------------ >>>>>>>>> *From:* Richard Levitte > >>>>>>>>> *Sent:* Tuesday, May 18, 2021 4:05:25 PM >>>>>>>>> *To:* Nivedita Chevvakula > >>>>>>>>> *Cc:* Richard Levitte >; Tim Champagne >; Connor Kelley >; buildbot-admin at openssl.org > >>>>>>>>> *Subject:* Re: [fips-sponsors] Buildbot workers >>>>>>>>> [ Also adding buildbot-admin at openssl.org (I should have done that long ago) ] >>>>>>>>> Yes, some technical details is what I'm trying to get. >>>>>>>>> Right now, that worker is building, sure, but that's a MacOS build, >>>>>>>>> which wasn't what you wanted. >>>>>>>>> So Tim, Connor, if you have something to share, I can hopefully do >>>>>>>>> better progress on our end. >>>>>>>>> Cheers, >>>>>>>>> Richard >>>>>>>>> On Mon, 17 May 2021 15:28:50 +0200, >>>>>>>>> Nivedita Chevvakula wrote: >>>>>>>>>> On this buildbot slave we don't run any our projects, we have set this slave only for buildbot worker. Please let me know if I give ssh creds it will expedite the process. >>>>>>>>>> Also adding Connor and Timmy, hopefully they can clarify on how we build OpenSSL project. >>>>>>>>>> Best, >>>>>>>>>> Niv >>>>>>>>>> ?On 5/13/21, 4:24 AM, "Richard Levitte" > wrote: >>>>>>>>>> What we expect to do is this at a minimum: >>>>>>>>>> perl Configure {args...} >>>>>>>>>> make >>>>>>>>>> In the form that you filled in, there was the option to specify >>>>>>>>>> necessary environment variables (which can affect the configuration >>>>>>>>>> step) and configuration options. I was hoping that would be enough to >>>>>>>>>> get something going. >>>>>>>>>> I do not know what you're talking about regarding a .conf file created >>>>>>>>>> by the Configure step. I understand that you have some sort of super >>>>>>>>>> project that involves building OpenSSL as a component, though, so I >>>>>>>>>> can only assume that somewhere in there, it should be possible to find >>>>>>>>>> how the OpenSSL part is configured, i.e. I assume that there is a run >>>>>>>>>> of Configure hiding in there somewhere, and that it should be possible >>>>>>>>>> to see what arguments are used, as well as any relevant environment >>>>>>>>>> variables. >>>>>>>>>> Does this answer your question? >>>>>>>>>> Cheers, >>>>>>>>>> Richard >>>>>>>>>> On Fri, 07 May 2021 15:12:11 +0200, >>>>>>>>>> Nivedita Chevvakula wrote: >>>>>>>>>> > > We generate a project using cmake that gets built as a dependency of other components in our project. If you are trying to do - build everything using make, which requires a .conf file created with ./Configure step. If so should have one of those somewhere that satisfies what you are looking to produce for iOS, as well as a >>>>>>>>> different one for Android, please provide that we can put it in place on the build bot and just use that? >>>>>>>>>> > > Please advise. >>>>>>>>>> > > Best, >>>>>>>>>> > Niv >>>>>>>>>> > > ?On 5/4/21, 2:56 AM, "Richard Levitte" > wrote: >>>>>>>>>> > > Hi, >>>>>>>>>> > > The worker is connecting fine, so far so good. >>>>>>>>>> > > However, I realised that there are things missing, where we need >>>>>>>>>> > information from you! >>>>>>>>>> > > This worker is meant to build for iOS, is it not? That should require >>>>>>>>>> > extra OpenSSL configuration options. So let me ask you this, when you >>>>>>>>>> > usually build OpenSSL for iOS, exactly how do you usually configure >>>>>>>>>> > OpenSSL? >>>>>>>>>> > > Cheers, >>>>>>>>>> > Richard >>>>>>>>>> > > On Tue, 04 May 2021 03:46:17 +0200, >>>>>>>>>> > Nivedita Chevvakula wrote: >>>>>>>>>> > > > > Richard, >>>>>>>>>> > > > > You can ignore my last mail with error starting buildbot. It is seems to work now after editing >>>>>>>>>> > > syntax for python2.7. Also we have created user ?buildbot? for this mac as recommended. Please let >>>>>>>>>> > > me know if we need to pass those credentials or need to setup anything else for the build bot. >>>>>>>>>> > > > > Best, >>>>>>>>>> > > > > Niv >>>>>>>>>> > > > > From: Nivedita Chevvakula > >>>>>>>>>> > > Date: Monday, May 3, 2021 at 6:44 PM >>>>>>>>>> > > To: Richard Levitte > >>>>>>>>>> > > Subject: Re: [fips-sponsors] Buildbot workers >>>>>>>>>> > > > > Richard, >>>>>>>>>> > > > > Buildbot has now installed with linker, make, c compilers. >>>>>>>>>> > > > > While starting the worker to connect to master after editing tac file as you mentioned getting >>>>>>>>>> > > syntax error . not able to pin point why. Attaching the error log and the tac file here. Could you >>>>>>>>>> > > please help. >>>>>>>>>> > > > > Best, >>>>>>>>>> > > > > Niv >>>>>>>>>> > > > > From: Nivedita Chevvakula > >>>>>>>>>> > > Date: Monday, May 3, 2021 at 9:22 AM >>>>>>>>>> > > To: Richard Levitte > >>>>>>>>>> > > Cc: "levitte at openssl.org " >, Tim Champagne >, Kevin >>>>>>>>>> > > Fox > >>>>>>>>>> > > Subject: Re: [fips-sponsors] Buildbot workers >>>>>>>>>> > > > > Hi Richard, >>>>>>>>>> > > > > Thank you for sending the worker bot setup requirements, I will go thru and will set up the >>>>>>>>>> > > workerbot and will install the rest. Do you have any deadline for this setup please share so that >>>>>>>>>> > > it will help me prioritize. >>>>>>>>>> > > > > So far these tools are installed over the mac : >>>>>>>>>> > > > > 1. Android Studio 4.1.3 >>>>>>>>>> > > 2. Xcode 12.5 >>>>>>>>>> > > 3. clang version 12.0.5 > > 4. Gcc >>>>>>>>>> > > 5. Visual Studio Community 2019 for Mac >>>>>>>>>> > > > > === Visual Studio Community 2019 for Mac === >>>>>>>>>> > > > > Version 8.9.7 (build 8) >>>>>>>>>> > > > > Installation UUID: f1ca8dad-7314-419a-8a39-880ba8a71230 >>>>>>>>>> > > > > GTK+ 2.24.23 (Raleigh theme) >>>>>>>>>> > > > > Xamarin.Mac 6.18.0.23 (d16-6 / 088c73638) >>>>>>>>>> > > > > Package version: 612000125 >>>>>>>>>> > > > > === Mono Framework MDK === >>>>>>>>>> > > > > Runtime: >>>>>>>>>> > > > > Mono 6.12.0.125 (2020-02/8c552e98bd6) (64-bit) >>>>>>>>>> > > > > Package version: 612000125 >>>>>>>>>> > > > > === Roslyn (Language Service) === >>>>>>>>>> > > > > 3.9.0-6.21152.10+c10f884b30737542ddd84ca889a4aad9281ce210 >>>>>>>>>> > > > > === NuGet === >>>>>>>>>> > > > > Version: 5.8.0.6860 >>>>>>>>>> > > > > === .NET Core SDK === >>>>>>>>>> > > > > SDK: /usr/local/share/dotnet/sdk/5.0.202/Sdks >>>>>>>>>> > > > > SDK Versions: >>>>>>>>>> > > > > 5.0.202 >>>>>>>>>> > > > > 3.1.408 >>>>>>>>>> > > > > 2.1.4 >>>>>>>>>> > > > > MSBuild SDKs: /Applications/Visual Studio.app/Contents/Resources/lib/monodevelop/bin/MSBuild/ >>>>>>>>>> > > Current/bin/Sdks >>>>>>>>>> > > > > === .NET Core Runtime === >>>>>>>>>> > > > > Runtime: /usr/local/share/dotnet/dotnet >>>>>>>>>> > > > > Runtime Versions: >>>>>>>>>> > > > > 5.0.5 >>>>>>>>>> > > > > 3.1.14 >>>>>>>>>> > > > > 2.0.5 >>>>>>>>>> > > > > === .NET Core 3.1 SDK === >>>>>>>>>> > > > > SDK: 3.1.408 >>>>>>>>>> > > > > === Xamarin.Profiler === >>>>>>>>>> > > > > Version: 1.6.15.68 >>>>>>>>>> > > > > Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler >>>>>>>>>> > > > > === Updater === >>>>>>>>>> > > > > Version: 11 >>>>>>>>>> > > > > === Apple Developer Tools === >>>>>>>>>> > > > > Xcode 12.5 (18205) >>>>>>>>>> > > > > Build 12E262 >>>>>>>>>> > > > > === Xamarin.Mac === >>>>>>>>>> > > > > Xamarin.Mac not installed. Can't find /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/ >>>>>>>>>> > > Version. >>>>>>>>>> > > > > === Xamarin.iOS === >>>>>>>>>> > > > > Xamarin.iOS not installed. >>>>>>>>>> > > > > Can't find mtouch or the Version file at /Library/Frameworks/Xamarin.iOS.framework/Versions/ >>>>>>>>>> > > Current. >>>>>>>>>> > > > > === Xamarin Designer === >>>>>>>>>> > > > > Version: 16.9.0.324 >>>>>>>>>> > > > > Hash: b1e216c75 >>>>>>>>>> > > > > Branch: remotes/origin/d16-9 >>>>>>>>>> > > > > Build date: 2021-04-16 00:02:50 UTC >>>>>>>>>> > > > > === Xamarin.Android === >>>>>>>>>> > > > > Version: 11.2.2.1 (Visual Studio Community) >>>>>>>>>> > > > > Commit: xamarin-android/d16-9/877f572 >>>>>>>>>> > > > > Android SDK: /Users/ec2-user/Library/Developer/Xamarin/android-sdk-macosx >>>>>>>>>> > > > > Supported Android versions: >>>>>>>>>> > > > > None installed >>>>>>>>>> > > > > SDK Tools Version: 26.1.1 >>>>>>>>>> > > > > SDK Platform Tools Version: 30.0.4 >>>>>>>>>> > > > > SDK Build Tools Version: 30.0.2 >>>>>>>>>> > > > > Build Information: >>>>>>>>>> > > > > Mono: 5e9cb6d >>>>>>>>>> > > > > Java.Interop: xamarin/java.interop/d16-9 at 54f8c24 >>>>>>>>>> > > > > ProGuard: Guardsquare/proguard/v7.0.1 at 912d149 >>>>>>>>>> > > > > SQLite: xamarin/sqlite/3.34.1 at daff8f4 >>>>>>>>>> > > > > Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-9 at d210f11 >>>>>>>>>> > > > > === Microsoft OpenJDK for Mobile === >>>>>>>>>> > > > > Java SDK: /Users/ec2-user/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_1.8.0.25 >>>>>>>>>> > > > > 1.8.0-25 >>>>>>>>>> > > > > Android Designer EPL code available here: >>>>>>>>>> > > > > https://github.com/xamarin/AndroidDesigner.EPL >>>>>>>>> > >>>>>>>>>> > > > > === Android SDK Manager === >>>>>>>>>> > > > > Version: 16.9.0.22 >>>>>>>>>> > > > > Hash: a391de2 >>>>>>>>>> > > > > Branch: remotes/origin/d16-9~2 >>>>>>>>>> > > > > Build date: 2021-03-24 08:30:26 UTC >>>>>>>>>> > > > > === Android Device Manager === >>>>>>>>>> > > > > Version: 16.9.0.17 >>>>>>>>>> > > > > Hash: fc2b3db >>>>>>>>>> > > > > Branch: remotes/origin/dev/jmt/d16-9bump~1 >>>>>>>>>> > > > > Build date: 2021-03-24 08:30:44 UTC >>>>>>>>>> > > > > === Build Information === >>>>>>>>>> > > > > Release ID: 809070008 >>>>>>>>>> > > > > Git revision: 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>>>>>>>>> > > > > Build date: 2021-04-16 07:38:03-04 >>>>>>>>>> > > > > Build branch: release-8.9 >>>>>>>>>> > > > > Xamarin extensions: 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>>>>>>>>> > > > > === Operating System === >>>>>>>>>> > > > > Mac OS X 10.16.0 >>>>>>>>>> > > > > Darwin 20.3.0 Darwin Kernel Version 20.3.0 >>>>>>>>>> > > > > Thu Jan 21 00:07:06 PST 2021 >>>>>>>>>> > > > > root:xnu-7195.81.3~1/RELEASE_X86_64 x86_64 >>>>>>>>>> > > > > Best, >>>>>>>>>> > > > > Niv >>>>>>>>>> > > > > From: Richard Levitte > >>>>>>>>>> > > Date: Monday, May 3, 2021 at 4:54 AM >>>>>>>>>> > > To: Nivedita Chevvakula > >>>>>>>>>> > > Cc: levitte at openssl.org >, Tim Champagne >, Kevin Fox >>>>>>>>>> > > > >>>>>>>>>> > > Subject: Re: [fips-sponsors] Buildbot workers >>>>>>>>>> > > > > Hi, >>>>>>>>>> > > > > Thank you for offering workers to us! >>>>>>>>>> > > > > To be able to set up your worker, you must use version 2.6.0 or >>>>>>>>>> > > higher. Older version do not support TLS-protected connections. >>>>>>>>>> > > > > Please see these instructions for installing the buildbot worker >>>>>>>>>> > > software: >>>>>>>>>> > > > > http://docs.buildbot.net/latest/manual/installation/worker.html >>>>>>>>> > >>>>>>>>>> > > > > When buildbot has been installed on the platform where the buildbot >>>>>>>>>> > > worker is to be run, this is how a worker is created: >>>>>>>>>> > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ >>>>>>>>>> > > buildbot.openssl.org:9989 'bluecedar-01' 'Rak;osErfabOn5' >>>>>>>>>> > > > > where BASEDIR is determined by you. See further down for a few notes >>>>>>>>>> > > on TLS. >>>>>>>>>> > > > > To run a buildbot worker, you do this: >>>>>>>>>> > > > > $ buildbot-worker start BASEDIR >>>>>>>>>> > > > > Apart from the software needed to run a buildbot worker, and the >>>>>>>>>> > > utilities that are the normal part of the operating system, you also >>>>>>>>>> > > need to ensure that the following components are available: >>>>>>>>>> > > > > - toolchains, i.e. C compiler, linker, make. If you have specified >>>>>>>>>> > > toolchains in the worker request form, you need to ensure that all >>>>>>>>>> > > of them are installed. >>>>>>>>>> > > > > - git >>>>>>>>>> > > > > Regarding TLS, it may be that the buildbot worker platform doesn't >>>>>>>>>> > > have the appropriate certification verification roots set up. In that >>>>>>>>>> > > case, you may need to apply the attached buildbot.tac patch, and store >>>>>>>>>> > > the attached PEM files in a directory of your choice. Finish up by >>>>>>>>>> > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with >>>>>>>>>> > > the path of directory where you stored the PEM files. >>>>>>>>>> > > > > > -- > Richard Levitte levitte at openssl.org >>>>>>>>>> > OpenSSL Project http://www.openssl.org/~levitte/ > >>>>>>>>>> -- Richard Levitte levitte at openssl.org >>>>>>>>>> OpenSSL Project http://www.openssl.org/~levitte/ > >>>>>>>>> -- >>>>>>>>> Richard Levitte levitte at openssl.org >>>>>>>>> OpenSSL Project http://www.openssl.org/~levitte/ > >>>>>>>>> _______________________________________________ >>>>>>>>> buildbot-admin mailing list >>>>>>>>> buildbot-admin at openssl.org >>>>>>>>> https://mta.openssl.org/mailman/listinfo/buildbot-admin > From ckelley at bluecedar.com Wed May 26 14:00:50 2021 From: ckelley at bluecedar.com (Connor Kelley) Date: Wed, 26 May 2021 10:00:50 -0400 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: References: <87k0p89dfr.wl-levitte@openssl.org> <87mttbm1gf.wl-levitte@openssl.org> <87o8dfqbwh.wl-levitte@openssl.org> <87h7iz95a2.wl-levitte@openssl.org> <7CC6990D-7F93-4E61-BE46-116A635AC1FA@bluecedar.com> <2a669cf9-d629-da3c-e386-ac4da9c5677a@openssl.org> <84BD88CC-9ACB-4C86-AA77-762DC8F996F7@bluecedar.com> <7831e130-1e9b-79f3-3248-2df93d71e342@openssl.org> <15D64FB6-775C-4907-A6BF-17FC1B4CF8E6@bluecedar.com> Message-ID: <8B921C1A-BC7A-4ED3-9A14-84C3700686C0@bluecedar.com> Hi Matt, Thanks for clarifying that that approach is not a viable option. How did you previously validate the iOS side? In order to validate the arm64 slice the binary would need to be run in something on a physical device, as otherwise you would just be testing the x86_64 slice on a simulator, which is not the same thing. Did you have some sort of a host program? I?m not positive what capabilities the hosted mac has, but it may be possible to attach a device to it, that would be something that would need to be investigated. What tests actually get run with ?make test?? Thanks, -Connor > On May 26, 2021, at 6:05 AM, Matt Caswell wrote: > > Unfortunately that's not going to work for us. It's a requirement for us that "make test" works - and without using Blue Cedar proprietary code. :-( > > Matt > > On 25/05/2021 16:12, Connor Kelley wrote: >> Hi Matt, >> That?s what I was thinking as well. None of those three options are applicable on iOS, so it sounds like in order to test this in any meaningful way on iOS I?m going to need to link against that library with our product, replacing the current version of our FIPS library. I?m open to other options though, as I?m sure there?s some defined test harness for the final FIPS validation, unless I?m mistaken. >> Thanks, >> -Connr >>> On May 21, 2021, at 3:25 AM, Matt Caswell wrote: >>> >>> Hi Connor >>> >>> I'm not familiar with iOS so I don't know the specific issues and challenges that you might have running the test suite on that platform. You won't be able to just run "make test" since you are cross-compiling so the generated executables aren't suitable for running on the host platform. >>> >>> There are probably 3 main approaches I can think of for getting the tests to run that have been employed for other platforms: >>> >>> 1) Transfer the build directory to the target platform and run them there. This would assume you can run command line tools on the target and have access to perl and make etc there. I have no idea whether this is feasible for iOS. >>> >>> 2) Using qemu. For Android I know it is theoretically possible to run Android binaries on Linux using the qemu emulator. Of course Android is fundamentally Linux "under the hood" which potentially makes this possible. I don't know if something similar could be done for iOS. There are some notes on this approach at the end of the NOTES-ANDROID.md file in the root directory of the OpenSSL source. >>> >>> 3) Using EXE_SHELL. We have previously been able to cross compile for a windows target and run the tests on Linux using the wine emulator. To do this we set the environment variable "EXE_SHELL" to "wine" before running the tests. This invokes the EXE_SHELL command every time you want to run an application and passes the application name and parameters as arguments to the EXE_SHELL command. Its then the responsibility of the EXE_SHELL command to run the code. >>> >>> I really have no idea if any of these approaches are viable for iOS. Perhaps Richard may have other ideas. >>> >>> Matt >>> >>> >>> On 20/05/2021 19:15, Connor Kelley wrote: >>>> Hi Matt, >>>> I did not see any suite to run for arm64, and got the following error: >>>> MacBook-Pro:openssl ckelley$ make test >>>> make depend && make _tests >>>> make[1]: Entering directory '/Users/ckelley/openssl' >>>> make[1]: Leaving directory '/Users/ckelley/openssl' >>>> make[1]: Entering directory '/Users/ckelley/openssl' >>>> perl ./util/wrap.pl apps/openssl fipsinstall -module providers/fips.dylib -provider_name fips -mac_name HMAC -section_name fips_sect > providers/fipsmodule.cnf >>>> util/../util/shlib_wrap.sh: line 113: /Users/ckelley/openssl/apps/openssl: Bad CPU type in executable >>>> util/../util/shlib_wrap.sh: line 113: /Users/ckelley/openssl/apps/openssl: Undefined error: 0 >>>> Are there arm64 tests that can be run for a cross-compiled target like we are attempting to build? I did not see anything specific or applicable, but will be happy to run whatever if something exists. >>>> Outside of that I was considering swapping out the existing FIPS library that we have and see what happens, but that version is much older, so it might not be immediately applicable. >>>> Thanks, >>>> -Connor >>>>> On May 20, 2021, at 2:11 PM, Matt Caswell > wrote: >>>>> >>>>> Great news! Are you able to run the test suite? >>>>> >>>>> Matt >>>>> >>>>> On 20/05/2021 17:48, Connor Kelley wrote: >>>>>> Hi Matt, >>>>>> After pulling in the fixes for the broken assembly fixes I was able to successfully build without any of the .conf changes so I was able to cancel the PR. >>>>>> Using top of tree I was able to successfully build and arm64 target with ./Configure ios64-xcrun enable-fips enable-fips-securitychecks -mios-version-min=11.0 && make >>>>>> Thanks, >>>>>> -Connor >>>>>>> On May 19, 2021, at 10:59 AM, Matt Caswell >> wrote: >>>>>>> >>>>>>> Thanks Connor...lets continue the conversation in the PR itself. >>>>>>> >>>>>>> Matt >>>>>>> >>>>>>> On 19/05/2021 15:43, Connor Kelley wrote: >>>>>>>> Hi Matt, >>>>>>>> I think the PR is trivial based on what you?re talking about but I?ll be happy to fill out one of those forms if you need it. >>>>>>>> The PR for the changes is here: https://github.com/openssl/openssl/pull/15352 > >> >>>>>>>> Thanks, >>>>>>>> -Connor >>>>>>>>> On May 19, 2021, at 3:57 AM, Matt Caswell > >>> wrote: >>>>>>>>> >>>>>>>>> Hi Connor, >>>>>>>>> >>>>>>>>> Please submit them as a pull request on our public github site: >>>>>>>>> >>>>>>>>> https://github.com/openssl/openssl/pulls > >> >>>>>>>>> >>>>>>>>> If you email the PR number here once created then we will know to give it the attention it deserves. >>>>>>>>> >>>>>>>>> If the changes are anything other than very trivial then we will also need an ICLA from you individually, as well as a CCLA from Blue Cedar. See: >>>>>>>>> >>>>>>>>> https://www.openssl.org/policies/cla.html > >>>>>>>>> >>>>>>>>> Matt >>>>>>>>> >>>>>>>>> >>>>>>>>> On 19/05/2021 01:54, Connor Kelley wrote: >>>>>>>>>> Hi Richard, >>>>>>>>>> I?ve got a working build that required a couple of updates to the 15-iOS.conf file to get it current. With those changes plus the configure invocation the build seemingly completes successfully. What is the process for submitting a PR to get those changes in and usable? >>>>>>>>>> Thanks, >>>>>>>>>> -Connor >>>>>>>>>> Get Outlook for iOS > >>>>>>>>>> ------------------------------------------------------------------------ >>>>>>>>>> *From:* Richard Levitte > >>>>>>>>>> *Sent:* Tuesday, May 18, 2021 4:05:25 PM >>>>>>>>>> *To:* Nivedita Chevvakula > >>>>>>>>>> *Cc:* Richard Levitte >; Tim Champagne >; Connor Kelley >; buildbot-admin at openssl.org > >>>>>>>>>> *Subject:* Re: [fips-sponsors] Buildbot workers >>>>>>>>>> [ Also adding buildbot-admin at openssl.org (I should have done that long ago) ] >>>>>>>>>> Yes, some technical details is what I'm trying to get. >>>>>>>>>> Right now, that worker is building, sure, but that's a MacOS build, >>>>>>>>>> which wasn't what you wanted. >>>>>>>>>> So Tim, Connor, if you have something to share, I can hopefully do >>>>>>>>>> better progress on our end. >>>>>>>>>> Cheers, >>>>>>>>>> Richard >>>>>>>>>> On Mon, 17 May 2021 15:28:50 +0200, >>>>>>>>>> Nivedita Chevvakula wrote: >>>>>>>>>>> On this buildbot slave we don't run any our projects, we have set this slave only for buildbot worker. Please let me know if I give ssh creds it will expedite the process. >>>>>>>>>>> Also adding Connor and Timmy, hopefully they can clarify on how we build OpenSSL project. >>>>>>>>>>> Best, >>>>>>>>>>> Niv >>>>>>>>>>> ?On 5/13/21, 4:24 AM, "Richard Levitte" > wrote: >>>>>>>>>>> What we expect to do is this at a minimum: >>>>>>>>>>> perl Configure {args...} >>>>>>>>>>> make >>>>>>>>>>> In the form that you filled in, there was the option to specify >>>>>>>>>>> necessary environment variables (which can affect the configuration >>>>>>>>>>> step) and configuration options. I was hoping that would be enough to >>>>>>>>>>> get something going. >>>>>>>>>>> I do not know what you're talking about regarding a .conf file created >>>>>>>>>>> by the Configure step. I understand that you have some sort of super >>>>>>>>>>> project that involves building OpenSSL as a component, though, so I >>>>>>>>>>> can only assume that somewhere in there, it should be possible to find >>>>>>>>>>> how the OpenSSL part is configured, i.e. I assume that there is a run >>>>>>>>>>> of Configure hiding in there somewhere, and that it should be possible >>>>>>>>>>> to see what arguments are used, as well as any relevant environment >>>>>>>>>>> variables. >>>>>>>>>>> Does this answer your question? >>>>>>>>>>> Cheers, >>>>>>>>>>> Richard >>>>>>>>>>> On Fri, 07 May 2021 15:12:11 +0200, >>>>>>>>>>> Nivedita Chevvakula wrote: >>>>>>>>>>> > > We generate a project using cmake that gets built as a dependency of other components in our project. If you are trying to do - build everything using make, which requires a .conf file created with ./Configure step. If so should have one of those somewhere that satisfies what you are looking to produce for iOS, as well as a >>>>>>>>>> different one for Android, please provide that we can put it in place on the build bot and just use that? >>>>>>>>>>> > > Please advise. >>>>>>>>>>> > > Best, >>>>>>>>>>> > Niv >>>>>>>>>>> > > ?On 5/4/21, 2:56 AM, "Richard Levitte" > wrote: >>>>>>>>>>> > > Hi, >>>>>>>>>>> > > The worker is connecting fine, so far so good. >>>>>>>>>>> > > However, I realised that there are things missing, where we need >>>>>>>>>>> > information from you! >>>>>>>>>>> > > This worker is meant to build for iOS, is it not? That should require >>>>>>>>>>> > extra OpenSSL configuration options. So let me ask you this, when you >>>>>>>>>>> > usually build OpenSSL for iOS, exactly how do you usually configure >>>>>>>>>>> > OpenSSL? >>>>>>>>>>> > > Cheers, >>>>>>>>>>> > Richard >>>>>>>>>>> > > On Tue, 04 May 2021 03:46:17 +0200, >>>>>>>>>>> > Nivedita Chevvakula wrote: >>>>>>>>>>> > > > > Richard, >>>>>>>>>>> > > > > You can ignore my last mail with error starting buildbot. It is seems to work now after editing >>>>>>>>>>> > > syntax for python2.7. Also we have created user ?buildbot? for this mac as recommended. Please let >>>>>>>>>>> > > me know if we need to pass those credentials or need to setup anything else for the build bot. >>>>>>>>>>> > > > > Best, >>>>>>>>>>> > > > > Niv >>>>>>>>>>> > > > > From: Nivedita Chevvakula > >>>>>>>>>>> > > Date: Monday, May 3, 2021 at 6:44 PM >>>>>>>>>>> > > To: Richard Levitte > >>>>>>>>>>> > > Subject: Re: [fips-sponsors] Buildbot workers >>>>>>>>>>> > > > > Richard, >>>>>>>>>>> > > > > Buildbot has now installed with linker, make, c compilers. >>>>>>>>>>> > > > > While starting the worker to connect to master after editing tac file as you mentioned getting >>>>>>>>>>> > > syntax error . not able to pin point why. Attaching the error log and the tac file here. Could you >>>>>>>>>>> > > please help. >>>>>>>>>>> > > > > Best, >>>>>>>>>>> > > > > Niv >>>>>>>>>>> > > > > From: Nivedita Chevvakula > >>>>>>>>>>> > > Date: Monday, May 3, 2021 at 9:22 AM >>>>>>>>>>> > > To: Richard Levitte > >>>>>>>>>>> > > Cc: "levitte at openssl.org " >, Tim Champagne >, Kevin >>>>>>>>>>> > > Fox > >>>>>>>>>>> > > Subject: Re: [fips-sponsors] Buildbot workers >>>>>>>>>>> > > > > Hi Richard, >>>>>>>>>>> > > > > Thank you for sending the worker bot setup requirements, I will go thru and will set up the >>>>>>>>>>> > > workerbot and will install the rest. Do you have any deadline for this setup please share so that >>>>>>>>>>> > > it will help me prioritize. >>>>>>>>>>> > > > > So far these tools are installed over the mac : >>>>>>>>>>> > > > > 1. Android Studio 4.1.3 >>>>>>>>>>> > > 2. Xcode 12.5 >>>>>>>>>>> > > 3. clang version 12.0.5 > > 4. Gcc >>>>>>>>>>> > > 5. Visual Studio Community 2019 for Mac >>>>>>>>>>> > > > > === Visual Studio Community 2019 for Mac === >>>>>>>>>>> > > > > Version 8.9.7 (build 8) >>>>>>>>>>> > > > > Installation UUID: f1ca8dad-7314-419a-8a39-880ba8a71230 >>>>>>>>>>> > > > > GTK+ 2.24.23 (Raleigh theme) >>>>>>>>>>> > > > > Xamarin.Mac 6.18.0.23 (d16-6 / 088c73638) >>>>>>>>>>> > > > > Package version: 612000125 >>>>>>>>>>> > > > > === Mono Framework MDK === >>>>>>>>>>> > > > > Runtime: >>>>>>>>>>> > > > > Mono 6.12.0.125 (2020-02/8c552e98bd6) (64-bit) >>>>>>>>>>> > > > > Package version: 612000125 >>>>>>>>>>> > > > > === Roslyn (Language Service) === >>>>>>>>>>> > > > > 3.9.0-6.21152.10+c10f884b30737542ddd84ca889a4aad9281ce210 >>>>>>>>>>> > > > > === NuGet === >>>>>>>>>>> > > > > Version: 5.8.0.6860 >>>>>>>>>>> > > > > === .NET Core SDK === >>>>>>>>>>> > > > > SDK: /usr/local/share/dotnet/sdk/5.0.202/Sdks >>>>>>>>>>> > > > > SDK Versions: >>>>>>>>>>> > > > > 5.0.202 >>>>>>>>>>> > > > > 3.1.408 >>>>>>>>>>> > > > > 2.1.4 >>>>>>>>>>> > > > > MSBuild SDKs: /Applications/Visual Studio.app/Contents/Resources/lib/monodevelop/bin/MSBuild/ >>>>>>>>>>> > > Current/bin/Sdks >>>>>>>>>>> > > > > === .NET Core Runtime === >>>>>>>>>>> > > > > Runtime: /usr/local/share/dotnet/dotnet >>>>>>>>>>> > > > > Runtime Versions: >>>>>>>>>>> > > > > 5.0.5 >>>>>>>>>>> > > > > 3.1.14 >>>>>>>>>>> > > > > 2.0.5 >>>>>>>>>>> > > > > === .NET Core 3.1 SDK === >>>>>>>>>>> > > > > SDK: 3.1.408 >>>>>>>>>>> > > > > === Xamarin.Profiler === >>>>>>>>>>> > > > > Version: 1.6.15.68 >>>>>>>>>>> > > > > Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler >>>>>>>>>>> > > > > === Updater === >>>>>>>>>>> > > > > Version: 11 >>>>>>>>>>> > > > > === Apple Developer Tools === >>>>>>>>>>> > > > > Xcode 12.5 (18205) >>>>>>>>>>> > > > > Build 12E262 >>>>>>>>>>> > > > > === Xamarin.Mac === >>>>>>>>>>> > > > > Xamarin.Mac not installed. Can't find /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/ >>>>>>>>>>> > > Version. >>>>>>>>>>> > > > > === Xamarin.iOS === >>>>>>>>>>> > > > > Xamarin.iOS not installed. >>>>>>>>>>> > > > > Can't find mtouch or the Version file at /Library/Frameworks/Xamarin.iOS.framework/Versions/ >>>>>>>>>>> > > Current. >>>>>>>>>>> > > > > === Xamarin Designer === >>>>>>>>>>> > > > > Version: 16.9.0.324 >>>>>>>>>>> > > > > Hash: b1e216c75 >>>>>>>>>>> > > > > Branch: remotes/origin/d16-9 >>>>>>>>>>> > > > > Build date: 2021-04-16 00:02:50 UTC >>>>>>>>>>> > > > > === Xamarin.Android === >>>>>>>>>>> > > > > Version: 11.2.2.1 (Visual Studio Community) >>>>>>>>>>> > > > > Commit: xamarin-android/d16-9/877f572 >>>>>>>>>>> > > > > Android SDK: /Users/ec2-user/Library/Developer/Xamarin/android-sdk-macosx >>>>>>>>>>> > > > > Supported Android versions: >>>>>>>>>>> > > > > None installed >>>>>>>>>>> > > > > SDK Tools Version: 26.1.1 >>>>>>>>>>> > > > > SDK Platform Tools Version: 30.0.4 >>>>>>>>>>> > > > > SDK Build Tools Version: 30.0.2 >>>>>>>>>>> > > > > Build Information: >>>>>>>>>>> > > > > Mono: 5e9cb6d >>>>>>>>>>> > > > > Java.Interop: xamarin/java.interop/d16-9 at 54f8c24 >>>>>>>>>>> > > > > ProGuard: Guardsquare/proguard/v7.0.1 at 912d149 >>>>>>>>>>> > > > > SQLite: xamarin/sqlite/3.34.1 at daff8f4 >>>>>>>>>>> > > > > Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-9 at d210f11 >>>>>>>>>>> > > > > === Microsoft OpenJDK for Mobile === >>>>>>>>>>> > > > > Java SDK: /Users/ec2-user/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_1.8.0.25 >>>>>>>>>>> > > > > 1.8.0-25 >>>>>>>>>>> > > > > Android Designer EPL code available here: >>>>>>>>>>> > > > > https://github.com/xamarin/AndroidDesigner.EPL >>>>>>>>>> > >>>>>>>>>>> > > > > === Android SDK Manager === >>>>>>>>>>> > > > > Version: 16.9.0.22 >>>>>>>>>>> > > > > Hash: a391de2 >>>>>>>>>>> > > > > Branch: remotes/origin/d16-9~2 >>>>>>>>>>> > > > > Build date: 2021-03-24 08:30:26 UTC >>>>>>>>>>> > > > > === Android Device Manager === >>>>>>>>>>> > > > > Version: 16.9.0.17 >>>>>>>>>>> > > > > Hash: fc2b3db >>>>>>>>>>> > > > > Branch: remotes/origin/dev/jmt/d16-9bump~1 >>>>>>>>>>> > > > > Build date: 2021-03-24 08:30:44 UTC >>>>>>>>>>> > > > > === Build Information === >>>>>>>>>>> > > > > Release ID: 809070008 >>>>>>>>>>> > > > > Git revision: 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>>>>>>>>>> > > > > Build date: 2021-04-16 07:38:03-04 >>>>>>>>>>> > > > > Build branch: release-8.9 >>>>>>>>>>> > > > > Xamarin extensions: 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>>>>>>>>>> > > > > === Operating System === >>>>>>>>>>> > > > > Mac OS X 10.16.0 >>>>>>>>>>> > > > > Darwin 20.3.0 Darwin Kernel Version 20.3.0 >>>>>>>>>>> > > > > Thu Jan 21 00:07:06 PST 2021 >>>>>>>>>>> > > > > root:xnu-7195.81.3~1/RELEASE_X86_64 x86_64 >>>>>>>>>>> > > > > Best, >>>>>>>>>>> > > > > Niv >>>>>>>>>>> > > > > From: Richard Levitte > >>>>>>>>>>> > > Date: Monday, May 3, 2021 at 4:54 AM >>>>>>>>>>> > > To: Nivedita Chevvakula > >>>>>>>>>>> > > Cc: levitte at openssl.org >, Tim Champagne >, Kevin Fox >>>>>>>>>>> > > > >>>>>>>>>>> > > Subject: Re: [fips-sponsors] Buildbot workers >>>>>>>>>>> > > > > Hi, >>>>>>>>>>> > > > > Thank you for offering workers to us! >>>>>>>>>>> > > > > To be able to set up your worker, you must use version 2.6.0 or >>>>>>>>>>> > > higher. Older version do not support TLS-protected connections. >>>>>>>>>>> > > > > Please see these instructions for installing the buildbot worker >>>>>>>>>>> > > software: >>>>>>>>>>> > > > > http://docs.buildbot.net/latest/manual/installation/worker.html >>>>>>>>>> > >>>>>>>>>>> > > > > When buildbot has been installed on the platform where the buildbot >>>>>>>>>>> > > worker is to be run, this is how a worker is created: >>>>>>>>>>> > > > > $ buildbot-worker create-worker --use-tls BASEDIR \ >>>>>>>>>>> > > buildbot.openssl.org:9989 'bluecedar-01' 'Rak;osErfabOn5' >>>>>>>>>>> > > > > where BASEDIR is determined by you. See further down for a few notes >>>>>>>>>>> > > on TLS. >>>>>>>>>>> > > > > To run a buildbot worker, you do this: >>>>>>>>>>> > > > > $ buildbot-worker start BASEDIR >>>>>>>>>>> > > > > Apart from the software needed to run a buildbot worker, and the >>>>>>>>>>> > > utilities that are the normal part of the operating system, you also >>>>>>>>>>> > > need to ensure that the following components are available: >>>>>>>>>>> > > > > - toolchains, i.e. C compiler, linker, make. If you have specified >>>>>>>>>>> > > toolchains in the worker request form, you need to ensure that all >>>>>>>>>>> > > of them are installed. >>>>>>>>>>> > > > > - git >>>>>>>>>>> > > > > Regarding TLS, it may be that the buildbot worker platform doesn't >>>>>>>>>>> > > have the appropriate certification verification roots set up. In that >>>>>>>>>>> > > case, you may need to apply the attached buildbot.tac patch, and store >>>>>>>>>>> > > the attached PEM files in a directory of your choice. Finish up by >>>>>>>>>>> > > find the string '/PATH/TO/ssl-roots-dir' and replace its contents with >>>>>>>>>>> > > the path of directory where you stored the PEM files. >>>>>>>>>>> > > > > > -- > Richard Levitte levitte at openssl.org >>>>>>>>>>> > OpenSSL Project http://www.openssl.org/~levitte/ > >>>>>>>>>>> -- Richard Levitte levitte at openssl.org >>>>>>>>>>> OpenSSL Project http://www.openssl.org/~levitte/ > >>>>>>>>>> -- >>>>>>>>>> Richard Levitte levitte at openssl.org >>>>>>>>>> OpenSSL Project http://www.openssl.org/~levitte/ > >>>>>>>>>> _______________________________________________ >>>>>>>>>> buildbot-admin mailing list >>>>>>>>>> buildbot-admin at openssl.org >>>>>>>>>> https://mta.openssl.org/mailman/listinfo/buildbot-admin From matt at openssl.org Wed May 26 14:15:31 2021 From: matt at openssl.org (Matt Caswell) Date: Wed, 26 May 2021 15:15:31 +0100 Subject: [buildbot-admin] [fips-sponsors] Buildbot workers In-Reply-To: <8B921C1A-BC7A-4ED3-9A14-84C3700686C0@bluecedar.com> References: <87k0p89dfr.wl-levitte@openssl.org> <87mttbm1gf.wl-levitte@openssl.org> <87o8dfqbwh.wl-levitte@openssl.org> <87h7iz95a2.wl-levitte@openssl.org> <7CC6990D-7F93-4E61-BE46-116A635AC1FA@bluecedar.com> <2a669cf9-d629-da3c-e386-ac4da9c5677a@openssl.org> <84BD88CC-9ACB-4C86-AA77-762DC8F996F7@bluecedar.com> <7831e130-1e9b-79f3-3248-2df93d71e342@openssl.org> <15D64FB6-775C-4907-A6BF-17FC1B4CF8E6@bluecedar.com> <8B921C1A-BC7A-4ED3-9A14-84C3700686C0@bluecedar.com> Message-ID: On 26/05/2021 15:00, Connor Kelley wrote: > Hi Matt, Thanks for clarifying that that approach is not a viable > option. How did you previously validate the iOS side? Actually I don't know. Many of the people who did the old validation are no longer with us, and it was (mostly) before my time. At least I was not involved in it at all. I'll ask around to see if anyone knows. > In order to validate the arm64 slice the binary would need to be run > in something on a physical device, as otherwise you would just be > testing the x86_64 slice on a simulator, which is not the same thing. > Did you have some sort of a host program? I?m not positive what > capabilities the hosted mac has, but it may be possible to attach a > device to it, that would be something that would need to be > investigated. What tests actually get run with ?make test?? "make test" runs a perl "runner" that executes a whole suite of tests - most of which are command line executables. See the source code in the "test" directory of the 3.0 source code. There are also a small number of tests that are written in perl - the so-called TLSProxy tests. They start an OpenSSL "s_server" application, and an OpenSSL "s_client" application and intercept TCP communications between the server and client - making modifications etc. I don't know if perl exists in the iOS world. If not it might be possible to run the perl on some external system, and use the "EXE_SHELL" approach I previously described to invoke some form of shim which would actually be responsible for running the test executable on the target system and reporting back the results. Not sure how we would do the TLSProxy tests though. Matt > > Thanks, -Connor > >> On May 26, 2021, at 6:05 AM, Matt Caswell >> wrote: >> >> Unfortunately that's not going to work for us. It's a requirement >> for us that "make test" works - and without using Blue Cedar >> proprietary code. :-( >> >> Matt >> >> On 25/05/2021 16:12, Connor Kelley wrote: >>> Hi Matt, That?s what I was thinking as well. None of those three >>> options are applicable on iOS, so it sounds like in order to test >>> this in any meaningful way on iOS I?m going to need to link >>> against that library with our product, replacing the current >>> version of our FIPS library. I?m open to other options though, as >>> I?m sure there?s some defined test harness for the final FIPS >>> validation, unless I?m mistaken. Thanks, -Connr >>>> On May 21, 2021, at 3:25 AM, Matt Caswell >>>> wrote: >>>> >>>> Hi Connor >>>> >>>> I'm not familiar with iOS so I don't know the specific issues >>>> and challenges that you might have running the test suite on >>>> that platform. You won't be able to just run "make test" since >>>> you are cross-compiling so the generated executables aren't >>>> suitable for running on the host platform. >>>> >>>> There are probably 3 main approaches I can think of for getting >>>> the tests to run that have been employed for other platforms: >>>> >>>> 1) Transfer the build directory to the target platform and run >>>> them there. This would assume you can run command line tools on >>>> the target and have access to perl and make etc there. I have >>>> no idea whether this is feasible for iOS. >>>> >>>> 2) Using qemu. For Android I know it is theoretically possible >>>> to run Android binaries on Linux using the qemu emulator. Of >>>> course Android is fundamentally Linux "under the hood" which >>>> potentially makes this possible. I don't know if something >>>> similar could be done for iOS. There are some notes on this >>>> approach at the end of the NOTES-ANDROID.md file in the root >>>> directory of the OpenSSL source. >>>> >>>> 3) Using EXE_SHELL. We have previously been able to cross >>>> compile for a windows target and run the tests on Linux using >>>> the wine emulator. To do this we set the environment variable >>>> "EXE_SHELL" to "wine" before running the tests. This invokes >>>> the EXE_SHELL command every time you want to run an application >>>> and passes the application name and parameters as arguments to >>>> the EXE_SHELL command. Its then the responsibility of the >>>> EXE_SHELL command to run the code. >>>> >>>> I really have no idea if any of these approaches are viable for >>>> iOS. Perhaps Richard may have other ideas. >>>> >>>> Matt >>>> >>>> >>>> On 20/05/2021 19:15, Connor Kelley wrote: >>>>> Hi Matt, I did not see any suite to run for arm64, and got >>>>> the following error: MacBook-Pro:openssl ckelley$ make test >>>>> make depend && make _tests make[1]: Entering directory >>>>> '/Users/ckelley/openssl' make[1]: Leaving directory >>>>> '/Users/ckelley/openssl' make[1]: Entering directory >>>>> '/Users/ckelley/openssl' perl ./util/wrap.pl apps/openssl >>>>> fipsinstall -module providers/fips.dylib -provider_name fips >>>>> -mac_name HMAC -section_name fips_sect > >>>>> providers/fipsmodule.cnf util/../util/shlib_wrap.sh: line >>>>> 113: /Users/ckelley/openssl/apps/openssl: Bad CPU type in >>>>> executable util/../util/shlib_wrap.sh: line 113: >>>>> /Users/ckelley/openssl/apps/openssl: Undefined error: 0 Are >>>>> there arm64 tests that can be run for a cross-compiled target >>>>> like we are attempting to build? I did not see anything >>>>> specific or applicable, but will be happy to run whatever if >>>>> something exists. Outside of that I was considering swapping >>>>> out the existing FIPS library that we have and see what >>>>> happens, but that version is much older, so it might not be >>>>> immediately applicable. Thanks, -Connor >>>>>> On May 20, 2021, at 2:11 PM, Matt Caswell >>>>> > wrote: >>>>>> >>>>>> Great news! Are you able to run the test suite? >>>>>> >>>>>> Matt >>>>>> >>>>>> On 20/05/2021 17:48, Connor Kelley wrote: >>>>>>> Hi Matt, After pulling in the fixes for the broken >>>>>>> assembly fixes I was able to successfully build without >>>>>>> any of the .conf changes so I was able to cancel the PR. >>>>>>> Using top of tree I was able to successfully build and >>>>>>> arm64 target with ./Configure ios64-xcrun enable-fips >>>>>>> enable-fips-securitychecks -mios-version-min=11.0 && >>>>>>> make Thanks, -Connor >>>>>>>> On May 19, 2021, at 10:59 AM, Matt Caswell >>>>>>>> >>>>>>>> >> >>>>>>>> wrote: >>>>>>>> >>>>>>>> Thanks Connor...lets continue the conversation in the >>>>>>>> PR itself. >>>>>>>> >>>>>>>> Matt >>>>>>>> >>>>>>>> On 19/05/2021 15:43, Connor Kelley wrote: >>>>>>>>> Hi Matt, I think the PR is trivial based on what >>>>>>>>> you?re talking about but I?ll be happy to fill out >>>>>>>>> one of those forms if you need it. The PR for the >>>>>>>>> changes is here: >>>>>>>>> https://github.com/openssl/openssl/pull/15352 >>>>>>>>> >>>>>>>>> >>>>>>>> > >>>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>> >> >>>>>>>>> Thanks, -Connor >>>>>>>>>> On May 19, 2021, at 3:57 AM, Matt Caswell >>>>>>>>>> >>>>>>>>>> > >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>> wrote: >>>>>>>>>> >>>>>>>>>> Hi Connor, >>>>>>>>>> >>>>>>>>>> Please submit them as a pull request on our public >>>>>>>>>> github site: >>>>>>>>>> >>>>>>>>>> https://github.com/openssl/openssl/pulls >>>>>>>>>> >>>>>>>>>> >>>>>>>>> > >>>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>> >> >>>>>>>>>> >>>>>>>>>> If you email the PR number here once created then >>>>>>>>>> we will know to give it the attention it deserves. >>>>>>>>>> >>>>>>>>>> If the changes are anything other than very trivial >>>>>>>>>> then we will also need an ICLA from you >>>>>>>>>> individually, as well as a CCLA from Blue Cedar. >>>>>>>>>> See: >>>>>>>>>> >>>>>>>>>> https://www.openssl.org/policies/cla.html >>>>>>>>>> >>>>>>>>>> >>>>>>>>> > >>>>>>>>>> >>>>>>>>>> Matt >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On 19/05/2021 01:54, Connor Kelley wrote: >>>>>>>>>>> Hi Richard, I?ve got a working build that >>>>>>>>>>> required a couple of updates to the 15-iOS.conf >>>>>>>>>>> file to get it current. With those changes plus >>>>>>>>>>> the configure invocation the build seemingly >>>>>>>>>>> completes successfully. What is the process for >>>>>>>>>>> submitting a PR to get those changes in and >>>>>>>>>>> usable? Thanks, -Connor Get Outlook for iOS >>>>>>>>>>> > >>>>>>>>>>> ------------------------------------------------------------------------ >>>>>>>>>>> >>>>>>>>>>> *From:* Richard Levitte > >>>>>>>>>>> *Sent:* Tuesday, May 18, 2021 4:05:25 PM *To:* >>>>>>>>>>> Nivedita Chevvakula >>>>>>>>>> > *Cc:* Richard >>>>>>>>>>> Levitte >>>>>>>>>> >; Tim Champagne >>>>>>>>>>> >>>>>>>>>> >; Connor >>>>>>>>>>> Kelley >>>>>>>>>> >; >>>>>>>>>>> buildbot-admin at openssl.org >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> > *Subject:* >>>>>>>>>>> Re: [fips-sponsors] Buildbot workers [ Also >>>>>>>>>>> adding buildbot-admin at openssl.org >>>>>>>>>>> (I should >>>>>>>>>>> have done that long ago) ] Yes, some technical >>>>>>>>>>> details is what I'm trying to get. Right now, >>>>>>>>>>> that worker is building, sure, but that's a MacOS >>>>>>>>>>> build, which wasn't what you wanted. So Tim, >>>>>>>>>>> Connor, if you have something to share, I can >>>>>>>>>>> hopefully do better progress on our end. Cheers, >>>>>>>>>>> Richard On Mon, 17 May 2021 15:28:50 +0200, >>>>>>>>>>> Nivedita Chevvakula wrote: >>>>>>>>>>>> On this buildbot slave we don't run any our >>>>>>>>>>>> projects, we have set this slave only for >>>>>>>>>>>> buildbot worker. Please let me know if I give >>>>>>>>>>>> ssh creds it will expedite the process. Also >>>>>>>>>>>> adding Connor and Timmy, hopefully they can >>>>>>>>>>>> clarify on how we build OpenSSL project. Best, >>>>>>>>>>>> Niv ?On 5/13/21, 4:24 AM, "Richard Levitte" >>>>>>>>>>>> >>>>>>>>>>> > wrote: What we >>>>>>>>>>>> expect to do is this at a minimum: perl >>>>>>>>>>>> Configure {args...} make In the form that you >>>>>>>>>>>> filled in, there was the option to specify >>>>>>>>>>>> necessary environment variables (which can >>>>>>>>>>>> affect the configuration step) and >>>>>>>>>>>> configuration options. I was hoping that would >>>>>>>>>>>> be enough to get something going. I do not know >>>>>>>>>>>> what you're talking about regarding a .conf >>>>>>>>>>>> file created by the Configure step. I >>>>>>>>>>>> understand that you have some sort of super >>>>>>>>>>>> project that involves building OpenSSL as a >>>>>>>>>>>> component, though, so I can only assume that >>>>>>>>>>>> somewhere in there, it should be possible to >>>>>>>>>>>> find how the OpenSSL part is configured, i.e. I >>>>>>>>>>>> assume that there is a run of Configure hiding >>>>>>>>>>>> in there somewhere, and that it should be >>>>>>>>>>>> possible to see what arguments are used, as >>>>>>>>>>>> well as any relevant environment variables. >>>>>>>>>>>> Does this answer your question? Cheers, >>>>>>>>>>>> Richard On Fri, 07 May 2021 15:12:11 +0200, >>>>>>>>>>>> Nivedita Chevvakula wrote: >>>>>>>>>>>>>> We generate a project using cmake that gets >>>>>>>>>>>>>> built as a dependency of other components >>>>>>>>>>>>>> in our project. If you are trying to do - >>>>>>>>>>>>>> build everything using make, which requires >>>>>>>>>>>>>> a .conf file created with ./Configure step. >>>>>>>>>>>>>> If so should have one of those somewhere >>>>>>>>>>>>>> that satisfies what you are looking to >>>>>>>>>>>>>> produce for iOS, as well as a >>>>>>>>>>> different one for Android, please provide that we >>>>>>>>>>> can put it in place on the build bot and just use >>>>>>>>>>> that? >>>>>>>>>>>>>> Please advise. Best, >>>>>>>>>>>>> Niv >>>>>>>>>>>>>> ?On 5/4/21, 2:56 AM, "Richard Levitte" >>>>>>>>>>>>>> >>>>>>>>>>>>> > wrote: Hi, >>>>>>>>>>>>>> The worker is connecting fine, so far so >>>>>>>>>>>>>> good. However, I realised that there are >>>>>>>>>>>>>> things missing, where we need >>>>>>>>>>>>> information from you! >>>>>>>>>>>>>> This worker is meant to build for iOS, is >>>>>>>>>>>>>> it not? That should require >>>>>>>>>>>>> extra OpenSSL configuration options. So let >>>>>>>>>>>>> me ask you this, when you usually build >>>>>>>>>>>>> OpenSSL for iOS, exactly how do you usually >>>>>>>>>>>>> configure OpenSSL? >>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>> Richard >>>>>>>>>>>>>> On Tue, 04 May 2021 03:46:17 +0200, >>>>>>>>>>>>> Nivedita Chevvakula wrote: >>>>>>>>>>>>>>>> Richard, You can ignore my last mail >>>>>>>>>>>>>>>> with error starting buildbot. It is >>>>>>>>>>>>>>>> seems to work now after editing >>>>>>>>>>>>>> syntax for python2.7. Also we have created >>>>>>>>>>>>>> user ?buildbot? for this mac as >>>>>>>>>>>>>> recommended. Please let me know if we need >>>>>>>>>>>>>> to pass those credentials or need to setup >>>>>>>>>>>>>> anything else for the build bot. >>>>>>>>>>>>>>>> Best, Niv From: Nivedita Chevvakula >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> Date: Monday, May 3, 2021 at 6:44 PM To: >>>>>>>>>>>>>> Richard Levitte >>>>>>>>>>>>> > Subject: Re: >>>>>>>>>>>>>> [fips-sponsors] Buildbot workers >>>>>>>>>>>>>>>> Richard, Buildbot has now installed >>>>>>>>>>>>>>>> with linker, make, c compilers. While >>>>>>>>>>>>>>>> starting the worker to connect to >>>>>>>>>>>>>>>> master after editing tac file as you >>>>>>>>>>>>>>>> mentioned getting >>>>>>>>>>>>>> syntax error . not able to pin point why. >>>>>>>>>>>>>> Attaching the error log and the tac file >>>>>>>>>>>>>> here. Could you please help. >>>>>>>>>>>>>>>> Best, Niv From: Nivedita Chevvakula >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> Date: Monday, May 3, 2021 at 9:22 AM To: >>>>>>>>>>>>>> Richard Levitte >>>>>>>>>>>>> > Cc: >>>>>>>>>>>>>> "levitte at openssl.org >>>>>>>>>>>>>> " >>>>>>>>>>>>>> >>>>>>>>>>>>> >, Tim >>>>>>>>>>>>>> Champagne >>>>>>>>>>>>> >, Kevin >>>>>>>>>>>>>> Fox >>>>>>>>>>>>> > Subject: Re: >>>>>>>>>>>>>> [fips-sponsors] Buildbot workers >>>>>>>>>>>>>>>> Hi Richard, Thank you for sending the >>>>>>>>>>>>>>>> worker bot setup requirements, I will >>>>>>>>>>>>>>>> go thru and will set up the >>>>>>>>>>>>>> workerbot and will install the rest. Do you >>>>>>>>>>>>>> have any deadline for this setup please >>>>>>>>>>>>>> share so that it will help me prioritize. >>>>>>>>>>>>>>>> So far these tools are installed over >>>>>>>>>>>>>>>> the mac : 1. Android Studio 4.1.3 >>>>>>>>>>>>>> 2. Xcode 12.5 3. clang version 12.0.5 >>>>>>>>>>>>>> > > 4. Gcc 5. Visual Studio Community >>>>>>>>>>>>>> 2019 for Mac >>>>>>>>>>>>>>>> === Visual Studio Community 2019 for >>>>>>>>>>>>>>>> Mac === Version 8.9.7 (build 8) >>>>>>>>>>>>>>>> Installation UUID: >>>>>>>>>>>>>>>> f1ca8dad-7314-419a-8a39-880ba8a71230 >>>>>>>>>>>>>>>> GTK+ 2.24.23 (Raleigh theme) >>>>>>>>>>>>>>>> Xamarin.Mac 6.18.0.23 (d16-6 / >>>>>>>>>>>>>>>> 088c73638) Package version: 612000125 >>>>>>>>>>>>>>>> === Mono Framework MDK === Runtime: >>>>>>>>>>>>>>>> Mono 6.12.0.125 (2020-02/8c552e98bd6) >>>>>>>>>>>>>>>> (64-bit) Package version: 612000125 === >>>>>>>>>>>>>>>> Roslyn (Language Service) === >>>>>>>>>>>>>>>> 3.9.0-6.21152.10+c10f884b30737542ddd84ca889a4aad9281ce210 >>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>> === NuGet === >>>>>>>>>>>>>>>> Version: 5.8.0.6860 === .NET Core SDK >>>>>>>>>>>>>>>> === SDK: >>>>>>>>>>>>>>>> /usr/local/share/dotnet/sdk/5.0.202/Sdks >>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>> SDK Versions: >>>>>>>>>>>>>>>> 5.0.202 3.1.408 2.1.4 MSBuild SDKs: >>>>>>>>>>>>>>>> /Applications/Visual >>>>>>>>>>>>>>>> Studio.app/Contents/Resources/lib/monodevelop/bin/MSBuild/ >>>>>>>>>>>> >>>>>>>>>>>>>>>> >> Current/bin/Sdks >>>>>>>>>>>>>>>> === .NET Core Runtime === Runtime: >>>>>>>>>>>>>>>> /usr/local/share/dotnet/dotnet Runtime >>>>>>>>>>>>>>>> Versions: 5.0.5 3.1.14 2.0.5 === .NET >>>>>>>>>>>>>>>> Core 3.1 SDK === SDK: 3.1.408 === >>>>>>>>>>>>>>>> Xamarin.Profiler === Version: >>>>>>>>>>>>>>>> 1.6.15.68 Location: >>>>>>>>>>>>>>>> /Applications/Xamarin >>>>>>>>>>>>>>>> Profiler.app/Contents/MacOS/Xamarin >>>>>>>>>>>>>>>> Profiler === Updater === Version: 11 >>>>>>>>>>>>>>>> === Apple Developer Tools === Xcode >>>>>>>>>>>>>>>> 12.5 (18205) Build 12E262 === >>>>>>>>>>>>>>>> Xamarin.Mac === Xamarin.Mac not >>>>>>>>>>>>>>>> installed. Can't find >>>>>>>>>>>>>>>> /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/ >>>>>>>>>>>> >>>>>>>>>>>>>>>> >> Version. >>>>>>>>>>>>>>>> === Xamarin.iOS === Xamarin.iOS not >>>>>>>>>>>>>>>> installed. Can't find mtouch or the >>>>>>>>>>>>>>>> Version file at >>>>>>>>>>>>>>>> /Library/Frameworks/Xamarin.iOS.framework/Versions/ >>>>>>>>>>>> >>>>>>>>>>>>>>>> >> Current. >>>>>>>>>>>>>>>> === Xamarin Designer === Version: >>>>>>>>>>>>>>>> 16.9.0.324 Hash: b1e216c75 Branch: >>>>>>>>>>>>>>>> remotes/origin/d16-9 Build date: >>>>>>>>>>>>>>>> 2021-04-16 00:02:50 UTC === >>>>>>>>>>>>>>>> Xamarin.Android === Version: 11.2.2.1 >>>>>>>>>>>>>>>> (Visual Studio Community) Commit: >>>>>>>>>>>>>>>> xamarin-android/d16-9/877f572 Android >>>>>>>>>>>>>>>> SDK: >>>>>>>>>>>>>>>> /Users/ec2-user/Library/Developer/Xamarin/android-sdk-macosx >>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>> Supported Android versions: >>>>>>>>>>>>>>>> None installed SDK Tools Version: >>>>>>>>>>>>>>>> 26.1.1 SDK Platform Tools Version: >>>>>>>>>>>>>>>> 30.0.4 SDK Build Tools Version: 30.0.2 >>>>>>>>>>>>>>>> Build Information: Mono: 5e9cb6d >>>>>>>>>>>>>>>> Java.Interop: >>>>>>>>>>>>>>>> xamarin/java.interop/d16-9 at 54f8c24 >>>>>>>>>>>>>>>> ProGuard: >>>>>>>>>>>>>>>> Guardsquare/proguard/v7.0.1 at 912d149 >>>>>>>>>>>>>>>> SQLite: xamarin/sqlite/3.34.1 at daff8f4 >>>>>>>>>>>>>>>> Xamarin.Android Tools: >>>>>>>>>>>>>>>> xamarin/xamarin-android-tools/d16-9 at d210f11 >>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>> === Microsoft OpenJDK for Mobile === >>>>>>>>>>>>>>>> Java SDK: >>>>>>>>>>>>>>>> /Users/ec2-user/Library/Developer/Xamarin/jdk/microsoft_dist_openjdk_1.8.0.25 >>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>> 1.8.0-25 >>>>>>>>>>>>>>>> Android Designer EPL code available >>>>>>>>>>>>>>>> here: >>>>>>>>>>>>>>>> https://github.com/xamarin/AndroidDesigner.EPL >>>>>>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> === Android SDK Manager === Version: >>>>>>>>>>>>>>>> 16.9.0.22 Hash: a391de2 Branch: >>>>>>>>>>>>>>>> remotes/origin/d16-9~2 Build date: >>>>>>>>>>>>>>>> 2021-03-24 08:30:26 UTC === Android >>>>>>>>>>>>>>>> Device Manager === Version: 16.9.0.17 >>>>>>>>>>>>>>>> Hash: fc2b3db Branch: >>>>>>>>>>>>>>>> remotes/origin/dev/jmt/d16-9bump~1 >>>>>>>>>>>>>>>> Build date: 2021-03-24 08:30:44 UTC === >>>>>>>>>>>>>>>> Build Information === Release ID: >>>>>>>>>>>>>>>> 809070008 Git revision: >>>>>>>>>>>>>>>> 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>> Build date: 2021-04-16 07:38:03-04 >>>>>>>>>>>>>>>> Build branch: release-8.9 Xamarin >>>>>>>>>>>>>>>> extensions: >>>>>>>>>>>>>>>> 8b7ac2442978ec88d09703fafa4e43eb774f0a26 >>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>> === Operating System === >>>>>>>>>>>>>>>> Mac OS X 10.16.0 Darwin 20.3.0 Darwin >>>>>>>>>>>>>>>> Kernel Version 20.3.0 Thu Jan 21 >>>>>>>>>>>>>>>> 00:07:06 PST 2021 >>>>>>>>>>>>>>>> root:xnu-7195.81.3~1/RELEASE_X86_64 >>>>>>>>>>>>>>>> x86_64 Best, Niv From: Richard Levitte >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> > >>>>>>>>>>>>>> Date: Monday, May 3, 2021 at 4:54 AM To: >>>>>>>>>>>>>> Nivedita Chevvakula >>>>>>>>>>>>>> >>>>>>>>>>>>> > Cc: >>>>>>>>>>>>>> levitte at openssl.org >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >, Tim >>>>>>>>>>>>>> Champagne >>>>>>>>>>>>> >, Kevin >>>>>>>>>>>>>> Fox >>>>>>>>>>>>> > Subject: Re: >>>>>>>>>>>>>> [fips-sponsors] Buildbot workers >>>>>>>>>>>>>>>> Hi, Thank you for offering workers to >>>>>>>>>>>>>>>> us! To be able to set up your worker, >>>>>>>>>>>>>>>> you must use version 2.6.0 or >>>>>>>>>>>>>> higher. Older version do not support >>>>>>>>>>>>>> TLS-protected connections. >>>>>>>>>>>>>>>> Please see these instructions for >>>>>>>>>>>>>>>> installing the buildbot worker >>>>>>>>>>>>>> software: >>>>>>>>>>>>>>>> http://docs.buildbot.net/latest/manual/installation/worker.html >>>>>>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> When buildbot has been installed on the >>>>>>>>>>>>>>>> platform where the buildbot >>>>>>>>>>>>>> worker is to be run, this is how a worker >>>>>>>>>>>>>> is created: >>>>>>>>>>>>>>>> $ buildbot-worker create-worker >>>>>>>>>>>>>>>> --use-tls BASEDIR \ >>>>>>>>>>>>>> buildbot.openssl.org:9989 >>>>>>>>>>>>>> >>>>>>>>>>>>>> 'bluecedar-01' 'Rak;osErfabOn5' >>>>>>>>>>>>>>>> where BASEDIR is determined by you. >>>>>>>>>>>>>>>> See further down for a few notes >>>>>>>>>>>>>> on TLS. >>>>>>>>>>>>>>>> To run a buildbot worker, you do this: >>>>>>>>>>>>>>>> $ buildbot-worker start BASEDIR Apart >>>>>>>>>>>>>>>> from the software needed to run a >>>>>>>>>>>>>>>> buildbot worker, and the >>>>>>>>>>>>>> utilities that are the normal part of the >>>>>>>>>>>>>> operating system, you also need to ensure >>>>>>>>>>>>>> that the following components are >>>>>>>>>>>>>> available: >>>>>>>>>>>>>>>> - toolchains, i.e. C compiler, >>>>>>>>>>>>>>>> linker, make. If you have specified >>>>>>>>>>>>>> toolchains in the worker request form, you >>>>>>>>>>>>>> need to ensure that all of them are >>>>>>>>>>>>>> installed. >>>>>>>>>>>>>>>> - git Regarding TLS, it may be that >>>>>>>>>>>>>>>> the buildbot worker platform doesn't >>>>>>>>>>>>>> have the appropriate certification >>>>>>>>>>>>>> verification roots set up. In that case, >>>>>>>>>>>>>> you may need to apply the attached >>>>>>>>>>>>>> buildbot.tac patch, and store the attached >>>>>>>>>>>>>> PEM files in a directory of your choice. >>>>>>>>>>>>>> Finish up by find the string >>>>>>>>>>>>>> '/PATH/TO/ssl-roots-dir' and replace its >>>>>>>>>>>>>> contents with the path of directory where >>>>>>>>>>>>>> you stored the PEM files. >>>>>>>>>>>>>>>>> -- > Richard Levitte >>>>>>>>>>>>>>>>> levitte at openssl.org >>>>>>>>>>>>>>>>> >>>>>>>>>>>>> OpenSSL Project >>>>>>>>>>>>> http://www.openssl.org/~levitte/ >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> > >>>>>>>>>>>> -- Richard Levitte levitte at openssl.org >>>>>>>>>>>> OpenSSL Project >>>>>>>>>>>> http://www.openssl.org/~levitte/ >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> > >>>>>>>>>>> -- Richard Levitte levitte at openssl.org >>>>>>>>>>> OpenSSL Project >>>>>>>>>>> http://www.openssl.org/~levitte/ >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> > >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> buildbot-admin mailing list >>>>>>>>>>> buildbot-admin at openssl.org >>>>>>>>>>> >>>>>>>>>>> https://mta.openssl.org/mailman/listinfo/buildbot-admin > From grace.hopkins at oracle.com Thu May 27 16:15:32 2021 From: grace.hopkins at oracle.com (Grace Hopkins) Date: Thu, 27 May 2021 12:15:32 -0400 Subject: [buildbot-admin] Fwd: FW: [External] : Re: Oracle Build Bot Workers In-Reply-To: References: Message-ID: Hello Richard, I am setting up the Oracle X5 Buildbot Worker for OpenSSL. I need the Buildbot Worker credentials (worker name and password) so I can run buildbot-worker create-worker. Can you help me with this? If you are not the correct person to ask about the Buildbot Worker credentials, can you recommend someone else? Thank you, Grace Hopkins -------- Forwarded Message -------- Subject: FW: [External] : Re: [buildbot-admin] Oracle Build Bot Workers Date: Thu, 27 May 2021 10:21:50 -0400 From: Chris Brych To: Grace Hopkins , John Ackerley , Tom Dwyer FYI.? I think you need these certificates on the machine to run build bot. *From:* Chris Brych *Sent:* May 6, 2021 11:29 AM *To:* Ales Cernosek ; Steve McKinty ; John Ackerley ; Tom Dwyer ; Jennifer Brady *Subject:* FW: [External] : Re: [buildbot-admin] Oracle Build Bot Workers HI Ales, I received certificates from OpenSSL needed for use with Build bot.? I?ve attached them. Cheers, Chris -----Original Message----- From: Richard Levitte [mailto:levitte at openssl.org ] Sent: May 4, 2021 3:20 AM To: Chris Brych > Cc: buildbot-admin at openssl.org ; Shane Lontis >; Jennifer Brady > Subject: [External] : Re: [buildbot-admin] Oracle Build Bot Workers An attachment in the email has been found to contain executable code and has been removed. File removed : isrg-root-x1.pem, diff,pem ---------------------------------------------------------------------- I have set up the solaris worker, the other two will need a conversation, which I'm taking separately. Thank you for offering workers to us! To be able to set up your worker, you must use version 3.0 or higher.? Older version do not support TLS-protected connections. Please see these instructions for installing the buildbot worker software: https://urldefense.com/v3/__http://docs.buildbot.net/latest/manual/installation/worker.html__;!!GqivPVa7Brio!LJqMxflBlaYCVWIutYLFLeDGtfGkNQRcUvx2kKGZjq9oTHcw2EwDMkfO9rXthZkesg$ When buildbot has been installed on the platform where the buildbot worker is to be run, this is how a worker is created: ??? $ buildbot-worker create-worker --use-tls BASEDIR \ ??????? buildbot.openssl.org:9989 Oracle-Solaris-Sparc-M8 '