Skip to content

Update ci.yml#61

Open
DrahtBot wants to merge 17 commits into
maflcko:mainfrom
DrahtBot:DrahtBot-patch-1
Open

Update ci.yml#61
DrahtBot wants to merge 17 commits into
maflcko:mainfrom
DrahtBot:DrahtBot-patch-1

Conversation

@DrahtBot

@DrahtBot DrahtBot commented Oct 31, 2025

Copy link
Copy Markdown
Collaborator

No description provided.

@DrahtBot

DrahtBot commented Oct 31, 2025

Copy link
Copy Markdown
Collaborator Author

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Reviews

See the guideline for information on the review process.

Type Reviewers
User requested bot ignore maflcko

If your review is incorrectly listed, please copy-paste <!--meta-tag:bot-skip--> into the comment that the bot should ignore.

Comment thread .github/workflows/ci.yml Outdated
fi

echo "test1" >> $GITHUB_STEP_SUMMARY
echo "test2" >> $GITHUB_STEP_SUMMARY

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the output text (

let text = r.output.text.as_deref().unwrap_or_default();
) is not populated by GHA, and the workaround via GITHUB_STEP_SUMMARY seems tedious, so I guess just downloading the full log and truncating it may be best.

Updated the step to print pull request number to use Python instead of shell script.
Change dummy task to exit with false instead of true.
@DrahtBot

DrahtBot commented Nov 5, 2025

Copy link
Copy Markdown
Collaborator Author

🚧 At least one of the CI tasks failed.
Task Dummy Task 1: https://github.com/maflcko/DrahtBot/actions/runs/19115117072/job/54622115972
LLM reason (✨ experimental): CTest reported errors during the test run, causing the CI to fail.

Hints

Try to run the tests locally, according to the documentation. However, a CI failure may still
happen due to a number of reasons, for example:

  • Possibly due to a silent merge conflict (the changes in this pull request being
    incompatible with the current code in the target branch). If so, make sure to rebase on the latest
    commit of the target branch.

  • A sanitizer issue, which can only be found by compiling with the sanitizer and running the
    affected test.

  • An intermittent issue.

Leave a comment here, if you need help tracking down a confusing failure.

@maflcko maflcko changed the title Update ci.yml Update ci.yml. Nov 18, 2025
@maflcko

maflcko commented Nov 25, 2025

Copy link
Copy Markdown
Owner

ACK

@maflcko

maflcko commented Nov 25, 2025

Copy link
Copy Markdown
Owner

No description provided.

@maflcko maflcko changed the title Update ci.yml. Update ci.yml World Jun 15, 2026
@maflcko maflcko changed the title Update ci.yml World Update ci.yml Jun 15, 2026
@DrahtBot DrahtBot changed the title Update ci.yml Update ci.yml Jun 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants