Closed mssonicbld closed 7 months ago
/azp run Azure.sonic-sairedis
/azp run Azure.sonic-sairedis
this change has nothing to do with swss, i think swss build is broken
/azp run Azure.sonic-sairedis
/azp run Azure.sonic-sairedis
There's no new builds of https://dev.azure.com/mssonic/build/_build?definitionId=465&_a=summary&view=runs for some reason. That is likely causing this failure.
@xumia Looks like that pipeline got disabled because it didn't get classified. Would you be able to help with classifying that pipeline and re-enabling it? I tried to do it, but couldn't find the link to do so.
@xumia Looks like that pipeline got disabled because it didn't get classified. Would you be able to help with classifying that pipeline and re-enabling it? I tried to do it, but couldn't find the link to do so.
It is good now, right? I do nothing.
/azp run
/azp run Azure.sonic-sairedis
/azp run Azure.sonic-sairedis
/azp run Azure.sonic-sairedis
can you add empty commit to this PR ? to see if it will trigger pipeline change ? since somehow pipeline is broken and not adding extra step instaling dash api, hence swss build error
/azp run Azure.sonic-sairedis
@xumia Looks like that pipeline got disabled because it didn't get classified. Would you be able to help with classifying that pipeline and re-enabling it? I tried to do it, but couldn't find the link to do so.
It is good now, right? I do nothing.
@xumia This is for the pipeline at https://dev.azure.com/mssonic/build/_build?definitionId=465&_a=summary (building the lib-packages
target of sonic-buildimage and publishing those artifacts). It was disabled back in December because the pipeline didn't appear to be assigned to a service. To unblock this cherry-pick PR, I manually re-enabled the pipeline, triggered a build for master and 202311 branch, and then disabled the pipeline after the builds finished.
Is that pipeline now assigned to a service? If so, it can be re-enabled, I think.
This fixes a breakage from #1194 where code coverage and ASAN were not enabled, due to DEB_CONFIGURE_EXTRA_FLAGS no longer being used in dh_auto_configure.
Signed-off-by: Saikrishna Arcot sarcot@microsoft.com