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.

Sign up for GitHub

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

Jump to bottom

target-arm64-vm-linux-release-be buildbot multiple failures #33659

Closed
aam opened this issue Jun 27, 2018 · 8 comments
Closed

target-arm64-vm-linux-release-be buildbot multiple failures #33659

aam opened this issue Jun 27, 2018 · 8 comments
Assignees
@aam
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. gardening

Comments

@aam
Copy link
Contributor

aam commented Jun 27, 2018

target-arm64-vm-linux-release-be buildbot started to fail with Snapshot not compatible with the current VM configuration: the snapshot requires 'release no-strong no-type_checks no-asserts no-error_on_bad_type no-error_on_bad_override no-sync_async no-reify_generic_functio' but the VM has 'release no-strong no-type_checks no-asserts no-error_on_bad_type no-error_on_bad_override no-sync_async no-reify_generic_functions use_field_guards use_osr arm64' Error while initializing Kernel isolate since https://ci.chromium.org/buildbot/client.dart/target-arm64-vm-linux-release-be/6210.

https://dart-review.googlesource.com/61521 is likely culprit since https://ci.chromium.org/buildbot/client.dart/target-arm64-vm-linux-release-be/6243 that landed revert of that fixed that snapshot incompatible problem.

And it broke again in https://ci.chromium.org/buildbot/client.dart/target-arm64-vm-linux-release-be/6253 that has https://dart-review.googlesource.com/62201.

cc @whesse @zanderso
@aam aam added the gardening label Jun 27, 2018
@zanderso zanderso added the area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. label Jun 27, 2018
@aam
Copy link
Contributor Author

aam commented Jun 27, 2018

The path forward would be to enhance cross-arm64 testing, build full arm64 sdk and use that instead of what is being used now.

dart-bot pushed a commit that referenced this issue Jun 28, 2018
@athomas
[infra] Download checked in SDKs from CIPD
66c9109 
#33659

Change-Id: I94fccf4bbce2f0140bf0d6efa953d44b290df856
Reviewed-on: https://dart-review.googlesource.com/62840
Commit-Queue: Alexander Thomas <athom@google.com>
Reviewed-by: William Hesse <whesse@google.com>
Reviewed-by: Zach Anderson <zra@google.com>
@athomas athomas assigned aam and unassigned whesse Jun 28, 2018
@athomas athomas added area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. and removed area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. labels Jun 28, 2018
@athomas
Copy link
Member

athomas commented Jun 28, 2018

We use an arm64 SDK on that bot since 72b77ac. Re-assigning to VM.

@athomas
Copy link
Member

athomas commented Jun 28, 2018

The bot is still going to be red, but I suspect that is for a different reason: https://logs.chromium.org/v/?s=chromium%2Fbb%2Fclient.dart%2Ftarget-arm64-vm-linux-release-be%2F6359%2F%2B%2Frecipes%2Fsteps%2Fvm_tests%2F0%2Fstdout

@athomas
Copy link
Member

athomas commented Jun 28, 2018

Also note that this pair of builders was converted to Dart2 (requested by @mraleph).

@aam
Copy link
Contributor Author

aam commented Jun 29, 2018

Also note that this pair of builders was converted to Dart2

Do you mean that arm64 tests used to run in dart1 mode, now are running in dart2 mode? Or something else?

@aam aam changed the title target-arm64-vm-linux-release-be buildbot fails 'Snapshot not compatible with the current VM configuration' target-arm64-vm-linux-release-be buildbot multiple failures Jun 29, 2018
@athomas
Copy link
Member

athomas commented Jul 2, 2018

@aam mostly resolved this last week. The builder just has a handful of failing tests now, which can probably be dealt with a status update.

@aam
Copy link
Contributor Author

aam commented Jul 3, 2018

https://dart-review.googlesource.com/c/sdk/+/63444 with few more status file changes

@aam
Copy link
Contributor Author

aam commented Jul 18, 2018

buildbot is green now

@aam aam closed this as completed Jul 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aam aam

Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. gardening
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@aam @whesse @zanderso @athomas