Skip to content
BenchBase (Java with Maven)

Fix Port Binding Issue During Testing #1505

Sign in to view logs

Fix Port Binding Issue During Testing

Fix Port Binding Issue During Testing #1505

Triggered via pull request November 14, 2023 16:35
@bpkrothbpkroth
synchronize #382
neeetman:main
Status Failure
Total duration 1h 19m 24s
Artifacts 8
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

maven.yml

on: pull_request
compile-and-test
4m 2s
compile-and-test
docker-build-test-publish
9m 5s
docker-build-test-publish
Matrix: package-and-upload
Matrix: cockroachdb
Matrix: mariadb
Matrix: mysql
Matrix: postgresql
Matrix: sqlite
Matrix: sqlserver
Fit to window
Zoom out
Zoom in

Annotations

12 errors
mysql (smallbank)
The hosted runner: GitHub Actions 30 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
mysql (noop)
The hosted runner: GitHub Actions 27 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
sqlserver (noop)
The hosted runner: GitHub Actions 6 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
postgresql (otmetrics)
The hosted runner: GitHub Actions 33 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
postgresql (tpcc)
The hosted runner: GitHub Actions 16 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
postgresql (sibench)
The hosted runner: GitHub Actions 48 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
sqlserver (twitter)
The hosted runner: GitHub Actions 44 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
sqlserver (templated)
The hosted runner: GitHub Actions 52 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
sqlserver (tpch)
The hosted runner: GitHub Actions 35 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
sqlite (epinions)
The hosted runner: GitHub Actions 34 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
sqlite (tpcc)
The hosted runner: GitHub Actions 36 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
sqlite (sibench)
The hosted runner: GitHub Actions 58 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

Artifacts

Produced during runtime
Name Size
benchbase-cockroachdb Expired
50 MB
benchbase-mariadb Expired
53.2 MB
benchbase-mysql Expired
52.7 MB
benchbase-phoenix Expired
179 MB
benchbase-postgres Expired
50 MB
benchbase-spanner Expired
88 MB
benchbase-sqlite Expired
61.1 MB
benchbase-sqlserver Expired
50.2 MB