1840841 - Searchfox doesn't display the right files on mozilla-esr102

Status: VERIFIED FIXED

(Webtools :: Searchfox, defect)

Description

[Johan Lorenzo [:jlorenzo]]

Attachment: image.png

Steps to reproduce

1. Visit https://searchfox.org/mozilla-esr102/source/browser/config/version_display.txt

Expected result

Content should match what's currently on https://hg.mozilla.org/releases/mozilla-esr102/raw-file/tip/browser/config/version_display.txt (102.13.0esr at time of writing)

Actual result

Mozilla-central seems to be displayed instead because the value is currently 116.0a1. See attached screenshot.

Comment 1

[Kartikaya Gupta (email:[e-mail])]

In the indexer log I see this:

+ git fetch --multiple central pine elm beta release esr102 esr91 esr78 esr68 esr60 esr45 esr31 esr17
Fetching central
^MERROR TLS/SSL connection has been closed (EOF) (_ssl.c:997)
Run the command again with `git -c cinnabar.check=traceback <command>` to see the full traceback.
error: could not fetch central
Fetching pine
^MERROR TLS/SSL connection has been closed (EOF) (_ssl.c:997)
Run the command again with `git -c cinnabar.check=traceback <command>` to see the full traceback.
error: could not fetch pine
Fetching elm
^MERROR TLS/SSL connection has been closed (EOF) (_ssl.c:997)
Run the command again with `git -c cinnabar.check=traceback <command>` to see the full traceback.
error: could not fetch elm
Fetching beta
^MERROR TLS/SSL connection has been closed (EOF) (_ssl.c:997)
Run the command again with `git -c cinnabar.check=traceback <command>` to see the full traceback.
error: could not fetch beta
Fetching release
^MERROR TLS/SSL connection has been closed (EOF) (_ssl.c:997)
Run the command again with `git -c cinnabar.check=traceback <command>` to see the full traceback.
error: could not fetch release
Fetching esr102
^MERROR TLS/SSL connection has been closed (EOF) (_ssl.c:997)
Run the command again with `git -c cinnabar.check=traceback <command>` to see the full traceback.
error: could not fetch esr102
[snip]

which is maybe related? It left the git checkout at master rather than esr102. I think this was an intermittent failure which resulted in bad fallback behaviour. But the next working config2 run should be good I hope.

Comment 2

[Kartikaya Gupta (email:[e-mail])]

New config2 run is up, and it shows the right content.

Comment 3

[Johan Lorenzo [:jlorenzo]]

I confirm it does. Thank you very much :kats! 😃