(In reply to Ionuț Goldan [:igoldan], Performance Sheriffing from comment #5) > Anyway, I [pushed to Try](https://treeherder.mozilla.org/#/jobs?repo=try&revision=8ffce9e099a166f9e7ea0d7f5a5639263dfcedfc) the removal of the **fcp** from Rap-Cr tasks, to consolidate my theory. I see that all pageload tests failed because of this, while all benchmarks ran successfully. Have I missed something?
Bug 1554964 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Ionuț Goldan [:igoldan], Performance Sheriffing from comment #5) > Anyway, I [pushed to Try](https://treeherder.mozilla.org/#/jobs?repo=try&revision=8ffce9e099a166f9e7ea0d7f5a5639263dfcedfc) the removal of the **fcp** from Rap-Cr tasks, to consolidate my theory. I see that all pageload tests failed because of this, while all benchmarks ran successfully. Have I missed something? Still, the successfulness of the benchmarks *(which previously failed)* confirm there's something wrong when recording the **fcp**.
(In reply to Ionuț Goldan [:igoldan], Performance Sheriffing from comment #5) > Anyway, I [pushed to Try](https://treeherder.mozilla.org/#/jobs?repo=try&revision=8ffce9e099a166f9e7ea0d7f5a5639263dfcedfc) the removal of the **fcp** from Rap-Cr tasks, to consolidate my theory. I see that all pageload tests failed because of this, while all benchmarks ran successfully. Have I missed something? Still, the successfulness of the benchmarks *(which previously failed)* confirms there's something wrong when recording the **fcp**.