Closed Bug 835378 Opened 12 years ago Closed 12 years ago

problems with hg->git mapper and last night's nightly?

Categories

(Release Engineering :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: joduinn, Unassigned)

References

Details

from #releng: ... 08:09:01 < philor> and b2g18 nightlies are broken with their mapper troubles again, wonder if anyone will notice today? ... 08:10:35 < joduinn> philor: can you file bug with details? is it "just" the mapper you see problems with, or are the builds also broken? 08:11:25 < philor> joduinn: the builds are broken by the mapper failing to find some rev, and "if anyone will notice" means "Not My Department to file on them, wonder if anyone will?" ... 08:14:26 < joduinn> philor: can you give some details even here, I'll paste into bug. Vague bugs usually take longer to figure out. 08:15:08 < philor> joduinn: https://tbpl.mozilla.org/?tree=Mozilla-B2g18&onlyunstarred=1 and click on one of the red letters, you'll know as much as I know 08:15:14 < joduinn> fyi, I know we were fixing a hg->git replication problem last night (Caused by bug in hg->git replication code when dealing with extended charsets)... doubt that was involved, but never know 08:15:22 < joduinn> philor: k 08:17:05 < catlee> hwine: have any idas? 08:17:08 < catlee> ideas 08:18:03 < hwine> catlee: iirc, this is now "by design" - if the mapper isn't working, we fail a nightly 08:18:18 < hwine> catlee: that was the outcome of the changes last week, aiui ... 08:20:07 < catlee> hwine: yes...but why can't mapper find the rev? ...
The rev doesn't exist in mapper because the hg -> git conversion is currently broken. We recently changed the build process to fail if it can't find the git revision for a given hg revision.
Depends on: 835202
The mapper files have caught up since bug 835202 has resolved
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.