Page MenuHomePhabricator

Add an indicator to the test table for passing runs that are particularly slow
Closed, ResolvedPublic

Description

To help people identify implementations or test cases that are slower than the others, maybe we should add an icon warning about it, with some explanatory title text or perhaps a link to a page to give advice on how to tune implementations?

If we're doing this, we'd need to decide what conditions warranted being warned about slowness? Slower by more than X% compared to the 'best' one? Slower by X& compared to the average? Slower than some fixed time (e.g. 1 second)?

There's no obvious candidate in https://doc.wikimedia.org/codex/latest/icons/all-icons.html but a quick literature review shows icons demonstrating slowness are generally either turtles or tachometers with the arrow over to the left, which might be suitable?

Details

Related Changes in GitLab:
TitleReferenceAuthorSource BranchDest Branch
warnings: Raise them when a call approaches its resource limitsrepos/abstract-wiki/wikifunctions/function-orchestrator!785jforresterT427112-2main
Customize query in GitLab

Event Timeline

Jdforrester-WMF changed the task status from Open to In Progress.Aug 14 2026, 7:06 PM
Jdforrester-WMF claimed this task.

Yeah, this will be in-effect done by the orchestrator warning about speed, good call.

Was the code which raises those new Error types deployed yet? I've only been seeing Z592/size warning and Z582/Wasm fuel limit. For example with factor 10^26 - 1 (whereas factor 10^25 - 1 succeeds with no warnings). edit: Of course I found one the next day...