Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upLimit test data excluded and support HARFBUZZ_SYS_NO_PKG_CONFIG better #142
Conversation
|
I don't understand the error. On the PR build (
Is this a Travis-CI cache issue of some sort? |
|
The PR is on travis-ci.com, and mine is on travis-ci.org. Does that make a difference? |
|
That's the same error that I saw on my PR for one of the CI builds (the other passed). I don't know what to make of it. |
|
At least now something's happening on both travis-ci.com and travis-ci.org: https://travis-ci.com/servo/rust-harfbuzz/jobs/189894765 (
https://travis-ci.org/spl/rust-harfbuzz/jobs/515032933 (
|
|
Well, at least I can confirm that the last modified file time does change. Not yet sure if that's useful, but it seems to imply that
1554278467.852523536 - 1554278454.221515537 = 13.63100791 seconds |
|
Now, when I see:
I can confirm that its file modification time changed (and no other non- -[harfbuzz-sys 0.3.1] -rw-rw-r-- 1 travis travis 12409 2019-04-03 11:36:22.227032921 +0000 hb-ot-shape-complex-myanmar-machine.hh
+[harfbuzz-sys 0.3.1] -rw-rw-r-- 1 travis travis 12409 2019-04-03 11:36:36.647224654 +0000 hb-ot-shape-complex-myanmar-machine.hhand no content changed:
Unfortunately, this particular error and every other one appears nondeterministically. |
|
Just to prove my point, triggering a rebuild in 4a6d69a caused the error to go away. |
|
I'm at a loss. Sometimes, it's |
fasihrana
commented
Apr 10, 2019
|
This just caused an issue for me publishing my own dependent crate to crates.io. I don't see an issue when building binaries, but this shows up in |
@fasihrana I think you're referring to #137, which was fixed in #144, and that was merged to This particular PR started as a fix for #137 but has since become an attempt to figure out yet another, more elusive issue with |
fasihrana
commented
Apr 10, 2019
Thank you. I'll update my crate once that is released. |
|
While this was a interesting (and challenging) experiment to determine why sporadic and spurious errors were appearing when running |
|
Correction: The |
cargo package sporadically complains about file modifications outside the OUT_DIR. See servo#142 for an experiment with chasing down that issue, which can involve different files changed at different times. The build script is written to build out-of-tree in the OUT_DIR, but it seems like 'configure' and/or 'make' still modifies the source tree. This change involves creating a temporary BUILD_DIR in the OUT_DIR, copying the source files there, building, installing into the OUT_DIR, and removing the BUILD_DIR.
cargo package sporadically complains about file modifications outside the OUT_DIR. See servo#142 for an experiment with chasing down that issue, which can involve different files changed at different times. The build script is written to build out-of-tree in the OUT_DIR, but `configure` and/or `make` still modifies the source tree. This change involves creating a temporary BUILD_DIR in the OUT_DIR, copying the source files there, building, installing into the OUT_DIR, and, finally, removing the BUILD_DIR.
cargo package sporadically complains about file modifications outside the OUT_DIR. See servo#142 for an experiment with chasing down that issue, which can involve different files changed at different times. The build script is written to build out-of-tree in the OUT_DIR, but `configure` and/or `make` still modifies the source tree. This change involves creating a temporary BUILD_DIR in the OUT_DIR, copying the source files there, building, installing into the OUT_DIR, and, finally, removing the BUILD_DIR.
`cargo package` sporadically complains about file modifications outside `OUT_DIR`. See servo#142 for an experiment with chasing down that issue, which can involve different files changed at different times. The build script is written to build out-of-tree in `OUT_DIR`, but `configure` and/or `make` still modify the source tree. This change involves creating a temporary `BUILD_DIR` in `OUT_DIR`, copying the source files there, building, installing into `OUT_DIR`, and, finally, removing `BUILD_DIR`.
Avoid source changes during static build `cargo package` sporadically complains about file modifications outside `OUT_DIR`. See #142 for an experiment with chasing down that issue, which can involve different files changed at different times. The build script is written to build out-of-tree in `OUT_DIR`, but `configure` and/or `make` still modify the source tree. This change involves creating a temporary `BUILD_DIR` in `OUT_DIR`, copying the source files there, building, installing into `OUT_DIR`, and, finally, removing `BUILD_DIR`. <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/rust-harfbuzz/147) <!-- Reviewable:end -->
spl commentedApr 2, 2019
•
edited by larsbergstrom
HARFBUZZ_SYS_NO_PKG_CONFIGbeing0or1.osx.This change is