I configured my local setup NOT to use sccache.
TB built successfully.
So it seems that sccache had a problem.
I noticed that my sccache was old : 0.2.2.
I upgraded it to 0.2.8-alpha.0 from github, and now re-invoking the
local build with sccache enabled and see
if the build succeeds.
Also, I enabled the logging by
SCCACHE_ERROR_LOG=/tmp/t.err
RUST_LOG=debug
before starting sccache server and monitor the LOG output (here it is
/tmp/t.err) to see anything suspicious is occuring.
I did so with 0.2.2 but other than the obscure failure, I did not see
clear picture of what went wrong.
I will report my finding whether with 0.2.8-alpha.0 sccache the build
succeeds, and if there is anything strange I may notice from the log.
TIA
On 2018/08/04 13:51, ISHIKAWA,chiaki wrote:
Hi,
I have been building TB under linux on a local PC.
Has anything been changed in the manner Rust library is compiled in
the last 5-10 days (or since mid-April)?
I have seen the following error for the first time on my PC:
error: failed to execute compile
caused by: error reading compile response from server
caused by: Failed to read response header
caused by: failed to fill whole buffer
error: Could not compile `style`.
To learn more, run the command again with --verbose.
make[4]: *** [/NREF-COMM-CENTRAL/mozilla/config/rules.mk:1006:
force-cargo-library-build] Error 101
make[3]: *** [/NREF-COMM-CENTRAL/mozilla/config/recurse.mk:74:
toolkit/library/rust/target] Error 2
make[3]: *** Waiting for unfinished jobs....
I am not sure what the server is.
Maybe, it could be that I refreshed the sccache, and some rust code
files may get recompiled for the first time in weeks, etc. So I am not
sure if a possible cause is inserted into the source tree in the last
few days (I refreshed my source this morning, and the last time was a
few days ago.)
So the change to trigger this bug easily might have happened in the
last several weeks or even more since I did not update the source tree
of TB together with M-C for a couple of months while I was working on
adapting a large patch set to the latest mid-April source tree.
Anyway, I suspect some kind of timeout error is to blame.
Is there a way to make the time out longer for this particular server:
I am not sure exactly though what the server is.
I am on a relatively powerful XEONÂ PC and so the CPU power may not be
a big problem (it has not been the case for the last few years), but
it may be I am running out of memory due to other activities on the
said PC (browsing with FF seems to occupy more memory now that it uses
separate processes for different tabs.)
So I suspect excessive paging I noticed sometimes may have caused an
unusual delay of the server, presumably sccache server, or does rustc
supports some type of compilation farm on its own?
Anyway, being able to extend the timeout value should fix the issue, I
hope.
I have tried to invoke the rust compilation time and time again, but
my local script stops after the compilation of C++ files and then
stops at this
error: Could not compile `style`.
repeatedly. Not good :-(
TIA
_______________________________________________
dev-builds mailing list
dev-builds@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-builds
_______________________________________________
dev-builds mailing list
dev-builds@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-builds
