|mozilla/mach configure| or |mozilla/mach build| no longer works for TB source tree (local linux build)

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

|mozilla/mach configure| or |mozilla/mach build| no longer works for TB source tree (local linux build)

ISHIKAWA,chiaki
This may be expected more or less, but between mid-April (or earlier?) and now,
something changed presumably in M-C tree, and
|mozilla/mach configure| no longer works.

|make -f client.mk configure|, et al still works, though.

This may not be a big deal, but I thought I report it here.

(There is a similar bug report for Firefox under Android build about two
years ago, but it was unresolved back then ???)

The error message from |mozilla/mach build|:

/NREF-COMM-CENTRAL/comm-central/mozilla/configure
Configure complete!
        <--- note nothing gets built.
Be sure to run |mach build| to pick up any changes
Error running mach:

    ['build']

The error occurred in code that was called by the mach command. This is either
a bug in the called code itself or in the way that mach is calling it.

You should consider filing a bug for this issue.

If filing a bug, please include the full output of mach, including this error
message.

The details of the failure are as follows:

BuildEnvironmentNotFoundException: config.status not available. Run configure.

  File
"/NREF-COMM-CENTRAL/comm-central/mozilla/python/mozbuild/mozbuild/mach_commands.py",
line 173, in build
    mach_context=self._mach_context)
  File
"/NREF-COMM-CENTRAL/comm-central/mozilla/python/mozbuild/mozbuild/controller/building.py",
line 1051, in build
    config = self.config_environment
  File
"/NREF-COMM-CENTRAL/comm-central/mozilla/python/mozbuild/mozbuild/base.py",
line 236, in config_environment
    raise BuildEnvironmentNotFoundException('config.status not available.
Run configure.')

real    0m0.473s
user    0m0.287s
sys    0m0.167s
_______________________________________________
dev-apps-thunderbird mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-thunderbird
Reply | Threaded
Open this post in threaded view
|

Re: |mozilla/mach configure| or |mozilla/mach build| no longer works for TB source tree (local linux build)

ISHIKAWA,chiaki
One nice feature of using |mozilla/mach build| is the terse output from
compile command and
only the warning lines are shown during build which makes it very easy to spot
suspicious code as opposed to the copious output from |make -f client.mk build|.

Is it worthwhile to report this to bugzilla still now that the FF developers
may not be interested in supporting the tree for TB build any more?

TIA


On 2018年07月30日 09:29, ishikawa wrote:

> This may be expected more or less, but between mid-April (or earlier?) and now,
> something changed presumably in M-C tree, and
> |mozilla/mach configure| no longer works.
>
> |make -f client.mk configure|, et al still works, though.
>
> This may not be a big deal, but I thought I report it here.
>
> (There is a similar bug report for Firefox under Android build about two
> years ago, but it was unresolved back then ???)
>
> The error message from |mozilla/mach build|:
>
> /NREF-COMM-CENTRAL/comm-central/mozilla/configure
> Configure complete!
>         <--- note nothing gets built.
> Be sure to run |mach build| to pick up any changes
> Error running mach:
>
>     ['build']
>
> The error occurred in code that was called by the mach command. This is either
> a bug in the called code itself or in the way that mach is calling it.
>
> You should consider filing a bug for this issue.
>
> If filing a bug, please include the full output of mach, including this error
> message.
>
> The details of the failure are as follows:
>
> BuildEnvironmentNotFoundException: config.status not available. Run configure.
>
>   File
> "/NREF-COMM-CENTRAL/comm-central/mozilla/python/mozbuild/mozbuild/mach_commands.py",
> line 173, in build
>     mach_context=self._mach_context)
>   File
> "/NREF-COMM-CENTRAL/comm-central/mozilla/python/mozbuild/mozbuild/controller/building.py",
> line 1051, in build
>     config = self.config_environment
>   File
> "/NREF-COMM-CENTRAL/comm-central/mozilla/python/mozbuild/mozbuild/base.py",
> line 236, in config_environment
>     raise BuildEnvironmentNotFoundException('config.status not available.
> Run configure.')
>
> real    0m0.473s
> user    0m0.287s
> sys    0m0.167s
>

_______________________________________________
dev-apps-thunderbird mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-thunderbird
Reply | Threaded
Open this post in threaded view
|

Re: |mozilla/mach configure| or |mozilla/mach build| no longer works for TB source tree (local linux build)

Jörg Knobloch
Reply | Threaded
Open this post in threaded view
|

Re: |mozilla/mach configure| or |mozilla/mach build| no longer works for TB source tree (local linux build)

ISHIKAWA,chiaki
On 2018/07/30 16:21, Jörg Knobloch wrote:
> You need to use M-C as top source directory now:
>
> http://lists.thunderbird.net/pipermail/maildev_lists.thunderbird.net/2018-April/001152.html 
>
> http://lists.thunderbird.net/pipermail/maildev_lists.thunderbird.net/2018-April/001153.html 
>
>
> Jörg.
>

Thank you for the tips.

I think I have been working to update the patch with mid-April source tree.
I updated the source and suddenly "C-C as top source directory" did not
work any more.

I think I need to shuffle the files and check my MOZCONFIG file and
need to update a host of shell scripts to work with the new layout.

Thank you again!

Chiaki

_______________________________________________
dev-apps-thunderbird mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-thunderbird
Reply | Threaded
Open this post in threaded view
|

Re: |mozilla/mach configure| or |mozilla/mach build| no longer works for TB source tree (local linux build)

ISHIKAWA,chiaki
One more thing regarding the M-C layout change.

So this means we now have a different procedure for job submission to
try server?

Is there a document explaining this?

It used to be that if we need to include a patch for SUB M-C directory
we need to create extra files that would be handled by try server to be
the patch for SUB M-C directory.

Basically, we did this after creating the C-C patches, AND necessary
files to affect M-C changes for mozilla subdirectory(M-C), and then
under C-C top directory, we issued

     hg push -f ssh://hg.mozilla.org/try-comm-central

Now, what is the proper procedure now?

What is the "CURRENT DIRECTORY" when we submit the build job for TB now?
[And what would be the target, i.e., ssh://hg.mozilla.org/??? ]

Will the current directory to issue |hg push| be
1. - top-level M-C, or
2. - sub comm directory ?

In the case of 1, how do we tell we need to modify sub comm directory?

In the case of 2, how do we tell we need to modify the code in the other
subdirectories of mozilla (M-C) directory?

??? puzzled ???

Chiaki

PS: I sent a subscription request to MailDev mailing list. I didn't know
this existed (!)


On 2018/07/31 1:58, ISHIKAWA,chiaki wrote:

> On 2018/07/30 16:21, Jörg Knobloch wrote:
>> You need to use M-C as top source directory now:
>>
>> http://lists.thunderbird.net/pipermail/maildev_lists.thunderbird.net/2018-April/001152.html 
>>
>> http://lists.thunderbird.net/pipermail/maildev_lists.thunderbird.net/2018-April/001153.html 
>>
>>
>> Jörg.
>>
>
> Thank you for the tips.
>
> I think I have been working to update the patch with mid-April source tree.
> I updated the source and suddenly "C-C as top source directory" did not
> work any more.
>
> I think I need to shuffle the files and check my MOZCONFIG file and
> need to update a host of shell scripts to work with the new layout.
>
> Thank you again!
>
> Chiaki
>
> _______________________________________________
> dev-apps-thunderbird mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-apps-thunderbird

_______________________________________________
dev-apps-thunderbird mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-thunderbird
Reply | Threaded
Open this post in threaded view
|

Re: |mozilla/mach configure| or |mozilla/mach build| no longer works for TB source tree (local linux build)

Josiah Bruner-3
Hi Chiaki,

The process for submitting to try can be found here:
https://wiki.mozilla.org/ReleaseEngineering/ThunderbirdTryServer

It claims to answer all your questions. I tested the push-to-comm
scenario fairly recently and it worked. That said, I did not test the
"Pushing mozilla-central patches" stuff, so that may or may not work.

Regards,

// Josiah Bruner (:jsbruner)

On 7/31/18 2:34 PM, ISHIKAWA,chiaki wrote:

> One more thing regarding the M-C layout change.
>
> So this means we now have a different procedure for job submission to
> try server?
>
> Is there a document explaining this?
>
> It used to be that if we need to include a patch for SUB M-C directory
> we need to create extra files that would be handled by try server to be
> the patch for SUB M-C directory.
>
> Basically, we did this after creating the C-C patches, AND necessary
> files to affect M-C changes for mozilla subdirectory(M-C), and then
> under C-C top directory, we issued
>
>      hg push -f ssh://hg.mozilla.org/try-comm-central
>
> Now, what is the proper procedure now?
>
> What is the "CURRENT DIRECTORY" when we submit the build job for TB now?
> [And what would be the target, i.e., ssh://hg.mozilla.org/??? ]
>
> Will the current directory to issue |hg push| be
> 1. - top-level M-C, or
> 2. - sub comm directory ?
>
> In the case of 1, how do we tell we need to modify sub comm directory?
>
> In the case of 2, how do we tell we need to modify the code in the other
> subdirectories of mozilla (M-C) directory?
>
> ??? puzzled ???
>
> Chiaki
>
> PS: I sent a subscription request to MailDev mailing list. I didn't know
> this existed (!)
>
>
> On 2018/07/31 1:58, ISHIKAWA,chiaki wrote:
>> On 2018/07/30 16:21, Jörg Knobloch wrote:
>>> You need to use M-C as top source directory now:
>>>
>>> http://lists.thunderbird.net/pipermail/maildev_lists.thunderbird.net/2018-April/001152.html 
>>>
>>> http://lists.thunderbird.net/pipermail/maildev_lists.thunderbird.net/2018-April/001153.html 
>>>
>>>
>>> Jörg.
>>>
>>
>> Thank you for the tips.
>>
>> I think I have been working to update the patch with mid-April source
>> tree.
>> I updated the source and suddenly "C-C as top source directory" did
>> not work any more.
>>
>> I think I need to shuffle the files and check my MOZCONFIG file and
>> need to update a host of shell scripts to work with the new layout.
>>
>> Thank you again!
>>
>> Chiaki
>>
>> _______________________________________________
>> dev-apps-thunderbird mailing list
>> [hidden email]
>> https://lists.mozilla.org/listinfo/dev-apps-thunderbird
>
> _______________________________________________
> dev-apps-thunderbird mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-apps-thunderbird
_______________________________________________
dev-apps-thunderbird mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-thunderbird
Reply | Threaded
Open this post in threaded view
|

Re: |mozilla/mach configure| or |mozilla/mach build| no longer works for TB source tree (local linux build)

mozilla
In reply to this post by ISHIKAWA,chiaki
On Sun, Jul 29, 2018 at 6:31 PM ishikawa <[hidden email]> wrote:

> This may be expected more or less, but between mid-April (or earlier?) and
> now,
> something changed presumably in M-C tree, and
> |mozilla/mach configure| no longer works.
>
> |make -f client.mk configure|, et al still works, though.
>

I'll note that `client.mk` is an unsupported entrypoint for thunderbird
builds, in addition to the source layout changes.
_______________________________________________
dev-apps-thunderbird mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-thunderbird
Reply | Threaded
Open this post in threaded view
|

Re: |mozilla/mach configure| or |mozilla/mach build| no longer works for TB source tree (local linux build)

ISHIKAWA,chiaki
In reply to this post by Josiah Bruner-3
Dear Joshia,

Thank you.

The page seems to explain the essentials.

I will iron out the kinks of local build before submitting a build job.

With local build, I got hit with the following bug on top of needing to
remove configure file which Jorg mentioned.


Bug 1462794
Build error: cannot convert ‘nsPresState*’ to ‘mozilla::PresState*’
caused by left-over nsILayoutHistoryState.h in source tree

Also, I noticed a flurry of errors (due to my stricter checking on local
PC using GCC) which I needed to patch
and I submit a probable bug as I found in  the verbose warning which
suddenly came out after the layout change. Somehow the stricter warning
I applied to C-C tree is now applied to M-C tree as well, or that the
layout change somehow let the warning to be printed.

The following is probably a real bug.

Bug 1479950
Incorrect use of "&&" in place of "&" :
mozilla/gfx/skia/skia/src/gpu/GrColorSpaceXform.cpp:184:31: warning:
enum constant in boolean context [-Wint-in-bool-context] if
(SkToBool(a->fFlags && kApplyGamutXform_Flag) && a->fGamutXform !=
b->fGamutXform

I have a couple of unused variable warnings (which are turned into error
on my local PC). These and others will be filed eventually.

I am still compiling locally after I took the remedy in bug 1462794 above.
I will report the submission success once I get around to it. But with
the current pace, I am not sure if that happens this week :-(


Thank you very much.


On 2018/08/01 5:42, Josiah Bruner wrote:

> Hi Chiaki,
>
> The process for submitting to try can be found here:
> https://wiki.mozilla.org/ReleaseEngineering/ThunderbirdTryServer
>
> It claims to answer all your questions. I tested the push-to-comm
> scenario fairly recently and it worked. That said, I did not test the
> "Pushing mozilla-central patches" stuff, so that may or may not work.
>
> Regards,
>
> // Josiah Bruner (:jsbruner)
>
> On 7/31/18 2:34 PM, ISHIKAWA,chiaki wrote:
>> One more thing regarding the M-C layout change.
>>
>> So this means we now have a different procedure for job submission to
>> try server?
>>
>> Is there a document explaining this?
>>
>> It used to be that if we need to include a patch for SUB M-C directory
>> we need to create extra files that would be handled by try server to
>> be the patch for SUB M-C directory.
>>
>> Basically, we did this after creating the C-C patches, AND necessary
>> files to affect M-C changes for mozilla subdirectory(M-C), and then
>> under C-C top directory, we issued
>>
>>      hg push -f ssh://hg.mozilla.org/try-comm-central
>>
>> Now, what is the proper procedure now?
>>
>> What is the "CURRENT DIRECTORY" when we submit the build job for TB now?
>> [And what would be the target, i.e., ssh://hg.mozilla.org/??? ]
>>
>> Will the current directory to issue |hg push| be
>> 1. - top-level M-C, or
>> 2. - sub comm directory ?
>>
>> In the case of 1, how do we tell we need to modify sub comm directory?
>>
>> In the case of 2, how do we tell we need to modify the code in the
>> other subdirectories of mozilla (M-C) directory?
>>
>> ??? puzzled ???
>>
>> Chiaki
>>
>> PS: I sent a subscription request to MailDev mailing list. I didn't
>> know this existed (!)
>>
>>
>> On 2018/07/31 1:58, ISHIKAWA,chiaki wrote:
>>> On 2018/07/30 16:21, Jörg Knobloch wrote:
>>>> You need to use M-C as top source directory now:
>>>>
>>>> http://lists.thunderbird.net/pipermail/maildev_lists.thunderbird.net/2018-April/001152.html 
>>>>
>>>> http://lists.thunderbird.net/pipermail/maildev_lists.thunderbird.net/2018-April/001153.html 
>>>>
>>>>
>>>> Jörg.
>>>>
>>>
>>> Thank you for the tips.
>>>
>>> I think I have been working to update the patch with mid-April source
>>> tree.
>>> I updated the source and suddenly "C-C as top source directory" did
>>> not work any more.
>>>
>>> I think I need to shuffle the files and check my MOZCONFIG file and
>>> need to update a host of shell scripts to work with the new layout.
>>>
>>> Thank you again!
>>>
>>> Chiaki
>>>
>>> _______________________________________________
>>> dev-apps-thunderbird mailing list
>>> [hidden email]
>>> https://lists.mozilla.org/listinfo/dev-apps-thunderbird
>>
>> _______________________________________________
>> dev-apps-thunderbird mailing list
>> [hidden email]
>> https://lists.mozilla.org/listinfo/dev-apps-thunderbird
> _______________________________________________
> dev-apps-thunderbird mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-apps-thunderbird

_______________________________________________
dev-apps-thunderbird mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-thunderbird
Reply | Threaded
Open this post in threaded view
|

Re: |mozilla/mach configure| or |mozilla/mach build| no longer works for TB source tree (local linux build)

ISHIKAWA,chiaki
In reply to this post by ISHIKAWA,chiaki
On 2018年08月01日 06:08, Tom Prince wrote:

> On Sun, Jul 29, 2018 at 6:31 PM ishikawa <[hidden email]> wrote:
>
>> This may be expected more or less, but between mid-April (or earlier?) and
>> now,
>> something changed presumably in M-C tree, and
>> |mozilla/mach configure| no longer works.
>>
>> |make -f client.mk configure|, et al still works, though.
>>
>
> I'll note that `client.mk` is an unsupported entrypoint for thunderbird
> builds, in addition to the source layout changes.
>

Thank you. Your points are well taken.

I have changed my scripts to build, test, etc. to use |./mach| or |../mach|
, depending on the current directory,  directly.

I could build TB finally, but the |make mozill| and |../mach xpcshell-test|
have not been completed yet.

TIA
_______________________________________________
dev-apps-thunderbird mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-thunderbird
Reply | Threaded
Open this post in threaded view
|

Re: |mozilla/mach configure| or |mozilla/mach build| no longer works for TB source tree (local linux build)

ISHIKAWA,chiaki
In reply to this post by ISHIKAWA,chiaki
A big question.

For C-C tryserver job, should we use

     ../mach try <trysyntaxt>

or do we push directly to

     hg push -f ssh://hg.mozilla.org/try-comm-central


without |mach try <trysyntax>| wrapper?

I am asking BECAUSE

1. |../mach try| does not grok |--buildbot| passed at the end of
<trysyntax>. It barfs and fails to perform push.

2. |../mach try| pushes the changes to ssh://hg.mozilla.org/try, NOT THE
CORRECT
    ssh://hg.mozilla.org/try-comm-central even though I have, according to
https://wiki.mozilla.org/ReleaseEngineering/ThunderbirdTryServer, the
following setup in my .hg/hgrc file.

> "
>
>   * The |.hg/hgrc| that exists within the |comm/| folder must contain:
>
> [defaults]
> push-to-try = -sssh://hg.mozilla.org/try-comm-central
> "
(BTW, is "-s" above correct, and not -f ??? I just thought the direct
use of hg mentions -f there.)

Any thought?

TIA

Chiaki

On 2018/08/01 10:39, ISHIKAWA,chiaki wrote:

> Dear Joshia,
>
> Thank you.
>
> The page seems to explain the essentials.
>
> I will iron out the kinks of local build before submitting a build job.
>
> With local build, I got hit with the following bug on top of needing
> to remove configure file which Jorg mentioned.
>
>
> Bug 1462794
> Build error: cannot convert ‘nsPresState*’ to ‘mozilla::PresState*’
> caused by left-over nsILayoutHistoryState.h in source tree
>
> Also, I noticed a flurry of errors (due to my stricter checking on
> local PC using GCC) which I needed to patch
> and I submit a probable bug as I found in  the verbose warning which
> suddenly came out after the layout change. Somehow the stricter
> warning I applied to C-C tree is now applied to M-C tree as well, or
> that the layout change somehow let the warning to be printed.
>
> The following is probably a real bug.
>
> Bug 1479950
> Incorrect use of "&&" in place of "&" :
> mozilla/gfx/skia/skia/src/gpu/GrColorSpaceXform.cpp:184:31: warning:
> enum constant in boolean context [-Wint-in-bool-context] if
> (SkToBool(a->fFlags && kApplyGamutXform_Flag) && a->fGamutXform !=
> b->fGamutXform
>
> I have a couple of unused variable warnings (which are turned into
> error on my local PC). These and others will be filed eventually.
>
> I am still compiling locally after I took the remedy in bug 1462794
> above.
> I will report the submission success once I get around to it. But with
> the current pace, I am not sure if that happens this week :-(
>
>
> Thank you very much.
>
>
> On 2018/08/01 5:42, Josiah Bruner wrote:
>> Hi Chiaki,
>>
>> The process for submitting to try can be found here:
>> https://wiki.mozilla.org/ReleaseEngineering/ThunderbirdTryServer
>>
>> It claims to answer all your questions. I tested the push-to-comm
>> scenario fairly recently and it worked. That said, I did not test the
>> "Pushing mozilla-central patches" stuff, so that may or may not work.
>>
>> Regards,
>>
>> // Josiah Bruner (:jsbruner)
>>
>> On 7/31/18 2:34 PM, ISHIKAWA,chiaki wrote:
>>> One more thing regarding the M-C layout change.
>>>
>>> So this means we now have a different procedure for job submission
>>> to try server?
>>>
>>> Is there a document explaining this?
>>>
>>> It used to be that if we need to include a patch for SUB M-C
>>> directory we need to create extra files that would be handled by try
>>> server to be the patch for SUB M-C directory.
>>>
>>> Basically, we did this after creating the C-C patches, AND necessary
>>> files to affect M-C changes for mozilla subdirectory(M-C), and then
>>> under C-C top directory, we issued
>>>
>>>      hg push -f ssh://hg.mozilla.org/try-comm-central
>>>
>>> Now, what is the proper procedure now?
>>>
>>> What is the "CURRENT DIRECTORY" when we submit the build job for TB
>>> now?
>>> [And what would be the target, i.e., ssh://hg.mozilla.org/??? ]
>>>
>>> Will the current directory to issue |hg push| be
>>> 1. - top-level M-C, or
>>> 2. - sub comm directory ?
>>>
>>> In the case of 1, how do we tell we need to modify sub comm directory?
>>>
>>> In the case of 2, how do we tell we need to modify the code in the
>>> other subdirectories of mozilla (M-C) directory?
>>>
>>> ??? puzzled ???
>>>
>>> Chiaki
>>>
>>> PS: I sent a subscription request to MailDev mailing list. I didn't
>>> know this existed (!)
>>>
>>>
>>> On 2018/07/31 1:58, ISHIKAWA,chiaki wrote:
>>>> On 2018/07/30 16:21, Jörg Knobloch wrote:
>>>>> You need to use M-C as top source directory now:
>>>>>
>>>>> http://lists.thunderbird.net/pipermail/maildev_lists.thunderbird.net/2018-April/001152.html 
>>>>>
>>>>> http://lists.thunderbird.net/pipermail/maildev_lists.thunderbird.net/2018-April/001153.html 
>>>>>
>>>>>
>>>>> Jörg.
>>>>>
>>>>
>>>> Thank you for the tips.
>>>>
>>>> I think I have been working to update the patch with mid-April
>>>> source tree.
>>>> I updated the source and suddenly "C-C as top source directory" did
>>>> not work any more.
>>>>
>>>> I think I need to shuffle the files and check my MOZCONFIG file and
>>>> need to update a host of shell scripts to work with the new layout.
>>>>
>>>> Thank you again!
>>>>
>>>> Chiaki
>>>>
>>>> _______________________________________________
>>>> dev-apps-thunderbird mailing list
>>>> [hidden email]
>>>> https://lists.mozilla.org/listinfo/dev-apps-thunderbird
>>>
>>> _______________________________________________
>>> dev-apps-thunderbird mailing list
>>> [hidden email]
>>> https://lists.mozilla.org/listinfo/dev-apps-thunderbird
>> _______________________________________________
>> dev-apps-thunderbird mailing list
>> [hidden email]
>> https://lists.mozilla.org/listinfo/dev-apps-thunderbird
>
> _______________________________________________
> dev-apps-thunderbird mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-apps-thunderbird


_______________________________________________
dev-apps-thunderbird mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-thunderbird
Reply | Threaded
Open this post in threaded view
|

Re: |mozilla/mach configure| or |mozilla/mach build| no longer works for TB source tree (local linux build)

Jörg Knobloch
On 03/08/2018 03:02, ISHIKAWA,chiaki wrote:
> For C-C tryserver job, should we use
>     ../mach try <trysyntaxt>
> or do we push directly to
>     hg push -f ssh://hg.mozilla.org/try-comm-central

I don't know what we should use, I use the latter.

Jörg.


_______________________________________________
dev-apps-thunderbird mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-thunderbird
Reply | Threaded
Open this post in threaded view
|

Re: |mozilla/mach configure| or |mozilla/mach build| no longer works for TB source tree (local linux build)

ISHIKAWA,chiaki
On 2018/08/04 16:20, Jörg Knobloch wrote:

> On 03/08/2018 03:02, ISHIKAWA,chiaki wrote:
>> For C-C tryserver job, should we use
>>     ../mach try <trysyntaxt>
>> or do we push directly to
>>     hg push -f ssh://hg.mozilla.org/try-comm-central
>
> I don't know what we should use, I use the latter.
>
> Jörg.
>
>
>
>
It looks the explicit use of |hg push| is recommended when people use
mqueue extesion (as I do.)
 From https://wiki.mozilla.org/ReleaseEngineering/TryServer
near the middle.

>
>         Using mq
>
> The aforementioned tools may not play all that nicely with mercurial
> queues <https://www.mercurial-scm.org/wiki/MqExtension>. If you use
> mq, you can still push to try manually. First build your try syntax
> with the TryChooser <http://trychooser.pub.build.mozilla.org/> web
> page. Then run:
>
> $ hg qref --message "try: <your-computed-syntax-here>"
> $ hg push -f try

Aforementioned tools include the use of |mach try|.

So I will stick to explicit use of |hg push|, but I could not perform
successful submission yet. I got strange errors.
This can wait for a while until getting resolved. I will investigate.

So far, with the new M-C/C-C layout, I could build TB successfully after
resolving an issue or two with ccacche and sccache.

I found that my local patch set did not introduce any more local errors
than the stock unmodified tree when I performed tests of |make mozmill|
and |mach xpcshell-test ...|.

Isn't that great?

Especially, for the last few months, I noticed NO errors from |make
mozmill| and successful tests are way over 1200 or 1300. This had not
happened for a long time.
I believe this is mostly due to your effort, Jorg, with the help of
Aceman and others.
Thank you for the great work to keep C-C in good shape.

I will submit a few easy small patches which I noticed during this
transition that forced me to look at the warnings from C++ compilers
very carefully.

TIA


> _______________________________________________
> dev-apps-thunderbird mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-apps-thunderbird


_______________________________________________
dev-apps-thunderbird mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-thunderbird