The default bug view has changed. See this FAQ.

LINK : fatal error LNK1266: error reading instrumentation file 'firefox.pgd'; File not found

RESOLVED FIXED in mozilla9

Status

()

Core
Build Config
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: armenzg, Assigned: glandium)

Tracking

(Blocks: 1 bug)

Trunk
mozilla9
x86_64
Windows Server 2008
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: fixed-in-bs)

Attachments

(2 attachments, 2 obsolete attachments)

I am hitting this compilation error on the Windows 64-bit builds and is keeping the builds red.

nsBrowserApp.obj 
LINK : fatal error LNK1266: error reading instrumentation file 'firefox.pgd'; File not found
make[6]: Leaving directory `/e/builds/moz2_slave/m-cen-w64/build/obj-firefox/browser/app'
make[6]: *** [firefox.exe] Error 242
make[5]: Leaving directory `/e/builds/moz2_slave/m-cen-w64/build/obj-firefox/browser'
make[4]: Leaving directory `/e/builds/moz2_slave/m-cen-w64/build/obj-firefox'
make[5]: *** [libs] Error 2
make[4]: *** [libs_tier_app] Error 2
make[3]: Leaving directory `/e/builds/moz2_slave/m-cen-w64/build/obj-firefox'
make[3]: *** [tier_app] Error 2
make[2]: *** [default] Error 2
make[2]: Leaving directory `/e/builds/moz2_slave/m-cen-w64/build/obj-firefox'
make[1]: Leaving directory `/e/builds/moz2_slave/m-cen-w64/build'
make[1]: *** [realbuild] Error 2
make: *** [profiledbuild] Error 2
Probably related to Bug 669031 ...
(Assignee)

Comment 2

6 years ago
It kind of partially looks like bug 678409, in that you somehow don't have profiling information, and the linker fails because of it, while it shouldn't.
(Assignee)

Comment 3

6 years ago
(In reply to Kyle Huey [:khuey] (khuey@mozilla.com) from comment #1)
> Probably related to Bug 669031 ...

Not quite, in that the file missing from bug 669031 is pretty much expected not to be there. Firefox.pgd being missing is not. Except if PROFILE_GEN_SCRIPT does nothing.
I have also hit this in the last week:
"LINK : fatal error LNK1266: error reading instrumentation file 'plc4.pgd'; File not found"

If I disable PGO on win64 do you think it will make us complete the step?
Yes, because this step will never be run.
(Assignee)

Comment 6

6 years ago
(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #4)
> I have also hit this in the last week:
> "LINK : fatal error LNK1266: error reading instrumentation file 'plc4.pgd';
> File not found"
> 
> If I disable PGO on win64 do you think it will make us complete the step?

You can also clobber.
(Assignee)

Updated

6 years ago
Duplicate of this bug: 678409
(Assignee)

Updated

6 years ago
Blocks: 659942
(Assignee)

Comment 8

6 years ago
Created attachment 553458 [details] [diff] [review]
Don't remove pgd files, but clear them with pgomgr instead
Attachment #553458 - Flags: review?(ted.mielczarek)
(Assignee)

Comment 9

6 years ago
Created attachment 553461 [details] [diff] [review]
Don't remove pgd files, but clear them with pgomgr instead. NSPR part
Attachment #553461 - Flags: review?(ted.mielczarek)
Comment on attachment 553458 [details] [diff] [review]
Don't remove pgd files, but clear them with pgomgr instead

Review of attachment 553458 [details] [diff] [review]:
-----------------------------------------------------------------

::: config/rules.mk
@@ +903,5 @@
>  ifdef MOZ_PROFILE_GENERATE
>  # Clean up profiling data during PROFILE_GENERATE phase
>  export::
>  ifeq ($(OS_ARCH)_$(GNU_CC), WINNT_)
> +	-$(for pgd,$(wildcard *.pgd),pgomgr -clear $(pgd);)

ITYM $(foreach) here. Will this blow up if there are no pgd files present? (This will expand to just - then.)
Attachment #553458 - Flags: review?(ted.mielczarek) → review+
(Assignee)

Comment 11

6 years ago
Created attachment 553464 [details] [diff] [review]
Don't remove pgd files, but clear them with pgomgr instead
Attachment #553464 - Flags: review?(ted.mielczarek)
(Assignee)

Updated

6 years ago
Attachment #553458 - Attachment is obsolete: true
(Assignee)

Comment 12

6 years ago
Created attachment 553465 [details] [diff] [review]
Don't remove pgd files, but clear them with pgomgr instead. NSPR part
Attachment #553465 - Flags: review?(ted.mielczarek)
(Assignee)

Updated

6 years ago
Attachment #553461 - Attachment is obsolete: true
Attachment #553461 - Flags: review?(ted.mielczarek)
Attachment #553465 - Flags: review?(ted.mielczarek) → review+
Attachment #553464 - Flags: review?(ted.mielczarek) → review+
Clobbering did the job. Clobberer was not working on staging.

This is not a valid bug anymore but I see patches. Feel free to close it or whatever you feel is right.
No longer blocks: 558448
I have hit this again in production.

I have marked every builder to clobber since they could have objdirs from when they were connected to staging.
Assignee: nobody → mh+mozilla
NSPR patch:
Checking in config/rules.mk;
/cvsroot/mozilla/nsprpub/config/rules.mk,v  <--  rules.mk
new revision: 3.82; previous revision: 3.81
done
(Assignee)

Comment 16

6 years ago
http://hg.mozilla.org/projects/build-system/rev/e25c18bf42d2
Whiteboard: fixed-in-bs [needs nspr update]
(Assignee)

Comment 17

6 years ago
http://hg.mozilla.org/projects/build-system/rev/14497b5c651e
Whiteboard: fixed-in-bs [needs nspr update] → fixed-in-bs
http://hg.mozilla.org/mozilla-central/rev/e25c18bf42d2
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla9
(Assignee)

Updated

6 years ago
Duplicate of this bug: 669031
You need to log in before you can comment on or make changes to this bug.