Closed Bug 1476290 Opened 6 years ago Closed 6 years ago

Raptor's 2nd run fails locally

Categories

(Testing :: Raptor, defect)

Product:
Testing
Component:
Raptor
Platform:
Unspecified
Windows 10
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: igoldan, Unassigned)

References

Details

Raptor benchmark tests fail to run when you run the command the 2nd time, on latest mozilla-inbound, which for me is 9a7bf0017c6c. I tested this against speedometer mostly. But it reproduces for stylebench as well.

After the "* pausing 30 seconds to let browser settle... *" log line, I get this error:

INFO -  PID 15468 | JavaScript error: undefined, line 0: Error: An unexpected error occurred


ae04f1ff217f  is the commit that doesn't reproduce the issue. It's from July 9.
The speedometer command I've used is |mach raptor-test -t raptor-speedometer-firefox|.
I can't reproduce this on OSX with latest inbound. Running ./mach raptor-test -t raptor-speedometer, then let it finish, then run the same command again and the test runs fine again and finishes successfully.

Must be something platform specific.
I was not able to reproduce this locally on win10 with the latest mozilla-inbound (rev:9a7bf0017c6c)  The only change I had locally was running 1 cycle to improve end to end time.
:igoldan, is this still happening? If not, please close this bug out. Thanks :)
Flags: needinfo?(igoldan)
as a note, :igoldan is on pto until September 24th.
:igoldan, can you look at this again?
(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #6)
> :igoldan, can you look at this again?

Yes, I did and the issue isn't reproducing anymore. Marking this as WORKSFORME.
Flags: needinfo?(igoldan)
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.