Closed Bug 690138 Opened 13 years ago Closed 12 years ago

l10n-stage: failing win32 try job reported as warning

Categories

(Release Engineering :: General, defect, P3)

x86
Windows XP
defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: joey, Assigned: joey)

References

Details

(Whiteboard: [tryserver][l10n])

My try job is testing some makefile changes {threadsafe mkdir} that are isolated from almost everything in the sandbox and should be considered a nop for submissions.


A few problems were reported while creating 'omni.jar' for l10n:

  o command run and try info included down below

  o Files were MIA { linux-mobile also reported another odd problem that might be due to a network hiccup }:

  adding: defaults/profile/mimeTypes.rdf (188 bytes security) (deflated 44%)
Can't find 'chrome.manifest' in ./omni.jar
Can't find 'components/interfaces.manifest' in ./omni.jar
   [ snip -- long streams of files ]

  o A few problems were reported
sed: can't read components/*.manifest: No such file or directory

  o make reports failure for the target { note 'Error 2' not 'ignoring', make -k is not in use }
make[4]: *** [repackage-zip] Error 2
make[3]: *** [repackage-win32-installer] Error 2
make[2]: *** [repackage-win32-installer-x-test] Error 2
make[1]: *** [l10n-check] Error 2
make[1]: Leaving directory `/e/builds/moz2_slave/try-w32/build/obj-firefox/browser/locales'
make: *** [l10n-check] Error 2
program finished with exit code 2

   o Logfile block trailer reports 'failed' for l10n-check
======== Finished 'make l10n-check ...' failed (results: 2, elapsed: 21 secs) ========

   o Result summary in the log reported 1 warning, email for the try submission also noted the same status.  

  * results: warnings (1)
  * Try submission 641748889589 - warnings

Conditions should have forced win32 to report an overall failure.


builder: try-win32
slave: w32-ix-slave04
starttime: 1317236005.67
results: warnings (1)
buildid: 20110928115423
builduid: 1d3139d7a12b4be2b81717c5b0eb107e
revision: 641748889589

cd ../../dist/l10n-stage; \
          (cd firefox && rm -f omni.jar components/binary.manifest && grep -h '^binary-component' components/*.man
ifest > binary.manifest ; for m in components/*.manifest; do sed -e 's/^binary-component/#binary-component/' $m > 
tmp.manifest && mv tmp.manifest $m; done; zip -r9m omni.jar chrome chrome.manifest components/*.js components/*.xp
t components/*.manifest modules res defaults greprefs.js jsloader  -x chrome/icons/\* defaults/pref/channel-prefs.
Priority: -- → P3
Whiteboard: [tryserver][l10n]
Depends on: 680246
check installed mt.exe version

build/config/install.exe.manifest : manfiest authoring warning 81010002: Unrecognized Element "compatibility" in namespace "urn:schemas-microsoft-com:compatibility.v1"
Assignee: nobody → joey
See Also: → 693612
See Also: → 693619
See Also: → 693621
See Also: → 693623
See Also: → 693630
Blocks: 680246
No longer depends on: 680246
No longer blocks: 680246
Dependency with 680246 was reversed.  A consumer that can make use of library makefile logic should not block the introduction of that logic.
Depends on: 680246
No longer depends on: 680246
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.