| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
We had been doing this manually, and this will be a lot more convenient.
|
|
[petrhosek](https://github.com/petrhosek) commented on this PR went in
https://github.com/llvm/llvm-project/pull/172673#issuecomment-3740109442
that the ids check workflow has a syntax error in it. After looking at
the workflow, it appears to be missing - on the uses lines. After this
change and having looked at the file in Githubs file editor, no syntax
error red lines are now appearing so this should fix it.
|
|
LLVM_ABI (#172673)
This PR adds a workflow which checks that llvm apis have been annotated
with LLVM_ABI.
Co-authored-by: mcbarton <matthew.c.barton@hotmail.co.uk>
|
|
This is needed to properly test that #172673 is working as expected.
|
|
|
|
(#173441)
Sub-project tarbball creation has been disabled in the export.sh script
by default. It can be enabled by passing the --sub-project option. This
will not be used for official releases, but the option will allow users
to generate the sub-project tarballs themseleves if they want to.
https://discourse.llvm.org/t/rfc-do-something-with-the-subproject-tarballs-in-the-release-page/75024/
---------
Co-authored-by: Cullen Rhodes <cullen.rhodes@arm.com>
|
|
A new runner just came out. Nothing terribly interesting in the release
notes, but it is good to update to stay ahead of the relatively short
time horizon for runner binary support by Github Actions.
|
|
Add flang-rt to the autolabel github yaml.
|
|
This reverts commit 20d0ec849804218d75647aeafbe23f8a02a83b56.
The publish-sphinx-docs buildbot still uses LLVM_ENABLE_PROJECTS=openmp.
|
|
The build mode has been deprecated in #136314. According to the
deprecation message, it was supposed to be removed in the LLVM 21
release. Each build mode increased the maintanance overhead when
failing, such as in #151117.
Let's remove it in LLVM 22.
|
|
Windows x86 binaries will now be built and uploaded automatically when a new release is tagged.
|
|
Right now, some paths for `mlir:python` are missing, which means
relevant people don’t always get notified. This PR adds those paths.
|
|
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
|
[EnricoMi/publish-unit-test-result-action](https://redirect.github.com/EnricoMi/publish-unit-test-result-action)
| action | minor | `v2.21.0` → `v2.22.0` |
|
[actions/attest-build-provenance](https://redirect.github.com/actions/attest-build-provenance)
| action | minor | `v3.0.0` → `v3.1.0` |
| ghcr.io/llvm/ci-ubuntu-24.04-abi-tests | container | digest |
`9138b6a` → `ef869c1` |
|
[github/codeql-action](https://redirect.github.com/github/codeql-action)
| action | patch | `v4.31.6` → `v4.31.9` |
| llvm/actions | action | digest | `5dd9550` → `89a8cf8` |
|
[tj-actions/changed-files](https://redirect.github.com/tj-actions/changed-files)
| action | patch | `v47.0.0` → `v47.0.1` |
|
|
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
|
[actions/download-artifact](https://redirect.github.com/actions/download-artifact)
| action | major | `v6.0.0` → `v7.0.0` |
|
[actions/upload-artifact](https://redirect.github.com/actions/upload-artifact)
| action | major | `v5.0.0` → `v6.0.0` |
|
[actions/upload-artifact](https://redirect.github.com/actions/upload-artifact)
| action | major | `5.0.0` → `6.0.0` |
|
|
|
|
Previously we added `doc8` to `code-lint` workflow. However, PRs contain
only documentation changes won't trigger this workflow.
An example: https://github.com/llvm/llvm-project/pull/173699/checks
didn't trigger `code-lint`.
This commit fixes the issue.
|
|
This workflow never actually tested changes to the issue write workflow
because changes to issue-write.yml need to be committed to main before
they do anything.
|
|
Closes #167098
---------
Co-authored-by: EugeneZelenko <eugene.zelenko@gmail.com>
Co-authored-by: Baranov Victor <bar.victor.2002@gmail.com>
|
|
We experimented with using this to help curate release notes for the
stable releases, but it has not worked out.
|
|
Dropping -g1 should improve the debuginfo and hopefully make the abi
tests more accurate. I think -g1 was originally used to save disk space,
but the GitHub runners have more disk space now, so it isn't necessary.
The abi-compliance checker recommends using -Og, but it seems not to
make a difference and it's more simple just to not specify any extra
flags.
|
|
Just to keep things up to date. It does not look like we can yet jump to
VS 2026 despite it being available since the vs_buildtools.exe link does
not work with VS v18 (which corresponds to Visual Studio 2026).
I've tested this locally running the full premerge pipeline and
everything checks out.
|
|
This is primarily intended to upgrade past python 3.9 so that we can
continue building MLIR after
https://discourse.llvm.org/t/rfc-adopt-regularly-scheduled-python-minimum-version-bumps/88841/9
lands. This also makes us consistent with the Linux container.
I tested this locally by building the container with this change applied
and running the entire premerge pipeline within the freshly built
container.
|
|
This function was deprecated recently. Update to the auth parameter to
get ahead of the deprecation.
|
|
This package is available in Ubuntu now, so we don't need to build it
manually.
|
|
artifact (#171525)
This will simplify the process of verifying the assets, because the
attestation file for $file will be $file.jsonl. Otherwise, it's not
clear which attestation file goes with which asset.
|
|
Daniel Grumberg is no longer a maintainer for Clang ExtractAPI. I have
updated the code owners list accordingly and added myself in his stead.
|
|
This moves us back to the main runner set so that the next runner set
can be used for upgrading again when we want to do that. This also
captures the Github Runner version upgrade.
|
|
To start using the more recently built containers.
|
|
|
|
upgrade macOS version to latest stable version in github action. We run
into a problem that timed `os_sync` API only becomes available in 14.4+.
|
|
platform.machine() on x86_64 on Windows returns AMD64 rather than
x86_64. Make premerge.yaml reflect this.
|
|
This PR contains the following updates:
| Package | Type | Update | Change | Pending |
|---|---|---|---|---|
| [actions/checkout](https://redirect.github.com/actions/checkout) |
action | patch | `v6.0.0` -> `v6.0.1` | |
| [actions/setup-node](https://redirect.github.com/actions/setup-node) |
action | minor | `v6.0.0` -> `v6.1.0` | |
|
[github/codeql-action](https://redirect.github.com/github/codeql-action)
| action | patch | `v4.31.5` -> `v4.31.6` | `v4.31.7` |
|
|
(#170528)
|
|
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [actions/checkout](https://redirect.github.com/actions/checkout) |
action | major | `v5.0.0` -> `v6.0.1` |
|
|
|
|
|
|
https://discourse.llvm.org/t/rfc-display-true-result-for-aarch64-pre-commit-ci/88928
|
|
We need to cat all files that start with comments now that premerge
writes out files containing comments without that exact name.
|
|
Now that the issue-write workflow can support writing comments from
multiple files, make the premerge workflow write out comments from both
x86_64 Linux and Windows. AArch64 Linux right now is left out as the
premerge advisor does not currently support it.
|
|
This is so that we can read from multiple files emitted by the premerge
workflow.
Reviewers: tstellar, cmtice
Reviewed By: cmtice
Pull Request: https://github.com/llvm/llvm-project/pull/170411
|
|
This changed the name of one of the outputs that issue-write used to
control whether or not it ran. This patch should fix that.
|
|
We should actually run the test workflow when touching the workflow we
are attempting to test.
|
|
This is designed to allow a workflow (e.g., premerge) upload comments
across multiple jobs. Subsequent PRs will wire this up within the
issue-write workflow to support reading comments from multiple files.
Reviewers: tstellar, cmtice
Reviewed By: cmtice
Pull Request: https://github.com/llvm/llvm-project/pull/170216
|
|
This does not test most of the functionality (i.e., that writing to an
existing comment still works), but does ensure that the plumbing works
and things are not completely broken.
Reviewers: tstellar, cmtice
Reviewed By: cmtice
Pull Request: https://github.com/llvm/llvm-project/pull/170209
|
|
So that we can actually test the workflow before comitting into tree.
|
|
action (#169621)
Also, switch the release-sources workflow over to use this new action.
As a result of this change, the attestation file for the sources will be
renamed from attestation.jsonl to $TAG-sources-attestation.jsonl.
|
|
(#166875)
Previously, the bootstrapping-build job defined in run-buildbot required
the CC and CXX environment variables to be defined even though
run-buildbot documents these environment variables as being optional. It
also relied on ccache being available.
Refactor run-buildbot to make CC and CXX mandatory, and refactor various
places in the CI where we called run-buildbot without setting CC and
CXX. After this patch, all places that use run-buildbot are setting CC
and CXX before calling the script, which makes it easier to track what
compiler is used where. This also allows simplifying run-buildbot
itself.
Finally, this patch makes ccache optional for running the bootstrapping
build.
|
|
s/Chekcout/Checkout
|
|
This PR contains the following updates:
| Package | Type | Update | Change | Pending |
|---|---|---|---|---|
|
[actions/setup-python](https://redirect.github.com/actions/setup-python)
| action | minor | `v6.0.0` -> `v6.1.0` | |
|
[github/codeql-action](https://redirect.github.com/github/codeql-action)
| action | patch | `v4.31.4` -> `v4.31.5` | `v4.31.6` |
|
[hendrikmuhs/ccache-action](https://redirect.github.com/hendrikmuhs/ccache-action)
| action | patch | `v1.2.19` -> `v1.2.20` | |
|
|
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
|
[actions/upload-artifact](https://redirect.github.com/actions/upload-artifact)
| action | major | `v4.6.2` -> `v5.0.0` |
|
