Closed Bug 1025788 Opened 10 years ago Closed 10 years ago

[Flame] build tcpdump

Categories

(Firefox OS Graveyard :: GonkIntegration, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
2.1 S1 (1aug)

People

(Reporter: gerard-majax, Assigned: gerard-majax)

References

Details

(Whiteboard: [systemsfe])

Attachments

(1 file, 2 obsolete files)

52 bytes, text/x-github-pull-request
gerard-majax
: review+
Details | Review
As far as I can say, we do not build tcpdump for the Flame.

Adding:
> <project name="platform/external/tcpdump" path="external/tcpdump"/>

To the manifest should be enough.
We also need libpcap:

> <project name="platform/external/libpcap" path="external/libpcap"/>

That does produce a binary in xbin:
> $ find out/target/product/flame/system/ | grep tcpdump
> out/target/product/flame/system/xbin/tcpdump
Attached file Manifest update (obsolete) —
Michael, please find attached the pull request that adds the needed bits to the device manifest. I'm wondering about two points:
 - maybe we should do this against base-jb.xml and base-jb-caf.xml
 - we need to mirror those repos, right?
Assignee: nobody → lissyx+mozillians
Status: NEW → ASSIGNED
Attachment #8443388 - Flags: review?(mwu)
Whiteboard: [systemsfe]
Target Milestone: --- → 2.0 S4 (20june)
(In reply to Alexandre LISSY :gerard-majax from comment #2)
> Created attachment 8443388 [details] [review]
> Manifest update
> 
> Michael, please find attached the pull request that adds the needed bits to
> the device manifest. I'm wondering about two points:
>  - maybe we should do this against base-jb.xml and base-jb-caf.xml

Yes, base-jb.xml sounds good.

>  - we need to mirror those repos, right?

Yup. (unless someone mirrored them already)
As far as I can say, Flame includes base-caf-jb, not base-jb.
Include it in both.

In the kk manifests, base-kk-aosp includes base-kk, and base-kk-caf will include base-kk when it's introduced.
Comment on attachment 8443388 [details] [review]
Manifest update

Per discussion, waiting for a PR that adds this to the applicable base manifests.
Attachment #8443388 - Flags: review?(mwu)
Target Milestone: 2.0 S4 (20june) → 2.0 S5 (4july)
Comment on attachment 8443388 [details] [review]
Manifest update

Michael, new PR pushed with libpcap and tcpdump in:
 - base-caf-jb
 - base-caf
 - base-kk
Attachment #8443388 - Flags: review?(mwu)
Comment on attachment 8443388 [details] [review]
Manifest update

Looks good. As usual, make sure there are mirrors before merging.
Attachment #8443388 - Flags: review?(mwu) → review+
Depends on: 1029342
https://github.com/mozilla-b2g/b2g-manifest/commit/7031c46b9bd6f9ba1b83024576a02045fe169a7c
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
(In reply to Alexandre LISSY :gerard-majax from comment #9)
> https://github.com/mozilla-b2g/b2g-manifest/commit/
> 7031c46b9bd6f9ba1b83024576a02045fe169a7c

Reverted on suspicion of causing bug 1031354.

https://github.com/mozilla-b2g/b2g-manifest/commit/de6d982e708fc2df69a1051330aab5063f89e00e
Blocks: 1031354
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Can I get an explanation ? According to bug 1031378 it's the lack of mirroring of the new repos.
I did asked and waited for mirrors to be configured, in bug 1029342.
Flags: needinfo?(emorley)
Okay the URLs from bug 1029342 were wrong.
(In reply to Alexandre LISSY :gerard-majax from comment #11)
> Can I get an explanation ? According to bug 1031378 it's the lack of
> mirroring of the new repos.
> I did asked and waited for mirrors to be configured, in bug 1029342.

In cases like this, you need to ask the person assigned to that bug, or else someone else from releng, since the sheriffs do not set up or maintain repos on disk, mirroring to git.m.o or the b2g bumper bot.
Flags: needinfo?(emorley)
Target Milestone: 2.0 S5 (4july) → 2.0 S6 (18july)
Attached file Manifest update, rebased (obsolete) —
Carrying r+, rebasing the manifest on the current master after the backout. There is no emergency to land this, so I'll needinfo? myself to make sure we land it after the 2.0 hurry period.
Attachment #8443388 - Attachment is obsolete: true
Attachment #8453790 - Flags: review+
Flags: needinfo?(lissyx+mozillians)
Target Milestone: 2.0 S6 (18july) → 2.1 S1 (1aug)
Relanded, hopefully this will not break again :)
https://github.com/mozilla-b2g/b2g-manifest/commit/b5c6241c2e598e14ddfea126ee598c7e3c9430c9
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Flags: needinfo?(lissyx+mozillians)
Resolution: --- → FIXED
I'll keep my eye out for problems on this
(long term solution: bug 1031378)
Okay for some reason this is not working as expected:

> 05:55:57  WARNING - Returned 128 - sleeping and retrying
> 05:55:57  WARNING - Got output: fatal: remote error: FATAL: R any external/caf/platform/external/libpcap gitweb DENIED by fallthru
> 05:55:57  WARNING - (or you mis-spelled the reponame)
> 05:55:59  WARNING - Returned 128 - sleeping and retrying
> 05:55:59  WARNING - Got output: fatal: remote error: FATAL: R any external/caf/platform/external/tcpdump gitweb DENIED by fallthru
> 05:55:59  WARNING - (or you mis-spelled the reponame)
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
B2G bumper script is here:
http://hg.mozilla.org/build/mozharness/file/375d8b60ae6b/scripts/b2g_bumper.py

The answer will be in here.

The docs probably need to be improved on this topic - I'll investigate.
No longer blocks: 1031354
Depends on: 1031354
See Also: → 1042122
See Also: 1042122
Looking into this now...
OK, finally have a moment to look at this now (I got caught up in another matter on Tuesday).

Agreed that the repos are mirrored here:
http://git.mozilla.org/?p=external/aosp/platform/external/tcpdump.git;a=summary
http://git.mozilla.org/?p=external/aosp/platform/external/libpcap.git;a=summary

But for some reason they are being looked for here:
http://git.mozilla.org/?p=external/caf/platform/external/tcpdump.git;a=summary
http://git.mozilla.org/?p=external/caf/platform/external/libpcap.git;a=summary

In other words: they are being looked for under "caf" rather than under "aosp". I will now look into the code to see how this path is "built" as the xml entries are:

    <project name="platform/external/libpcap" path="external/libpcap"/>
    <project name="platform/external/tcpdump" path="external/tcpdump"/>

and at the moment I don't know how that gets translated to the full git url path.
See Also: → 1031378
This is strange indeed, the mappings seem correct:
e.g.: http://hg.mozilla.org/build/mozharness/file/26e71e92141f/configs/b2g_bumper/master.py#l73

This mapping exists in all the b2g2 bumper config files:
http://hg.mozilla.org/build/mozharness/file/26e71e92141f/configs/b2g_bumper

In vcs sync, we do mirror from:
https://android.googlesource.com/platform/external/libpcap/
https://android.googlesource.com/platform/external/tcpdump/

but at the moment I haven't (yet) seen how we know that in b2g_bumper - I will investigate now to see where that is defined...
So I think I found it. ;)

base-caf-jb.xml is imported in one and only one place:
 * https://github.com/mozilla-b2g/b2g-manifest/blob/master/flame.xml#L3

In base-caf-jb.xml, no remote="aosp" was specified.

flame.xml specifies a default remote of "caf":
 * https://github.com/mozilla-b2g/b2g-manifest/blob/master/flame.xml#L6

Therefore I'd assume, since no explicit remote is specified, it would take the default, which is "caf" rather than "aosp".

base-jb.xml is imported by four other manifests, which also all have "caf" as the default remote:
 * https://github.com/mozilla-b2g/b2g-manifest/blob/master/nexus-4.xml#L3-L5
 * https://github.com/mozilla-b2g/b2g-manifest/blob/master/emulator-jb.xml#L4-L6
 * https://github.com/mozilla-b2g/b2g-manifest/blob/master/emulator-x86-jb.xml (symlink)
 * https://github.com/mozilla-b2g/b2g-manifest/blob/master/flo.xml#L3-L5

Solution:

It looks to me like you should add remote="aosp" to the new entries for libpcap and tcpdump in base-caf-jb.xml and base-jb.xml.

I would suspect that when you test locally, you will discover you are cloning from:
  * git://codeaurora.org/platform/external/libpcap
  * git://codeaurora.org/platform/external/tcpdump
rather than:
  * https://android.googlesource.com/platform/external/libpcap
  * https://android.googlesource.com/platform/external/tcpdump

I've tested that these codeaurora URLs also work - and they do - which is why you no doubt did not pick this up in testing.

Are you sure you want to mirror from https://android.googlesource.com/ and not git://codeaurora.org/ ?
The mirror on git.mozilla.org should have been from caf, not aosp. CAF is our standard mirror and has all the same things that AOSP has.
If this needs to be changed, probably best to reopen that bug.
Yeah, all the requested mirrors on that bug were wrong. :)
OK, I've reopened bug 1029342. Would be grateful if you both (Michael and Alexandre) could check it before we proceed:
https://bugzilla.mozilla.org/show_bug.cgi?id=1029342#c9

Many thanks,
Pete
New PR, hopefully the last one.
Attachment #8453790 - Attachment is obsolete: true
Attachment #8467620 - Flags: review+
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: