Closed Bug 802475 Opened 13 years ago Closed 13 years ago

Intermittent "talosError: Unable to proceed with missing counter 'tp5n_xres'"

Categories

(Testing :: Talos, defect)

Product:
Testing
Component:
Talos
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

remove xres from talos (1.0)
3.88 KB, patch
Details | Diff | Splinter Review
+++ This bug was initially created as a clone of Bug #802289 +++ https://tbpl.mozilla.org/php/getParsedLog.php?id=16181263&tree=Firefox Rev3 Fedora 12 mozilla-central talos tpn on 2012-10-16 19:46:21 PDT for push dac5700acf8b slave: talos-r3-fed-019 No results collected for: tp5n_xres: Error Tue, 16 Oct 2012 20:16:42 Traceback (most recent call last): File "run_tests.py", line 303, in <module> FAIL: Unable to proceed with missing counter 'tp5n_xres' main() File "run_tests.py", line 300, in main run_tests(parser) File "run_tests.py", line 276, in run_tests talos_results.output(results_urls, **results_options) File "/home/cltbld/talos-slave/talos-data/talos/results.py", line 89, in output raise e utils.talosError: "Unable to proceed with missing counter 'tp5n_xres'"
copy-paste is *hard*
OS: Windows 7 → Linux
Summary: utils.talosError: "Unable to proceed with missing counter 'tp5n_xres'"Intermittent → Intermittent utils.talosError: "Unable to proceed with missing counter 'tp5n_xres'"
I see 16 instances of this in the Firefox graph for the last 30 days: http://graphs.mozilla.org/graph.html#tests=[[211,131,15]]&sel=none&displayrange=30&datatype=running Between the different branches and configurations, I expect we will hit this error a lot. 1) do we care about xres numbers? 2) have we ever backed out a patch based on xres numbers? 3) if we do care about them, what is our policy for when we don't collect? Looking in some logs and the talos code, we run xrestop and I don't see mention of it failing in the logfiles.
if we decide we don't care about xres, here is a patch to remove it.
(Bug 794895 will make this failure mode display in the annotated summary)
Depends on: 794895
Summary: Intermittent utils.talosError: "Unable to proceed with missing counter 'tp5n_xres'" → Intermittent "talosError: Unable to proceed with missing counter 'tp5n_xres'"
https://tbpl.mozilla.org/php/getParsedLog.php?id=16413567&tree=Firefox So, what will the solution to this look like? What will additional debugging look like?
could it be that we have machine that don't have xrestop? I need to build a patch that outputs where xrestop is and the version in all the log files.
It'd probably be quicker to look at https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=802475&entireHistory=true&tree=all to see the distribution (only three slaves have even hit it more than once), then pick one and look at https://secure.pub.build.mozilla.org/buildapi/recent/talos-r3-fed-053?numbuilds=800 with tpn in the search box to see that a slave that has hit it three times has also done a bunch of green runs.
Whiteboard: [orange]
Resolving WFM keyword:intermittent-failure bugs last modified >3 months ago, whose whiteboard contains none of: {random,disabled,marked,fuzzy,todo,fails,failing,annotated,time-bomb,leave open} There will inevitably be some false positives; for that (and the bugspam) I apologise. Filter on orangewfm.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: