Skip to content

Commit

Permalink
build(Dockerfile.compute-node): do not log tar contents (#7953)
Browse files Browse the repository at this point in the history 
in build logs we get a lot of lines for building the compute node images
because of verbose tar unpack. we know the sha256 so we don't need to
log the contents. my hope is that this will allow us more reliably use
the github live updating log view.
  • Loading branch information
@koivunej
koivunej authored Jun 4, 2024
1 parent 0acb604 commit 9d4c113
Showing 1 changed file with 35 additions and 35 deletions.
Loading

1 comment on commit 9d4c113

@github-actions
Copy link

Choose a reason for hiding this comment

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

3274 tests run: 3120 passed, 2 failed, 152 skipped (full report)

Failures on Postgres 14

  • test_pgbench_intensive_init_workload[vanilla-github-actions-selfhosted-1000]: release
  • test_basebackup_with_high_slru_count[github-actions-selfhosted-vectored-10-13-30]: release
# Run all failed tests locally:
scripts/pytest -vv -n $(nproc) -k "test_pgbench_intensive_init_workload[vanilla-release-pg14-github-actions-selfhosted-1000] or test_basebackup_with_high_slru_count[release-pg14-github-actions-selfhosted-vectored-10-13-30]"
Flaky tests (1)

Postgres 16

  • test_vm_bit_clear_on_heap_lock: debug

Code coverage* (full report)

  • functions: 31.5% (6571 of 20866 functions)
  • lines: 48.4% (50850 of 104995 lines)

* collected from Rust tests only

The comment gets automatically updated with the latest test results
9d4c113 at 2024-06-04T13:04:11.255Z :recycle:

Please sign in to comment.