(In reply to Marco Castelluccio [:marco] from comment #1) > I'm going to add a daily cron task that will automatically trigger the hook for m-c pushes that were not yet ingested. This should at least make it so that "latest" is never too old. What time of day were you thinking of setting the cron for? Right now the mozilla-central indexing job "start-release1-indexer"/"config1.json" starts doing things at 8am EST / 12pm GMT which has been moved earlier over time thanks to the Windows jobs getting faster via the move to cross-compilation. I think it's worth moving this later if we can get guaranteed matching coverage results. If it's a LOT later, it may be worth considering moving Searchfox to index after both of the nightlies (10 UTC and 22 UTC) instead of just 10 UTC. I don't know if coverage gets run for both nightlies though?
Bug 1677903 Comment 2 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 Marco Castelluccio [:marco] from comment #1) > I'm going to add a daily cron task that will automatically trigger the hook for m-c pushes that were not yet ingested. This should at least make it so that "latest" is never too old. What time of day were you thinking of setting the cron for? Right now the mozilla-central indexing job "start-release1-indexer"/"config1.json" starts doing things at 8am EST / 12pm GMT which has been moved earlier over time thanks to the Windows jobs getting faster via the move to cross-compilation. I think it's worth moving this later if we can get guaranteed matching coverage results. If it's a LOT later, it may be worth considering moving Searchfox to index after both of the nightlies ([10 UTC and 22 UTC](https://wiki.mozilla.org/Nightly#How_does_it_update.3F_Update_interval.3F)) instead of just 10 UTC. I don't know if coverage gets run for both nightlies though?