Skip to content

Conversation

@nate-thegrate
Copy link
Contributor

@nate-thegrate nate-thegrate commented Jul 25, 2024

Problem

For someone who isn't familiar with the LUCI website interface, trying to figure out why a check failed can be painful.

04:27 +10201 ~25 -10: C:/b/s/w/ir/x/w/flutter/packages/flutter/test/services/undo_manager_test.dart: Undo Interactions UndoManagerClient handleUndo
04:27 +10202 ~25 -10: C:/b/s/w/ir/x/w/flutter/packages/flutter/test/services/undo_manager_test.dart: Undo Interactions UndoManagerClient handleUndo
04:27 +10203 ~25 -10: C:/b/s/w/ir/x/w/flutter/packages/flutter/test/services/undo_manager_test.dart: Undo Interactions UndoManagerClient handleUndo
04:27 +10204 ~25 -10: C:/b/s/w/ir/x/w/flutter/packages/flutter/test/services/undo_manager_test.dart: Undo Interactions UndoManagerClient handleUndo
04:27 +10205 ~25 -10: C:/b/s/w/ir/x/w/flutter/packages/flutter/test/services/use_platform_channel_without_initialization_test.dart: throws assertion error iff WidgetsFlutterBinding is not yet initialized
04:27 +10206 ~25 -10: Some tests failed.
���ERROR #2���������������������������������������������������������������������
� Command: ..\..\bin\flutter.bat test --reporter=expanded --file-reporter=json:C:\b\s\w\ir\x\t\metrics_1722536319566442.json --test-randomize-ordering-seed=20240801 --fatal-warnings --no-track-widget-creation test\animation\ test\cupertino\ test\dart\ test\examples\ test\foundation\ test\gestures\ test\harness\ test\material\ test\painting\ test\physics\ test\rendering\ test\scheduler\ test\semantics\ test\services\
� Command exited with exit code 1 but expected zero exit code.
� Working directory: C:\b\s\w\ir\x\w\flutter\packages\flutter
��������������������������������������������������������������������������������
�11:23:19� Test failed.
��������������������������������������������������������
For your convenience, the error messages reported above are repeated here:
  �  �  
Command: ..\..\bin\flutter.bat test --reporter=expanded --file-reporter=json:C:\b\s\w\ir\x\t\metrics_1722536032214085.json --test-randomize-ordering-seed=20240801 --fatal-warnings --track-widget-creation test\animation\ test\cupertino\ test\dart\ test\examples\ test\foundation\ test\gestures\ test\harness\ test\material\ test\painting\ test\physics\ test\rendering\ test\scheduler\ test\semantics\ test\services\
Command exited with exit code 1 but expected zero exit code.
Working directory: C:\b\s\w\ir\x\w\flutter\packages\flutter
  �  �  
Command: ..\..\bin\flutter.bat test --reporter=expanded --file-reporter=json:C:\b\s\w\ir\x\t\metrics_1722536319566442.json --test-randomize-ordering-seed=20240801 --fatal-warnings --no-track-widget-creation test\animation\ test\cupertino\ test\dart\ test\examples\ test\foundation\ test\gestures\ test\harness\ test\material\ test\painting\ test\physics\ test\rendering\ test\scheduler\ test\semantics\ test\services\
Command exited with exit code 1 but expected zero exit code.
Working directory: C:\b\s\w\ir\x\w\flutter\packages\flutter
��������������������������������������������������������
You may find the errors by searching for "�ERROR #" in the logs.

Solution

This PR adds a wiki page that new contributors can reference when debugging CI/CD check failures.

View in Markdown format


(click to see images used)

some_checks_were_not_successful

tree_is_currently_broken

google_testing

view_more_details_button

luci_overview

click_to_run_tests

update_with_rebase

past builds

ci.yaml validation

@github-actions github-actions bot added c: contributor-productivity Team-specific productivity, code health, technical debt. framework flutter/packages/flutter repository. See also f: labels. d: docs/ flutter/flutter/docs, for contributors labels Jul 25, 2024
@nate-thegrate nate-thegrate marked this pull request as ready for review July 25, 2024 23:30
@christopherfujino
Copy link
Contributor

We have this: https://github.com/flutter/flutter/blob/master/docs/infra/Understanding-a-LUCI-build-failure.md#overview-of-an-infra-failure-build

If you have suggestions from improvements I would happily review a PR :)

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

Labels

c: contributor-productivity Team-specific productivity, code health, technical debt. d: docs/ flutter/flutter/docs, for contributors framework flutter/packages/flutter repository. See also f: labels.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants