chore: re-comment transiently failing component tests#10095
Merged
paulbalandan merged 1 commit intocodeigniter4:developfrom Apr 10, 2026
Merged
chore: re-comment transiently failing component tests#10095paulbalandan merged 1 commit intocodeigniter4:developfrom
paulbalandan merged 1 commit intocodeigniter4:developfrom
Conversation
paulbalandan
force-pushed
the
random-order-test-fail
branch
from
0bf2a5e to
378e514
Compare
Member
|
I'm unable to reproduce this issue locally on my side. |
Member
Author
|
No, it seems to be an issue only on GitHub Actions. |
michalsn
approved these changes
Apr 10, 2026
Member
michalsn
left a comment
michalsn
left a comment
There was a problem hiding this comment.
Okay, let’s see if this resolves it or if the tests fail elsewhere.
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
2 participants
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.
Description
I have no luck in #10092 debugging where to fix the
Class "CodeIgniter\CodeIgniter" not founderrors. Maybe worthwhile to just comment out those failing tests for now until we have some new leads.Checklist: