Hello @randombit, @reneme, @devnexen,

I investigated this issue to assess the current situation and determine if any changes were required. My goal was to create a PR to revert back to the previous configuration if the issue was resolved and to observe the current situation in CI.

Research Summary:

I reviewed the related issue report. This bug report was moved to a discussion due to the length of the resolution process. Then, after a long review, @lkfortuna notified the community that the bug was fixed on February 13th with the following message:

"closing as fixed by #9679"

I have observed that the bug has been resolved and many projects have switched their CI builds from workarounds to standard operation.

I analyzed src/scripts/ci/setup_gh_action.sh and src/scripts/ci/gha_linux_packages.py on the main branch.
I confirmed that version-specific workarounds are no longer needed.

Current Status:
In applying the workaround, I noticed that the debian packages to be installed in src/scripts/ci/setup_gh_action.sh were updated with the notation (*). Then I analyzed the same script file on the master branch and noticed that the packages to be installed are now managed by src/scripts/ci/gha_linux_packages.py and no version is specified.

Conclusion:
Based on this analysis, I believe that this issue can be closed, as the problem is solved both in the use of CI and in the existing codebase (since there is no need to test it separately in CI).

Please let me know if I have missed any aspect or if there are specific concerns that still need to be addressed.

Best regards,

Clang CI recently started failing #3776

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions