Skip to content
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

Revert "CI: disable ARM integration test cases with libunwind crash" #63959

Conversation

azat
Copy link
Collaborator

@azat azat commented May 16, 2024

Let's try re-run after #63865

Reverts #63867

Fixes: #63855

#job_style_check
#job_Integration_tests_aarch64
#job_Integration_tests_release

@robot-ch-test-poll2 robot-ch-test-poll2 added the pr-not-for-changelog This PR should not be mentioned in the changelog label May 16, 2024
@robot-ch-test-poll2
Copy link
Contributor

robot-ch-test-poll2 commented May 16, 2024

This is an automated comment for commit 99b7d38 with description of existing statuses. It's updated for the latest CI running

❌ Click here to open a full report in a separate page

Check nameDescriptionStatus
A SyncThere's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS⏳ pending
CI runningA meta-check that indicates the running CI. Normally, it's in success or pending state. The failed status indicates some problems with the PR⏳ pending
Integration testsThe integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests❌ failure
Mergeable CheckChecks if all other necessary checks are successful❌ failure
Successful checks
Check nameDescriptionStatus
Fast testNormally this is the first check that is ran for a PR. It builds ClickHouse and runs most of stateless functional tests, omitting some. If it fails, further checks are not started until it is fixed. Look at the report to see which tests fail, then reproduce the failure locally as described here✅ success
PR CheckThere's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS✅ success
Style checkRuns a set of checks to keep the code style clean. If some of tests failed, see the related log from the report✅ success
Unit testsRuns the unit tests for different release types✅ success

@alesapin
Copy link
Member

Tried to check it locally -- didn't help.

@azat azat marked this pull request as draft May 16, 2024 14:10
@alesapin
Copy link
Member

@azat, please push empty commit

@azat
Copy link
Collaborator Author

azat commented May 16, 2024

OK, but you were saying that it does not work?

Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
@alesapin
Copy link
Member

> OK, but you were saying that it does not work?
Yes, but I have build with clang-17. In CI we have clang-18... Maybe there is some difference...

@alesapin
Copy link
Member

yes, didn't help, no stack trace on segfault.

@azat

This comment was marked as off-topic.

@azat

This comment was marked as off-topic.

@azat

This comment was marked as off-topic.

@azat
Copy link
Collaborator Author

azat commented May 17, 2024

OK, I've found the root cause - #64058

@azat azat closed this May 17, 2024
@azat azat deleted the revert-63867-disable_arm_integration_test_cases_with_libunwind_crash branch May 17, 2024 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr-not-for-changelog This PR should not be mentioned in the changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Not a bug: libunwind: aarch64: SIGSEGV signal handler leads to another seg fault
3 participants