adoptium / adoptium/aqa-tests

dacapo-pmd perf benchmark fails to run on aarch64_windows

Open
#6,563 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
155
Forks
346
Avg merge
2d 9h
Merged PRs (30d)
36

Description

Found in Sept 2025 dry-run triage in https://github.com/adoptium/aqa-tests/issues/6555#issuecomment-3266284007, dacapo-pmd fails to pass on aarch64_windows. The previous version of test material (DaCapo 9.12-MR1) was running successfully on this platform but fails using 23.11-MR2-chopin-minimal test material.

dacapo_pmd failed, [deep history](https://trss.adoptium.net/deepHistory?testId=68bde3309598ec006ddc4344) shows it was passing on [5/22/2025](https://trss.adoptium.net/output/test?id=6835a85b3679cf006d50ec7c), but at that point, we were using DaCapo 9.12-MR1 materials. We have since updated to use DaCapo 23.11-MR2, https://github.com/adoptium/aqa-tests/issues/4858#issuecomment-2988946457, https://github.com/adoptium/aqa-tests/pull/6337 and not sure it was trialed against this platform during the testing. Will consider this failure as non-blocking, but open issue to investigate with this target excluded until root cause understood.
```
15:01:40 PMD checked 601 files.
15:01:40 Digest validation failed for pmd-report.txt, expecting 0x9ac4266f6d867118bf6365f3c935b97526705c2c found 0xf7fb29acd687098cb9646d419c36d553144b414b
15:01:40 ===== DaCapo 23.11-MR2-chopin-minimal pmd FAILED =====
15:01:40 Validation FAILED for pmd default
15:01:40 -----------------------------------
15:01:40 dacapo-pmd_0_FAILED
```

Until this can be properly investigated and resolved, exclude this target on aarch64_windows.

Contributor guide

Open the contributing guide

Research direction

Start with the linked deep history and test output to compare the passing DaCapo 9.12-MR1 run with the failing 23.11-MR2-chopin-minimal run on aarch64_windows. Investigate the pmd-report.txt digest mismatch and the material change, then verify the target can run successfully before removing its exclusion.

Written by the indexing model from the issue text.

Assessment

Domain
testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.