Revert "Arm backend: Add correction for floor mode"

[ArmRyan]

Reverts #14776 due to flaky test results

Signed-off-by: Ryan O'Shea ryan.oshea3@arm.com

cc @freddan80 @per @zingo @oscarandersson8218 @digantdesai

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❌ 4 New Failures, 1 Cancelled Job, 3 Unrelated Failures

As of commit ec93b9a with merge base 3591604 ():

NEW FAILURES - The following jobs have failed:

• pull / test-qnn-wheel-packages-linux (3.10) / linux-job (gh)
  RuntimeError: Command docker exec -t 429b4c72dd60488a02dd39a0fde91808605ef91273ed5d08a419d2f3a8974fbd /exec failed with exit code 1
• pull / test-qnn-wheel-packages-linux (3.11) / linux-job (gh)
  RuntimeError: Command docker exec -t 9213c7e0cd0ffb2210c21bcb4b813eb004cc3d4571e21ac5a2f1cda9129731e2 /exec failed with exit code 1
• pull / test-qnn-wheel-packages-linux (3.12) / linux-job (gh)
  RuntimeError: Command docker exec -t 93b3148158bee8a190da0459f4d77b76ceeb10df660228197fd1ca07a0497201 /exec failed with exit code 1
• pull / unittest / macos / macos-job (gh)
  backends/xnnpack/test/ops/test_conv1d.py::TestConv1d::test_qs8_conv1d_batchnorm_seq

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

• trunk / test-models-macos-coreml (mv2) / macos-job (gh)

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / unittest / windows / windows-job (gh) (trunk failure)
  Process completed with exit code 1.
• pull / unittest-editable / windows / windows-job (gh) (trunk failure)
  Process completed with exit code 1.
• trunk / unittest-release / windows / windows-job (gh) (trunk failure)
  Process completed with exit code 1.

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

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.