[Sebastian-Larsson]

cc @digantdesai @freddan80 @per @zingo @oscarandersson8218 @mansnils @robell @rascani

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/19931

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 13 New Failures, 1 Cancelled Job, 1 Unrelated Failure, 1 Unclassified Failure

As of commit ae0a316 with merge base f512d7e ():

NEW FAILURES - The following jobs have failed:

• Apple / build-demo-ios / macos-job (gh)
  RuntimeError: Command bash /Users/runner/work/_temp/exec_script failed with exit code 65
• pull / android / build-android (gh)
• pull / test-arm-backend-no-driver (test_pytest_models_tosa) / linux-job (gh)
  RuntimeError: Command docker exec -t b84f034fc082a624d0f0b31959ec73a71e3d90a2746fc62bb107573f58cd5d47 /exec failed with exit code 1
• pull / test-arm-backend-no-driver (test_pytest_ops_no_target) / linux-job (gh)
  RuntimeError: Command docker exec -t a736f5d5a5e7e29f3ebb9c19a33e34a6145d1b74c0f6cd22ad80ef61ae308491 /exec failed with exit code 1
• pull / test-arm-backend-no-driver (test_pytest_ops_tosa) / linux-job (gh)
  RuntimeError: Command docker exec -t 1457614874e067479d96d9260636d99d56a6ec464671d22ea520f1960b27e1c9 /exec failed with exit code 1
• pull / test-arm-backend-no-driver (test_run_tosa) / linux-job (gh)
  RuntimeError: Command docker exec -t f731c41bc97ca42853e51f14d7de615bb521382351f3ab5695a53fd332cbca20 /exec failed with exit code 1
• pull / test-arm-cortex-m-size-test (bare_metal) / linux-job (gh)
  RuntimeError: Command docker exec -t 2a5577afedbf67b215847fbf5ea74a7ce2d5aeb95904c1d95882847081332727 /exec failed with exit code 1
• pull / test-arm-cortex-m-size-test (zephyr-preset) / linux-job (gh)
  RuntimeError: Command docker exec -t 244c0f368557e4a5d5665db2966dd6176c812897ab4087b1acec531532fe0a24 /exec failed with exit code 1
• pull / test-mcu-cortex-m-backend / linux-job (gh)
  RuntimeError: Command docker exec -t 7b6ed511b410ae5ac02eba25594072b913a27a8e21afe3a7857aa28d81c63951 /exec failed with exit code 1
• pull / test-samsung-models-linux / linux-job (gh)
  test_w2l_fp16
• pull / unittest / linux / linux-job (gh)
  RuntimeError: Command docker exec -t b736570564dc9a87416c9f39bba9b9d6840540a2f26a231da8596edf3c780608 /exec failed with exit code 1
• pull / unittest-editable / linux / linux-job (gh)
  RuntimeError: Command docker exec -t 41ffbda882a49b4630aa23f0a4f399f6c63fb2c40ca9a9e0ba659eda7c4b91e8 /exec failed with exit code 1
• pull / unittest-nxp-neutron / linux-job (gh)
  RuntimeError: Command docker exec -t 75f8af55b7342d724fe0442243f8a02ab1443c73367a713698188c541547f71f /exec failed with exit code 1

UNCLASSIFIED FAILURE - DrCI could not classify the following job because the workflow did not run on the merge base. The failure may be pre-existing on trunk or introduced by this PR:

• .github/workflows/trunk.yml (gh) (this job did not run on the merge base, so DrCI cannot tell whether the failure is pre-existing)

CANCELLED JOB - The following job was cancelled. Please retry:

• pull / test-qnn-python-imports-linux / linux-job (gh)
  ##[error]The operation was canceled.

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• pull / test-moshi-linux / linux-job (gh) (matched linux rule in flaky-rules.json)
  E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/m/mesa/mesa-vdpau-drivers_23.2.1-1ubuntu3.1%7e22.04.3_amd64.deb 404 Not Found [IP: 91.189.91.83 80]

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[zingo]

Hi @digantdesai this will probably help some buck2 merge problems we cause, is this OK?

[digantdesai]

This is the right direction, but I did it in a non-glob manner to make sure the new test doesn't start failing internally. Let me pull it inside and see what happens.

[meta-codesync]

@digantdesai has imported this pull request. If you are a Meta employee, you can view this in D107387455.

[digantdesai]

Many test failures, I need to take a closer look but the right direction is to fix internal tests, and land this, just that it may take some time. :|

[digantdesai]

@rascani FYI - we can discuss this more later.

[digantdesai]

Sorry this is still on us.

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

[Sebastian-Larsson]

@digantdesai any updates on this?

[Sebastian-Larsson]

@digantdesai now this closed as stale, are we not doing this?