Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert "ci: Tune network" #495

Merged
merged 1 commit into from
Mar 1, 2024
Merged

Revert "ci: Tune network" #495

merged 1 commit into from
Mar 1, 2024

Conversation

tienvx
Copy link
Contributor

@tienvx tienvx commented Feb 29, 2024

Reverts #488

@tienvx tienvx mentioned this pull request Feb 29, 2024
@Lewiscowles1986
Copy link
Collaborator

Hmm, maybe the continued failures are something else. But the flakes are a lot. @YOU54F does PACT have any resources to look into this?

@tienvx tienvx merged commit fae219a into ffi Mar 1, 2024
41 of 59 checks passed
@tienvx tienvx deleted the revert-488-tune-network branch March 1, 2024 00:10
@YOU54F
Copy link
Member

YOU54F commented Mar 1, 2024

Hey hey,

I had noted issues on a personal project with pact-php on macos-12 and 14 due to some core libs being rebuilt and most of the formula on homebrew using shared libs, rather than static builds.

With regards to specific resources, I'm not sure what we can do maybe getting a list of all the CI snags, in a central place and we can work through them. I appreciate it is a thankless task then things are relatively stable and then just start borking outside of our control (GH images go through some fair flux, and we pull dependencies that do get rebuilt. Maybe trying to limit some of the variables that change in a run (docker containers for linux, pinned by commit hash actions)

does PACT have any resources to look into this?

What are you thinking you might need and I'll see what I can sort!

@YOU54F
Copy link
Member

YOU54F commented Mar 1, 2024

I am finding logs too verbose to be useful then things are going wrong, so tuning that would certainly help scroll daze. I can't do greps for failures/errors as debug/trace are full of them on successful runs :(

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.

3 participants