[Mellanox] Fix component versions caching bug #19982
Conversation
skr31
force-pushed
the
fix_version_component_caching
branch
from
a57b184 to
21360b4
Compare
|
/azpw ms_conflict -f |
|
/azpw run |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run |
|
/AzurePipelines run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run Azure.sonic-buildimage |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azpw run Azure.sonic-buildimage |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/AzurePipelines run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
PR test retriggered. |
|
/azpw Azure.sonic-buildimage |
|
/azp run Azure.sonic-buildimage |
|
PR validation will not pass. Please bypass policy force merge. |
@liushilongbuaa , Do we need to do something here ? or the maintainer can handle it ? |
Maintainer can handle it. |
|
@bingwang-ms , based on the comment above, can you please merge ? |
|
@bingwang-ms , Can you please merge and also cherry pick to 202405 ? |
|
@bingwang-ms , Can you please merge ? |
|
@skr31 please check failures. we need this to get into 202405 |
@liat-grozovik there are no failure for @skr31 to check.
So we can't rerun this checker and no matter what we do/did in the last 3 months - this checker will stay failed and it is a false alert. |
skr31
force-pushed
the
fix_version_component_caching
branch
from
21360b4 to
2222f7e
Compare
|
@bingwang-ms , Can you please cherry pick to 202405 ? |
- Why I did it The component versions file that is created during compilation was not being updated because it was being cached, even when some of the versions on it should have been updated. - How I did it Removed component-versions.dep
|
Cherry-pick PR to 202405: #21094 |
- Why I did it The component versions file that is created during compilation was not being updated because it was being cached, even when some of the versions on it should have been updated. - How I did it Removed component-versions.dep
mssonicbld
added
Included in 202405 Branch
and removed
Created PR to 202405 Branch
labels
|
Cherry-pick PR to 202411: #21410 |
mssonicbld
added
Included in 202411 Branch
and removed
Created PR to 202411 Branch
labels
- Why I did it The component versions file that is created during compilation was not being updated because it was being cached, even when some of the versions on it should have been updated. - How I did it Removed component-versions.dep
Why I did it
The component versions file that is created during compilation was not being updated because it was being cached, even when some of the versions on it should have been updated.
Work item tracking
How I did it
Removed component-versions.dep
How to verify it
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)