Open Bug 1936263 Opened 3 months ago Updated 7 days ago

Sequential runs of mach gradle unit tests should report the same output

Categories

(Fenix :: Tooling, defect)

All
Android
defect

Tracking

(Not tracked)

People

(Reporter: gerard-majax, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

While investigating bug 1936262, I finally found the correct invocation to see the warnings: ./mach gradle lib-crash:testDebugUnitTest --tests mozilla.components.lib.crash.CrashReporterTest.

Unfortunately, running that twice in a row result in the second run not showing any warning. It looks like touching / changing the test file and re-running is enough to get results again, as if it was cached somehow.

The severity field is not set for this bug.
:007, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(nbond)
Severity: -- → S3
Flags: needinfo?(nbond)
Severity: S3 → S2

gradle seems to cache results and not re-run the previous task. I noticed something similar in bug 1950158.

Does adding --rerun address your issue? It is documented at https://docs.gradle.org/current/userguide/command_line_interface.html#sec:builtin_task_options

See Also: → 1950158
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: