Skip to content

[engine] fuchsia builders failing with infra failure 6% of the time #54256

Description

@godofredoc

The paving process is failing and the device remains in zedboot mode. The builder times out because it expects the device on fuchsia to continue.

2020-04-08 04:36:04 [bootserver.exe.linux-x64] Received request from [fe80::d65d:df4d:fe1a:4333]:33330
2020-04-08 04:36:04 [bootserver.exe.linux-x64] Proceeding with nodename siren-relic-wick-poppy
2020-04-08 04:36:04 [bootserver.exe.linux-x64] Transfer starts
100%...
5%... 10%... 15%... 20%... 25%... 30%... 35%... 40%... 45%... 50%... 55%... 60%... 65%... 70%... 75%... 80%... 85%... 90%...
bootserver.exe.linux-x64: too many consecutive timeouts, aborting (status = -21)

Dumping system logs...
Unhandled exception:
Failed to get target IP for siren-relic-wick-poppy
#0 DevFinder._runDevFinderWithRetries (package:fuchsia_ctl/src/dev_finder.dart:65)
#1 _RootZone.runUnary (dart:async/zone.dart:1381)
#2 _FutureListener.handleValue (dart:async/future_impl.dart:139)
#3 Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:680)
#4 Future._propagateToListeners (dart:async/future_impl.dart:709)
#5 Future._complete (dart:async/future_impl.dart:514)
#6 new Future.delayed. (dart:async/future.dart:313)
#7 Timer._createTimer. (dart:async-patch/timer_patch.dart:23)
#8 _Timer._runTimers (dart:isolate-patch/timer_impl.dart:384)
#9 _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:418)
#10 _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:174)

Activity

  1. self-assigned this
    on Apr 8, 2020
  2. godofredoc commented on Apr 18, 2020

    @godofredoc
    ContributorAuthor

    The paving process is failing due to many paving processes running at the same time. There have been many fixes for this in the bootserver but we'll need to add retries to the paving process.

  3. added a commit that references this issue on Apr 19, 2020
  4. lock commented on May 6, 2020

    @lock

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  5. locked and limited conversation to collaborators on May 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

team-infraOwned by Infrastructure team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions