Skip to content

Fix CI#3752

Merged
addisoncrump merged 21 commits intomainfrom
fix-ci-again
Apr 2, 2026
Merged

Fix CI#3752
addisoncrump merged 21 commits intomainfrom
fix-ci-again

Conversation

@addisoncrump
Copy link
Copy Markdown
Member

me and the boys up at 1630 fixing CI

@domenukk
Copy link
Copy Markdown
Member

Yesss <3

@addisoncrump
Copy link
Copy Markdown
Member Author

Remaining issues are either associated with the known event manager bug (cc @rmalmain) or with the passes needing to be updated (cc @tokatoka). This PR is as good as I can make it for now.

Copy link
Copy Markdown
Member

@rmalmain rmalmain left a comment

Choose a reason for hiding this comment

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

looks ok to me.
@addisoncrump i've pushed a .gitattribute file to your branch (it just ignores Cargo.lock for diffs and stats, cf https://docs.github.com/en/repositories/working-with-files/managing-files/customizing-how-changed-files-appear-on-github). you will need to pull.

sudo apt-get install -y \
curl lsb-release wget software-properties-common gnupg shellcheck pax-utils \
libsqlite3-dev libpixman-1-dev libc6-dev gcc g++ build-essential libglib2.0-dev
echo "export LLVM_CONFIG_PATH=$(which llvm-config-21)" | sudo tee -a /etc/environment
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

cannot we use a central value for llvm version? (like reusing MAIN_LLVM_VERSION or similar)
otherwise we'll need to hunt for 21 later on when we need to update again.
I think we can define CI variables for this kind of stuff.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Probably wise. I'll go ahead and exchange this now.

@addisoncrump
Copy link
Copy Markdown
Member Author

Note to self: CI breaks on April 1st.

@riesentoaster
Copy link
Copy Markdown
Contributor

Note to self: CI breaks on April 1st.

Fixed here (I hope): #3778

@addisoncrump
Copy link
Copy Markdown
Member Author

wtf github, default branch update should be rebase

* Allow force disabling pizza mode regardless of the date

* Disable pizza mode in CI

* fixup remaining bits

---------

Co-authored-by: Addison Crump <addison.crump@cispa.de>
@addisoncrump addisoncrump merged commit e98b4f3 into main Apr 2, 2026
91 of 101 checks passed
@addisoncrump addisoncrump deleted the fix-ci-again branch April 2, 2026 11:54
@mannubaveja007
Copy link
Copy Markdown
Contributor

Finally Merged!

workflow_dispatch:
merge_group:
env:
AFL_PIZZA_MODE: "-1" # this is sad, I know, but it breaks on a certain spring day otherwise :(
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

It should be 0 to map to how AFL++ uses it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants