Skip to content

Conversation

@rishitha957
Copy link
Contributor

@rishitha957 rishitha957 commented Jan 22, 2026

fix runtestcase reporting failures as success

Signed-off-by: Rishitha Kalicheti <rkalicheti1@bloomberg.com>
Copy link

@roborivers roborivers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Coding style check: Success ✓.
Cbuild submission: Success ✓.
Regression testing: 0/0 tests failed ⚠.

Copy link

@roborivers roborivers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Coding style check: Success ✓.
Cbuild submission: Success ✓.
Regression testing: Success ✓.

The first 10 failing tests are:
analyze
analyze_partial_index_off_generated
renametable_lightweight_generated
renametable
selectv_timepart
consumer_non_atomic_default_consumer_generated
auth_twofiles_generated
auth_queueodh_generated
auth
userschema_queueodh_generated


testdb_note "test start"
timeout --kill-after=5s ${TEST_TIMEOUT} stdbuf -oL -eL bash -c "./runit ${DBNAME} 2>&1 | gawk '{ print strftime(\"%H:%M:%S>\"), \$0; fflush(); }'" &> ${TESTDIR}/logs/${DBNAME}.testcase
timeout --kill-after=5s ${TEST_TIMEOUT} stdbuf -oL -eL bash -c "set -o pipefail; ./runit ${DBNAME} 2>&1 | gawk '{ print strftime(\"%H:%M:%S>\"), \$0; fflush(); }'" &> ${TESTDIR}/logs/${DBNAME}.testcase
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we check for timeout $? before checking the pipeline status?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants