search

catapult-project / catapult

Deprecated Catapult GitHub. Please instead use http://crbug.com "Speed>Benchmarks" component for bugs and https://chromium.googlesource.com/catapult for downloading and editing source code..
https://chromium.googlesource.com/catapult
BSD 3-Clause "New" or "Revised" License
1.92k stars 564 forks source link

[📍] Generating the Results2 file failed. #4441

Closed wangxianzhu closed 6 years ago

wangxianzhu commented 6 years ago

In https://pinpoint-dot-chromeperf.appspot.com/job/14d52117c40000. click "Analyze benchmark results" and get "Generating the Results2 file failed".

wangxianzhu commented 6 years ago

This bug seems to prevent me from trying any CL on pinpoint. For example, https://pinpoint-dot-chromeperf.appspot.com/job/12b89797c40000. Can I get useful information from this try result without working "Analyze benchmark results"? For example, can I get the build logs and json results?

wangxianzhu commented 6 years ago

Never mind the previous comment. I found the method to get the json results: just click link after "isolate_hash".

simonhatch commented 6 years ago

I was able to manually force this to refresh, and it had no issues. You should be able to access the analyze benchmark results link now.

@dave-2 Logs seem to show a lot of results2 generation failures, all accessing the "changes" key in the job dict.

wangxianzhu commented 6 years ago

@simonhatch which link did you try that worked? I tried to refresh https://pinpoint-dot-chromeperf.appspot.com/results2/12b89797c40000 many times and all I got was the error.

mrego commented 6 years ago

I have the same issue in https://pinpoint-dot-chromeperf.appspot.com/job/16e32ddfc40000

simonhatch commented 6 years ago

Link from the first post.

mrego commented 6 years ago

How do you force a refresh?

I tried the very same job twice today and got the same error in both:

wangxianzhu commented 6 years ago

I just did some statistics on my pinpoint jobs, and found that all jobs before 5/4/2018 can show the results, and jobs after 5/7/2018 fail to show the results except one (23:1). I didn't schedule any jobs between 5/4 and 5/7.

mrego commented 6 years ago

Yesterday I retried and the result is similar:

simonhatch commented 6 years ago

I think there was a change to the job format that's causing these to fail to refresh properly. I'll dig into this today, and get all the broken ones rebuilt.

simonhatch commented 6 years ago

Ok this should be fixed, the results2 are set to force regeneration and all the ones posted in this bug have been regenerated.