[Merged by Bors] - chore: upload artifact for debugging no-build failures - #28062
Closed
bryangingechen wants to merge 1 commit into
Closed
[Merged by Bors] - chore: upload artifact for debugging no-build failures#28062bryangingechen wants to merge 1 commit into
bryangingechen wants to merge 1 commit into
Conversation
PR summary d79083011bImport changes for modified filesNo significant changes to the import graph Import changes for all files
Declarations diffNo declarations were harmed in the making of this PR! 🐙 You can run this locally as follows## summary with just the declaration names:
./scripts/declarations_diff.sh <optional_commit>
## more verbose report:
./scripts/declarations_diff.sh long <optional_commit>The doc-module for No changes to technical debt.You can run this locally as
|
Contributor
|
bors merge |
mathlib-bors Bot
pushed a commit
that referenced
this pull request
Aug 7, 2025
Since the `lake build --no-build` failures in the "Post-Build Step" job are still occurring (cf. [#mathlib4 > Failing CI @ 💬](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Failing.20CI/near/533022248)), we upload the contents of the `pr-branch` directory as a workflow artifact, to help with figuring out what's going on.
Contributor
|
Pull request successfully merged into master. Build succeeded: |
mathlib-bors Bot
pushed a commit
that referenced
this pull request
Aug 7, 2025
Follow-up to #28062. It turns out `.olean` files are stored in `.lake` which are excluded by default by the `actions/upload-artifact` action. We use the `include-hidden-files` option, taking care to exclude the `.git` folder which may include secrets like `GITHUB_TOKEN`, etc.
staroperator
pushed a commit
to staroperator/mathlib4
that referenced
this pull request
Aug 8, 2025
…mmunity#28062) Since the `lake build --no-build` failures in the "Post-Build Step" job are still occurring (cf. [#mathlib4 > Failing CI @ 💬](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Failing.20CI/near/533022248)), we upload the contents of the `pr-branch` directory as a workflow artifact, to help with figuring out what's going on.
staroperator
pushed a commit
to staroperator/mathlib4
that referenced
this pull request
Aug 8, 2025
Follow-up to leanprover-community#28062. It turns out `.olean` files are stored in `.lake` which are excluded by default by the `actions/upload-artifact` action. We use the `include-hidden-files` option, taking care to exclude the `.git` folder which may include secrets like `GITHUB_TOKEN`, etc.
Paul-Lez
pushed a commit
to Paul-Lez/mathlib4
that referenced
this pull request
Aug 23, 2025
…mmunity#28062) Since the `lake build --no-build` failures in the "Post-Build Step" job are still occurring (cf. [#mathlib4 > Failing CI @ 💬](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Failing.20CI/near/533022248)), we upload the contents of the `pr-branch` directory as a workflow artifact, to help with figuring out what's going on.
Paul-Lez
pushed a commit
to Paul-Lez/mathlib4
that referenced
this pull request
Aug 23, 2025
Follow-up to leanprover-community#28062. It turns out `.olean` files are stored in `.lake` which are excluded by default by the `actions/upload-artifact` action. We use the `include-hidden-files` option, taking care to exclude the `.git` folder which may include secrets like `GITHUB_TOKEN`, etc.
Paul-Lez
pushed a commit
to Paul-Lez/mathlib4
that referenced
this pull request
Aug 23, 2025
…mmunity#28062) Since the `lake build --no-build` failures in the "Post-Build Step" job are still occurring (cf. [#mathlib4 > Failing CI @ 💬](https://leanprover.zulipchat.com/#narrow/channel/287929-mathlib4/topic/Failing.20CI/near/533022248)), we upload the contents of the `pr-branch` directory as a workflow artifact, to help with figuring out what's going on.
Paul-Lez
pushed a commit
to Paul-Lez/mathlib4
that referenced
this pull request
Aug 23, 2025
Follow-up to leanprover-community#28062. It turns out `.olean` files are stored in `.lake` which are excluded by default by the `actions/upload-artifact` action. We use the `include-hidden-files` option, taking care to exclude the `.git` folder which may include secrets like `GITHUB_TOKEN`, etc.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since the
lake build --no-buildfailures in the "Post-Build Step" job are still occurring (cf. #mathlib4 > Failing CI @ 💬), we upload the contents of thepr-branchdirectory as a workflow artifact, to help with figuring out what's going on.