[submodule][master] Update submodule sonic-host-services to the latest HEAD automatically#22160
Conversation
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
e43b909 to
5646143
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
5646143 to
e2b1373
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
e2b1373 to
3103f82
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
3103f82 to
106b3a1
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
With pygobject=3.5.0, we are seeing build failures(marvell_prestera_armhf), could you please check. Collecting PyGObject==3.50.0 × pip subprocess to install build dependencies did not run successfully. |
|
I assume you're referring to this result looks like the actual error is I don't think it's related to the pygobject pinning since the other targets all succeeded. |
|
So I think there is a problem that we have Which obviously causes a conflict with the sonic-host-services change but then I'm not sure why we had the original build failure that my change was attempting to fix. I'm not sure if changing that to match will fix the actual problem but it probably should be done. How can I add that to the auto generated bumps? |
|
I'm having problems building the armhf target locally even without the host-services change |
|
So my first problem was caused because my local I've kicked off a build now but looks like it'll take a while |
106b3a1 to
adc3629
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Eventually my local make configure failed with so I still can't get to a point of seeing the failure from the pipeline I think the fix might be as simple as updating |
adc3629 to
9db04b0
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
9db04b0 to
0f6a327
Compare
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Why I did it
src/sonic-host-services
How I did it
How to verify it
Description for the changelog