Uh oh!
There was an error while loading. Please reload this page.
ARROW-14554: [C++][CI] Fix OSS-Fuzz build failure - #11583
Conversation
pitrou
commented
Nov 1, 2021
@github-actions crossbow submit -g cpp |
Thanks for opening a pull request! If this is not a minor PR. Could you open an issue for this pull request on JIRA? https://issues.apache.org/jira/browse/ARROW Opening JIRAs ahead of time contributes to the Openness of the Apache Arrow project. Then could you also rename pull request title in the following format? or See also: |
Revision: 209b1e6382c4fb4bc81e4f6a3e725fe2d1faddb9 Submitted crossbow builds: ursacomputing/crossbow @ actions-1063 |
pitrou
commented
Nov 1, 2021
@github-actions crossbow submit test-conda-* |
Revision: 4da0482af9451acbbd5c7efef6d83040e5d48d97 Submitted crossbow builds: ursacomputing/crossbow @ actions-1064 |
pitrou
commented
Nov 1, 2021
@github-actions crossbow submit test-conda-* |
pitrou
commented
Nov 1, 2021
@github-actions crossbow submit -g verify-rc-source |
Revision: 70a5ce2ae1beeac15b2745eaa4a701d4b8b2cb54 Submitted crossbow builds: ursacomputing/crossbow @ actions-1065 |
pitrou
commented
Nov 1, 2021
@github-actions crossbow submit vcpkg |
Revision: 70a5ce2ae1beeac15b2745eaa4a701d4b8b2cb54 Submitted crossbow builds: ursacomputing/crossbow @ actions-1066 |
Revision: 70a5ce2ae1beeac15b2745eaa4a701d4b8b2cb54 Submitted crossbow builds: ursacomputing/crossbow @ actions-1067
|
pitrou
commented
Nov 1, 2021
Hmm, it appears we cannot exercise the release verification script using crossbow (it tries to fetch Arrow 1.0.0)? @kszucs |
pitrou
commented
Nov 2, 2021
@github-actions crossbow submit test-conda-* |
Revision: a9cd09f34907e8183ebcdbca0f44d3145e17b11c Submitted crossbow builds: ursacomputing/crossbow @ actions-1068 |
pitrou
commented
Nov 2, 2021
@github-actions crossbow submit -g fuzz |
pitrou
commented
Nov 2, 2021
@github-actions crossbow submit -g fuzz |
pitrou
commented
Nov 2, 2021
@github-actions crossbow submit -g fuzz |
Revision: 7cf7cd67bf5f9748a95787eb0b824bae6d787036 Submitted crossbow builds: ursacomputing/crossbow @ actions-1069
|
pitrou
commented
Nov 2, 2021
@github-actions crossbow submit -g fuzz |
pitrou
commented
Nov 2, 2021
@github-actions crossbow submit -g fuzz |
Revision: 860317fead19201a884c7b2029a4ba5d9b8eb62f Submitted crossbow builds: ursacomputing/crossbow @ actions-1072
|
pitrou
commented
Nov 2, 2021
@github-actions crossbow submit -g fuzz |
Revision: 90971770ecc6e54fef48de05e50aa9e8f44c4713 Submitted crossbow builds: ursacomputing/crossbow @ actions-1073
|
ARROW-14393 downgraded the bundled GTest version to a version that doesn't build on the OSS-Fuzz setup (and there doesn't seem to be an obvious fix or workaround around those build errors). Re-bump the bundled GTest version, and try to fix the issue in the Windows verification script differently. Also, add a Crossbow task for the OSS-Fuzz build check, since the Github Actions cron job failure went unnoticed.
pitrou
commented
Nov 2, 2021
@github-actions crossbow submit test-conda-* |
Revision: 0bc448e Submitted crossbow builds: ursacomputing/crossbow @ actions-1074 |
pitrou
commented
Nov 2, 2021
@github-actions crossbow submit test-conda-* |
pitrou
commented
Nov 2, 2021
@github-actions crossbow submit test-conda-cpp-valgrind |
Revision: e035ed5 Submitted crossbow builds: ursacomputing/crossbow @ actions-1075
|
pitrou
commented
Nov 3, 2021
@github-actions crossbow submit test-conda-cpp-valgrind |
Revision: e035ed5 Submitted crossbow builds: ursacomputing/crossbow @ actions-1077
|
pitrou
commented
Nov 3, 2021
@kszucs Can we merge this? I'd like to unblock the OSS-Fuzz builds. |
kszucs
commented
Nov 3, 2021
We can only build releases with those tasks by providing additional parameters: #11511 (comment) |
kszucs
commented
Nov 3, 2021
Do we have a JIRA for that? |
pitrou
commented
Nov 3, 2021
I don't understand the question. What do you want a JIRA for? |
Benchmark runs are scheduled for baseline = 09b79a1 and contender = 64b80dd. 64b80dd is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
kszucs
commented
Nov 3, 2021
Does this fix the windows verification issue as well? |
Hopefully, but I have no way to verify it (as explained above :-)). |
ARROW-14393 downgraded the bundled GTest version to a version that doesn't build on the OSS-Fuzz setup
(and there doesn't seem to be an obvious fix or workaround around those build errors).
Re-bump the bundled GTest version, and try to fix the issue in the Windows verification script differently.
Also, add a Crossbow task for the OSS-Fuzz build check, since the Github Actions cron job failure went unnoticed.