-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MINOR: [CI][C++] Update testing submodule #13963
Conversation
PR apache#13781 moved back the testing submodule to an old changeset by mistake, which subsequently broke multiple CI builds. (added a dummy C++ change to trigger CI)
CI results on my fork: pitrou@ba7a02d |
I'm gonna merge on the basis that it will fix a bunch of C++ CI builds that are currently failing. |
Benchmark runs are scheduled for baseline = 689f084 and contender = 25a2734. 25a2734 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
['Python', 'R'] benchmarks have high level of regressions. |
PR apache#13781 moved back the testing submodule to an old changeset by mistake, which subsequently broke multiple CI builds. (added a dummy C++ change to trigger CI) Authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
PR apache#13781 moved back the testing submodule to an old changeset by mistake, which subsequently broke multiple CI builds. (added a dummy C++ change to trigger CI) Authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
PR apache#13781 moved back the testing submodule to an old changeset by mistake, which subsequently broke multiple CI builds. (added a dummy C++ change to trigger CI) Authored-by: Antoine Pitrou <[email protected]> Signed-off-by: Antoine Pitrou <[email protected]>
PR #13781 moved back the testing submodule to an old changeset by mistake, which subsequently broke multiple CI builds.
(added a dummy C++ change to trigger CI)