Suppress 'no version information available' messages from b2g build logs



Release Engineering
3 years ago
3 years ago


(Reporter: nthomas, Assigned: Camilo, Mentored)



Firefox Tracking Flags

(b2g-v2.0 fixed, b2g-v2.1 fixed, b2g-v2.1S fixed, b2g-v2.2 fixed, b2g-master fixed)


(Whiteboard: [simple][lang=python])


(1 attachment)



3 years ago
Spun out from bug 1059992. We get a lot of this in b2g builds:

eg 15:55:15 INFO - /builds/slave/b2g_m-aurora_flm-kk_ntly-00000/build/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/../lib/gcc/arm-eabi/4.7/../../../../arm-eabi/bin/as: /lib64/ no version information available (required by /builds/slave/b2g_m-aurora_flm-kk_ntly-00000/build/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/../lib/gcc/arm-eabi/4.7/../../../../arm-eabi/bin/as)

This appears to be from the prebuilt being compiled on a newer OS than we're building on (per 

I want to suppress this because it adds no useful information, and pushes over the 50MB log limit we set in buildbot for some jobs. eg in a m-a flame eng job which is slightly over the 50M limit, we could save 8362034 bytes.
Can we make `as` shut up about this? or do you think mozharness should swallow it (convert it into a DEBUG line perhaps)?

Comment 2

3 years ago
Maybe with as -W:
  -W  --no-warn           suppress warnings

The flame builds are using 'GNU assembler (GNU Binutils)' at the moment.
That's not something as itself is outputing. That's the system dynamic linker complaining.
Essentially, it's telling you that the as program from the ndk was built against a that has symbol versions, while the system doesn't. There is no way to make the dynamic linker shut up for those, except to install a that does have symbol versions.
Ok, so how about a mozharness output filter that identifies those lines and classifies them as DEBUG? They'd still end up in the raw and debug logs, but hidden from stdout/stderr captured by buildbot I think.

Comment 5

3 years ago
catlee pointed me at


3 years ago
Whiteboard: [simple][lang=python][good first bug][mentor=catlee]
Whiteboard: [simple][lang=python][good first bug][mentor=catlee] → [simple][lang=python][good first bug]

Comment 6

3 years ago
Hello Chris
I would be willing to work on this bug. If you are willing to provide me some guidance it would be great.

So the basic idea here is to add an output filter that matches these 'no version information available' lines and categorizes them as DEBUG level output rather than INFO level output (which is the default).

You can test your mozharness changes on Try. Read up on this over at


3 years ago
Whiteboard: [simple][lang=python][good first bug] → [simple][lang=python]

Comment 8

3 years ago
Created attachment 8578781 [details] [diff] [review]

Hey Chris
Sorry for the huge delay ... studying + working doesn't leave a lot of free time :/

Here is a patch with the requested change for mozharness. I tested it on my computer and also on the travis server. You can check the log here (

Sadly I still don't understand how to do this step on the 'Try' server, to test the mozharness changes. I would appreciate if you could give me some more info there :)

PS: I also checked the github repo for the mozilla-inbound to see if I could clone it, but since it says that it is experimental, I avoided cloning it.
Flags: needinfo?(catlee)
Patch looks good to me!

Regarding testing on Try, do you have access to push to try at the moment? Do you have an hg repository with mozharness with your patch landed?

If so, then you can edit testing/mozharness/mozharness.json in your gecko repository to point to your mozharness repository, and then push your change to try.
Flags: needinfo?(catlee)

Comment 10

3 years ago
Hey Chris
No, I don't have access to Try. I have filed a bug requesting access to the Try server (level 1). Here is the link: According to what I have read I would need your voucher to be granted access.

Regarding mozharness, yes I have a repository with the patch on it. I push it to the Try server as soon as I get access.

Comment 11

3 years ago
Hey Chris
I pinned Mozharness as per instructions and push the changes to the try server. Here is the result:

Nevertheless the address that I received in the email for the builds and logs, doesn't exist :/ I don't understand why
Unfortunately the link given to you there is a bit misleading :\

If you click on the "B" label in treeherder, you can find a link to your log below:

Looks like it worked!

Comment 13

3 years ago
oh great :)
So what would be the next step?
we land the patch!

I've pushed it here:

It will be included in a deployment in the next few days.



3 years ago
Attachment #8578781 - Flags: review+
Attachment #8578781 - Flags: checked-in+
mozharness production tag moved to:

Comment 16

3 years ago
Shouldn't this bug be closed?

Comment 17

3 years ago
Yes indeed, thanks for the patch!
Assignee: nobody → carocad
Last Resolved: 3 years ago
Resolution: --- → FIXED

Comment 18

3 years ago
I needed to apply this fix to older b2g branches too.

The last is a fairly scary jump from mozharness 5d24cd109af6 (production branch on March 10), but 2_1 is was using the mozilla-b2g37_v2_2 branch already so hopefully it'll be OK.
status-b2g-v2.0: --- → fixed
status-b2g-v2.1: --- → fixed
status-b2g-v2.1S: --- → fixed
status-b2g-v2.2: --- → fixed
status-b2g-master: --- → fixed
You need to log in before you can comment on or make changes to this bug.