[Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018
Hi, We were trying to pick up patches for some issues which we had reported like SSH not working and failing to attach data interface from controller to compute nodes. We failed to make the build. at step 2 of section Download Packages¶ from https://docs.starlingx.io/developer_guide/index.html#build-the-centos-mirror... document. when we run download_mirror.sh from the container There is one package which fails to download lighttpd-1.4.50-1.el7.src.rpm which is there in rpms_centos.lst. Since this version is not there on any mirror on internet, the version available is lighttpd-1.4.51-1.el7.src.rpm so we updated the file rpms_centos.lst and rpms_centos3rdparties.lst with lighttpd-1.4.51-1.el7.x86_64.rpm instead. Ran the download_mirror.sh again. Now everything is fine except it is failing in build-pkgs step with the following error. b6: ERROR: build_dir (415): Invalid srpm path 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as '/localdisk/designer/builder/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', found in '/localdisk/designer/builder/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path' now we are stuck and unable to build. Any suggestions would be welcome. on a general note, had a quick query how much time the incremental build is taking in general. Because we follow the steps for incremental build after step git clone https://git.starlingx.io/stx-tools and then we build the container image and all steps after that which is also taking 3 to 4 hours. Am I doing the incremental build properly?? Best Regards, Rajesh Jha The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment.
Try updating your stx-tools and running download_mirror.sh again. Alternatively, you can find it here ... http://mirror.starlingx.cengn.ca/mirror/centos/epel/dl.fedoraproject.org/pub... Scott On 18-11-02 05:19 AM, Rajesh Jha wrote:
Hi,
We were trying to pick up patches for some issues which we had reported like SSH not working and failing to attach data interface from controller to compute nodes. We failed to make the build. at step 2 of section Download Packages¶ from https://docs.starlingx.io/developer_guide/index.html#build-the-centos-mirror... document. when we run download_mirror.sh from the container There is one package which fails to download lighttpd-1.4.50-1.el7.src.rpm which is there in rpms_centos.lst. Since this version is not there on any mirror on internet, the version available is lighttpd-1.4.51-1.el7.src.rpm so we updated the file rpms_centos.lst and rpms_centos3rdparties.lst with lighttpd-1.4.51-1.el7.x86_64.rpm instead. Ran the download_mirror.sh again. Now everything is fine except it is failing in build-pkgs step with the following error.
b6: ERROR: build_dir (415): Invalid srpm path 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as '/localdisk/designer/builder/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', found in '/localdisk/designer/builder/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path'
now we are stuck and unable to build. Any suggestions would be welcome.
on a general note, had a quick query how much time the incremental build is taking in general. Because we follow the steps for incremental build after step git clone https://git.starlingx.io/stx-tools
and then we build the container image and all steps after that which is also taking 3 to 4 hours. Am I doing the incremental build properly??
Best Regards, Rajesh Jha
The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment.
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi all, Do we have bug/story to track the issue? I prefer to upgrade the lighttpd src rpm to 1.4.51 to solve it. Best Regards Shuicheng -----Original Message----- From: Scott Little [mailto:scott.little@windriver.com] Sent: Saturday, November 3, 2018 4:23 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 Try updating your stx-tools and running download_mirror.sh again. Alternatively, you can find it here ... http://mirror.starlingx.cengn.ca/mirror/centos/epel/dl.fedoraproject.org/pub... Scott On 18-11-02 05:19 AM, Rajesh Jha wrote:
Hi,
We were trying to pick up patches for some issues which we had reported like SSH not working and failing to attach data interface from controller to compute nodes. We failed to make the build. at step 2 of section Download Packages¶ from https://docs.starlingx.io/developer_guide/index.html#build-the-centos-mirror... document. when we run download_mirror.sh from the container There is one package which fails to download lighttpd-1.4.50-1.el7.src.rpm which is there in rpms_centos.lst. Since this version is not there on any mirror on internet, the version available is lighttpd-1.4.51-1.el7.src.rpm so we updated the file rpms_centos.lst and rpms_centos3rdparties.lst with lighttpd-1.4.51-1.el7.x86_64.rpm instead. Ran the download_mirror.sh again. Now everything is fine except it is failing in build-pkgs step with the following error.
b6: ERROR: build_dir (415): Invalid srpm path 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as '/localdisk/designer/builder/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', found in '/localdisk/designer/builder/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path'
now we are stuck and unable to build. Any suggestions would be welcome.
on a general note, had a quick query how much time the incremental build is taking in general. Because we follow the steps for incremental build after step git clone https://git.starlingx.io/stx-tools
and then we build the container image and all steps after that which is also taking 3 to 4 hours. Am I doing the incremental build properly??
Best Regards, Rajesh Jha
The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment.
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi all, I created a story for it: https://storyboard.openstack.org/#!/story/2004282 And here is the code. Please help review it: https://review.openstack.org/616061 https://review.openstack.org/616062 I have done build and deploy test. Please share me if there is any more test need be done. Thanks. Best Regards Shuicheng -----Original Message----- From: Lin, Shuicheng Sent: Wednesday, November 7, 2018 9:34 AM To: 'Scott Little' <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 Hi all, Do we have bug/story to track the issue? I prefer to upgrade the lighttpd src rpm to 1.4.51 to solve it. Best Regards Shuicheng -----Original Message----- From: Scott Little [mailto:scott.little@windriver.com] Sent: Saturday, November 3, 2018 4:23 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 Try updating your stx-tools and running download_mirror.sh again. Alternatively, you can find it here ... http://mirror.starlingx.cengn.ca/mirror/centos/epel/dl.fedoraproject.org/pub... Scott On 18-11-02 05:19 AM, Rajesh Jha wrote:
Hi,
We were trying to pick up patches for some issues which we had reported like SSH not working and failing to attach data interface from controller to compute nodes. We failed to make the build. at step 2 of section Download Packages¶ from https://docs.starlingx.io/developer_guide/index.html#build-the-centos-mirror... document. when we run download_mirror.sh from the container There is one package which fails to download lighttpd-1.4.50-1.el7.src.rpm which is there in rpms_centos.lst. Since this version is not there on any mirror on internet, the version available is lighttpd-1.4.51-1.el7.src.rpm so we updated the file rpms_centos.lst and rpms_centos3rdparties.lst with lighttpd-1.4.51-1.el7.x86_64.rpm instead. Ran the download_mirror.sh again. Now everything is fine except it is failing in build-pkgs step with the following error.
b6: ERROR: build_dir (415): Invalid srpm path 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as '/localdisk/designer/builder/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', found in '/localdisk/designer/builder/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path'
now we are stuck and unable to build. Any suggestions would be welcome.
on a general note, had a quick query how much time the incremental build is taking in general. Because we follow the steps for incremental build after step git clone https://git.starlingx.io/stx-tools
and then we build the container image and all steps after that which is also taking 3 to 4 hours. Am I doing the incremental build properly??
Best Regards, Rajesh Jha
The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment.
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi all, Anybody has +2 for stx-tools, please help review patch and W+1 for https://review.openstack.org/616062 . Otherwise it will break build, since https://review.openstack.org/616061 is already merged. Thanks. Best Regards Shuicheng -----Original Message----- From: Lin, Shuicheng Sent: Wednesday, November 7, 2018 12:29 PM To: Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 Hi all, I created a story for it: https://storyboard.openstack.org/#!/story/2004282 And here is the code. Please help review it: https://review.openstack.org/616061 https://review.openstack.org/616062 I have done build and deploy test. Please share me if there is any more test need be done. Thanks. Best Regards Shuicheng -----Original Message----- From: Lin, Shuicheng Sent: Wednesday, November 7, 2018 9:34 AM To: 'Scott Little' <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 Hi all, Do we have bug/story to track the issue? I prefer to upgrade the lighttpd src rpm to 1.4.51 to solve it. Best Regards Shuicheng -----Original Message----- From: Scott Little [mailto:scott.little@windriver.com] Sent: Saturday, November 3, 2018 4:23 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 Try updating your stx-tools and running download_mirror.sh again. Alternatively, you can find it here ... http://mirror.starlingx.cengn.ca/mirror/centos/epel/dl.fedoraproject.org/pub... Scott On 18-11-02 05:19 AM, Rajesh Jha wrote:
Hi,
We were trying to pick up patches for some issues which we had reported like SSH not working and failing to attach data interface from controller to compute nodes. We failed to make the build. at step 2 of section Download Packages¶ from https://docs.starlingx.io/developer_guide/index.html#build-the-centos-mirror... document. when we run download_mirror.sh from the container There is one package which fails to download lighttpd-1.4.50-1.el7.src.rpm which is there in rpms_centos.lst. Since this version is not there on any mirror on internet, the version available is lighttpd-1.4.51-1.el7.src.rpm so we updated the file rpms_centos.lst and rpms_centos3rdparties.lst with lighttpd-1.4.51-1.el7.x86_64.rpm instead. Ran the download_mirror.sh again. Now everything is fine except it is failing in build-pkgs step with the following error.
b6: ERROR: build_dir (415): Invalid srpm path 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as '/localdisk/designer/builder/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', found in '/localdisk/designer/builder/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path'
now we are stuck and unable to build. Any suggestions would be welcome.
on a general note, had a quick query how much time the incremental build is taking in general. Because we follow the steps for incremental build after step git clone https://git.starlingx.io/stx-tools
and then we build the container image and all steps after that which is also taking 3 to 4 hours. Am I doing the incremental build properly??
Best Regards, Rajesh Jha
The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment.
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On 11/7/18 6:32 PM, Lin, Shuicheng wrote:
Hi all, Anybody has +2 for stx-tools, please help review patch and W+1 for https://review.openstack.org/616062 . Otherwise it will break build, since https://review.openstack.org/616061 is already merged. Thanks.
Did you not set the Depends-On Correctly? We need to make sure that they are ordered correctly and blocked until the right one merges first in the future. Sau!
Best Regards Shuicheng
-----Original Message----- From: Lin, Shuicheng Sent: Wednesday, November 7, 2018 12:29 PM To: Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018
Hi all, I created a story for it: https://storyboard.openstack.org/#!/story/2004282
And here is the code. Please help review it: https://review.openstack.org/616061 https://review.openstack.org/616062 I have done build and deploy test. Please share me if there is any more test need be done. Thanks.
Best Regards Shuicheng
-----Original Message----- From: Lin, Shuicheng Sent: Wednesday, November 7, 2018 9:34 AM To: 'Scott Little' <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018
Hi all, Do we have bug/story to track the issue? I prefer to upgrade the lighttpd src rpm to 1.4.51 to solve it.
Best Regards Shuicheng
-----Original Message----- From: Scott Little [mailto:scott.little@windriver.com] Sent: Saturday, November 3, 2018 4:23 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018
Try updating your stx-tools and running download_mirror.sh again.
Alternatively, you can find it here ...
http://mirror.starlingx.cengn.ca/mirror/centos/epel/dl.fedoraproject.org/pub...
Scott
On 18-11-02 05:19 AM, Rajesh Jha wrote:
Hi,
We were trying to pick up patches for some issues which we had reported like SSH not working and failing to attach data interface from controller to compute nodes. We failed to make the build. at step 2 of section Download Packages¶ from https://docs.starlingx.io/developer_guide/index.html#build-the-centos-mirror... document. when we run download_mirror.sh from the container There is one package which fails to download lighttpd-1.4.50-1.el7.src.rpm which is there in rpms_centos.lst. Since this version is not there on any mirror on internet, the version available is lighttpd-1.4.51-1.el7.src.rpm so we updated the file rpms_centos.lst and rpms_centos3rdparties.lst with lighttpd-1.4.51-1.el7.x86_64.rpm instead. Ran the download_mirror.sh again. Now everything is fine except it is failing in build-pkgs step with the following error.
b6: ERROR: build_dir (415): Invalid srpm path 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as '/localdisk/designer/builder/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', found in '/localdisk/designer/builder/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path'
now we are stuck and unable to build. Any suggestions would be welcome.
on a general note, had a quick query how much time the incremental build is taking in general. Because we follow the steps for incremental build after step git clone https://git.starlingx.io/stx-tools
and then we build the container image and all steps after that which is also taking 3 to 4 hours. Am I doing the incremental build properly??
Best Regards, Rajesh Jha
The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment.
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi Saul, The two patches need be merged together, so it is like A and B depends on each other. But currently in gerrit/zuul, we cannot make patch depends on each other. It is a limitation I think. So I just set A depends on B. Best Regards Shuicheng -----Original Message----- From: Saul Wold [mailto:sgw@linux.intel.com] Sent: Thursday, November 8, 2018 1:06 PM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 On 11/7/18 6:32 PM, Lin, Shuicheng wrote:
Hi all, Anybody has +2 for stx-tools, please help review patch and W+1 for https://review.openstack.org/616062 . Otherwise it will break build, since https://review.openstack.org/616061 is already merged. Thanks.
Did you not set the Depends-On Correctly? We need to make sure that they are ordered correctly and blocked until the right one merges first in the future. Sau!
Best Regards Shuicheng
-----Original Message----- From: Lin, Shuicheng Sent: Wednesday, November 7, 2018 12:29 PM To: Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018
Hi all, I created a story for it: https://storyboard.openstack.org/#!/story/2004282
And here is the code. Please help review it: https://review.openstack.org/616061 https://review.openstack.org/616062 I have done build and deploy test. Please share me if there is any more test need be done. Thanks.
Best Regards Shuicheng
-----Original Message----- From: Lin, Shuicheng Sent: Wednesday, November 7, 2018 9:34 AM To: 'Scott Little' <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018
Hi all, Do we have bug/story to track the issue? I prefer to upgrade the lighttpd src rpm to 1.4.51 to solve it.
Best Regards Shuicheng
-----Original Message----- From: Scott Little [mailto:scott.little@windriver.com] Sent: Saturday, November 3, 2018 4:23 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018
Try updating your stx-tools and running download_mirror.sh again.
Alternatively, you can find it here ...
http://mirror.starlingx.cengn.ca/mirror/centos/epel/dl.fedoraproject.o rg/pub/epel/7/SRPMS/Packages/l/lighttpd-1.4.50-1.el7.src.rpm
Scott
On 18-11-02 05:19 AM, Rajesh Jha wrote:
Hi,
We were trying to pick up patches for some issues which we had reported like SSH not working and failing to attach data interface from controller to compute nodes. We failed to make the build. at step 2 of section Download Packages¶ from https://docs.starlingx.io/developer_guide/index.html#build-the-centos-mirror... document. when we run download_mirror.sh from the container There is one package which fails to download lighttpd-1.4.50-1.el7.src.rpm which is there in rpms_centos.lst. Since this version is not there on any mirror on internet, the version available is lighttpd-1.4.51-1.el7.src.rpm so we updated the file rpms_centos.lst and rpms_centos3rdparties.lst with lighttpd-1.4.51-1.el7.x86_64.rpm instead. Ran the download_mirror.sh again. Now everything is fine except it is failing in build-pkgs step with the following error.
b6: ERROR: build_dir (415): Invalid srpm path 'mirror:Source/lighttpd-1.4.50-1.el7.src.rpm', evaluated as '/localdisk/designer/builder/starlingx/cgcs-root/cgcs-centos-repo/Source/lighttpd-1.4.50-1.el7.src.rpm', found in '/localdisk/designer/builder/starlingx/cgcs-root/stx/stx-integ/base/lighttpd/centos/srpm_path'
now we are stuck and unable to build. Any suggestions would be welcome.
on a general note, had a quick query how much time the incremental build is taking in general. Because we follow the steps for incremental build after step git clone https://git.starlingx.io/stx-tools
and then we build the container image and all steps after that which is also taking 3 to 4 hours. Am I doing the incremental build properly??
Best Regards, Rajesh Jha
The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, please immediately alert the sender by reply e-mail and then delete this message. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. R Systems has taken every reasonable precaution to minimize the risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment.
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On Wed, Nov 7, 2018 at 11:12 PM Lin, Shuicheng <shuicheng.lin@intel.com> wrote:
The two patches need be merged together, so it is like A and B depends on each other. But currently in gerrit/zuul, we cannot make patch depends on each other. It is a limitation I think. So I just set A depends on B.
In this situation the best approach is to get A approved first. It will go through the gate pipeline but will not merge until B is approved. When B gets through the gate pipeline they will both merge close together. It is still not at exactly the same time but is gets close. You do not have to wait until A is done before approving B, you just want it to get started enough earlier so B does not finish ahead of it. This minimizes the gap between the merges. dt -- Dean Troyer dtroyer@gmail.com
Hi StarlingX, One possible workaround particular for the case of modifying the lst files are to use 3 commits: A - Adds the new source rpm to the .lst file in stx-tools B - Changes the code in [your git] to use the new source RPM C - Removes the old source rpm from the .lst file in stx-tools C Depends-On B B Depends-On A The only downside is that for some window, you might have two versions of the source rpm in your workspace, eating an extra few MB of disk space. -Jason
-----Original Message----- From: Dean Troyer <dtroyer@gmail.com> Sent: November 8, 2018 10:56 AM To: Lin, Shuicheng <shuicheng.lin@intel.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018
On Wed, Nov 7, 2018 at 11:12 PM Lin, Shuicheng <shuicheng.lin@intel.com> wrote:
The two patches need be merged together, so it is like A and B depends on each other. But currently in gerrit/zuul, we cannot make patch depends on each other. It is a limitation I think. So I just set A depends on B.
In this situation the best approach is to get A approved first. It will go through the gate pipeline but will not merge until B is approved. When B gets through the gate pipeline they will both merge close together. It is still not at exactly the same time but is gets close.
You do not have to wait until A is done before approving B, you just want it to get started enough earlier so B does not finish ahead of it. This minimizes the gap between the merges.
dt
--
Dean Troyer dtroyer@gmail.com
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Set the workflow of A to -1, set B to depend on A. Once B is fully approved and W+1, then A can be W+1, and (hopefully) they get merged in the same window. -----Original Message----- From: McKenna, Jason [mailto:Jason.McKenna@windriver.com] Sent: Thursday, November 08, 2018 12:15 PM To: Dean Troyer; Lin, Shuicheng Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018 Hi StarlingX, One possible workaround particular for the case of modifying the lst files are to use 3 commits: A - Adds the new source rpm to the .lst file in stx-tools B - Changes the code in [your git] to use the new source RPM C - Removes the old source rpm from the .lst file in stx-tools C Depends-On B B Depends-On A The only downside is that for some window, you might have two versions of the source rpm in your workspace, eating an extra few MB of disk space. -Jason
-----Original Message----- From: Dean Troyer <dtroyer@gmail.com> Sent: November 8, 2018 10:56 AM To: Lin, Shuicheng <shuicheng.lin@intel.com> Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Build failure on lastest build Sterling 31/10/2018
On Wed, Nov 7, 2018 at 11:12 PM Lin, Shuicheng <shuicheng.lin@intel.com> wrote:
The two patches need be merged together, so it is like A and B depends on each other. But currently in gerrit/zuul, we cannot make patch depends on each other. It is a limitation I think. So I just set A depends on B.
In this situation the best approach is to get A approved first. It will go through the gate pipeline but will not merge until B is approved. When B gets through the gate pipeline they will both merge close together. It is still not at exactly the same time but is gets close.
You do not have to wait until A is done before approving B, you just want it to get started enough earlier so B does not finish ahead of it. This minimizes the gap between the merges.
dt
--
Dean Troyer dtroyer@gmail.com
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
participants (7)
-
Dean Troyer
-
Lin, Shuicheng
-
McKenna, Jason
-
Penney, Don
-
Rajesh Jha
-
Saul Wold
-
Scott Little