Skip to content

add bytelimit for prefetch with better granularity#8756

Closed
flowguru wants to merge 3 commits into
apple:mainfrom
flowguru:b2
Closed

add bytelimit for prefetch with better granularity#8756
flowguru wants to merge 3 commits into
apple:mainfrom
flowguru:b2

Conversation

@flowguru

@flowguru flowguru commented Nov 9, 2022

Copy link
Copy Markdown
Contributor

This change adds bytelimit for prefetch API inside fdbserver, in order to do that, a better granularity is provided when fetching indexes and record.

Instead of fetching index once for each prefetch call, now there might be multiple index fetches.

Replace this text with your description here...

Code-Reviewer Section

The general pull request guidelines can be found here.

Please check each of the following things and check all boxes before accepting a PR.

  • The PR has a description, explaining both the problem and the solution.
  • The description mentions which forms of testing were done and the testing seems reasonable.
  • Every function/class/actor that was touched is reasonably well documented.

For Release-Branches

If this PR is made against a release-branch, please also check the following:

  • This change/bugfix is a cherry-pick from the next younger branch (younger release-branch or main if this is the youngest branch)
  • There is a good reason why this PR needs to go into a release branch and this reason is documented (either in the description above or in a linked GitHub issue)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang-ide on Linux CentOS 7

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang on Linux CentOS 7

  • Commit ID: 1425d5b
  • Duration 0:27:11
  • Result: ❌ FAILED
  • Error: Error while executing command: ctest -j ${NPROC} --no-compress-output -T test --output-on-failure. Reason: exit status 8
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr on Linux CentOS 7

  • Commit ID: 1425d5b
  • Duration 0:27:08
  • Result: ❌ FAILED
  • Error: Error while executing command: ctest -j ${NPROC} --no-compress-output -T test --output-on-failure. Reason: exit status 8
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-macos-m1 on macOS BigSur 11.5.2

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-macos on macOS Monterey 12.x

@flowguru

flowguru commented Nov 9, 2022

Copy link
Copy Markdown
Contributor Author

seems there are some testing issue, will take a look tomorrow

trace.0.0.0.0.0.1667954641.8ThUSC.0.1.xml:<Event Severity="40" ErrorKind="BugDetected" Time="82.273948" DateTime="2022-11-09T00:44:02Z" Type="InternalError" Machine="3.4.3.2:1" ID="0000000000000000" Error="internal_error" ErrorDescription="An internal error occurred" ErrorCode="4100" FailedAssertion="resultSize % SERVER_KNOBS-&gt;PREFETCH_INDEX_PAGE_SIZE == 0" File="/root/src/foundationdb/fdbserver/workloads/GetMappedRange.actor.cpp" Line="325" ThreadID="209490852615957828" Backtrace="addr2line -e fdbserver.debug -p -C -f -i 0x4420dbc 0x441f9f0 0x441fdee 0x43525fa 0x2d1c085 0x2d1ca05 0x2d1ac68 0x2d1bc95 0x3869838 0x39b697a 0x39ba04c 0x38fa828 0x39b2f88 0x39b311e 0x395b3e8 0xd8b158 0x4208c47 0x420930b 0x43062c8 0xc94a72 0x7f75a1463555" LogGroup="default" Roles="TS" />
trace.0.0.0.0.0.1667954641.8ThUSC.0.1.xml:<Event Severity="40" ErrorKind="Unset" Time="82.273948" DateTime="2022-11-09T00:44:02Z" Type="SystemError" Machine="3.4.3.2:1" ID="0000000000000000" Error="internal_error" ErrorDescription="An internal error occurred" ErrorCode="4100" ThreadID="209490852615957828" Backtrace="addr2line -e fdbserver.debug -p -C -f -i 0x4420dbc 0x441f9f0 0x441fdee 0x43520b8 0x435260c 0x2d1c085 0x2d1ca05 0x2d1ac68 0x2d1bc95 0x3869838 0x39b697a 0x39ba04c 0x38fa828 0x39b2f88 0x39b311e 0x395b3e8 0xd8b158 0x4208c47 0x420930b 0x43062c8 0xc94a72 0x7f75a1463555" LogGroup="default" Roles="TS" />
trace.0.0.0.0.0.1667954641.8ThUSC.0.1.xml:<Event Severity="40" ErrorKind="Unset" Time="82.273948" DateTime="2022-11-09T00:44:02Z" Type="TestFailure" Machine="3.4.3.2:1" ID="d74d63c0492fcee5" Error="internal_error" ErrorDescription="An internal error occurred" ErrorCode="4100" Reason="Error starting workload" Workload="GetMappedRange" ThreadID="209490852615957828" Backtrace="addr2line -e fdbserver.debug -p -C -f -i 0x4420dbc 0x441f9f0 0x441fdee 0x26e588c 0x26e59d7 0xd31569 0xdd3b19 0xd31569 0xd31569 0x26ba939 0xd31569 0x2d14de1 0xd31569 0x2d1ca8d 0x2d1ac68 0x2d1bc95 0x3869838 0x39b697a 0x39ba04c 0x38fa828 0x39b2f88 0x39b311e 0x395b3e8 0xd8b158 0x4208c47 0x420930b 0x43062c8 0xc94a72 0x7f75a1463555" LogGroup="default" Roles="TS" />
trace.0.0.0.0.0.1667954641.8ThUSC.0.1.xml:<Event Severity="40" ErrorKind="Unset" Time="82.275760" DateTime="2022-11-09T00:44:02Z" Type="StartFailedForWorkloadGetMappedRange" Machine="0.0.0.0:0" ID="0000000000000000" Error="operation_failed" ErrorDescription="Operation failed" ErrorCode="1000" ThreadID="209490852615957828" Backtrace="addr2line -e fdbserver.debug -p -C -f -i 0x4420dbc 0x441f9f0 0x441fdee 0x2725f79 0x26f53f4 0x26f5560 0xe5a498 0x10bc508 0x110c309 0x110c97a 0xd31569 0xdd63dd 0xdd66db 0xd31569 0xd3ea0c 0x4208c47 0x420930b 0x43062c8 0xc94a72 0x7f75a1463555" LogGroup="default" />

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang-ide on Linux CentOS 7

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang on Linux CentOS 7

  • Commit ID: f4c85eb
  • Duration 0:24:17
  • Result: ❌ FAILED
  • Error: Error while executing command: ctest -j ${NPROC} --no-compress-output -T test --output-on-failure. Reason: exit status 8
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang-ide on Linux CentOS 7

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr on Linux CentOS 7

  • Commit ID: f4c85eb
  • Duration 0:28:15
  • Result: ❌ FAILED
  • Error: Error while executing command: ctest -j ${NPROC} --no-compress-output -T test --output-on-failure. Reason: exit status 8
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang on Linux CentOS 7

  • Commit ID: 907f4f5
  • Duration 0:24:23
  • Result: ❌ FAILED
  • Error: Error while executing command: ctest -j ${NPROC} --no-compress-output -T test --output-on-failure. Reason: exit status 8
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr on Linux CentOS 7

  • Commit ID: 907f4f5
  • Duration 0:26:08
  • Result: ❌ FAILED
  • Error: Error while executing command: ctest -j ${NPROC} --no-compress-output -T test --output-on-failure. Reason: exit status 8
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@fdb-windows-ci

Copy link
Copy Markdown
Collaborator

Doxense CI Report for Windows 10

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-cluster-tests on Linux CentOS 7

  • Commit ID: 1425d5b
  • Duration 1:58:17
  • Result: ❌ FAILED
  • Error: Error while executing command: if $(grep -q -- "--- FAIL:" ${CODEBUILD_SRC_DIR}/fdb-kubernetes-tests/logs/*.log); then echo "TESTS FAILED SEE THESE LOGS:"; echo ; grep -l -- "--- FAIL:" ${CODEBUILD_SRC_DIR}/fdb-kubernetes-tests/logs/*.log; exit 1; fi. Reason: exit status 1
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-cluster-tests on Linux CentOS 7

  • Commit ID: f4c85eb
  • Duration 1:57:20
  • Result: ❌ FAILED
  • Error: Error while executing command: if $(grep -q -- "--- FAIL:" ${CODEBUILD_SRC_DIR}/fdb-kubernetes-tests/logs/*.log); then echo "TESTS FAILED SEE THESE LOGS:"; echo ; grep -l -- "--- FAIL:" ${CODEBUILD_SRC_DIR}/fdb-kubernetes-tests/logs/*.log; exit 1; fi. Reason: exit status 1
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-cluster-tests on Linux CentOS 7

  • Commit ID: 907f4f5
  • Duration 1:59:12
  • Result: ❌ FAILED
  • Error: Error while executing command: if $(grep -q -- "--- FAIL:" ${CODEBUILD_SRC_DIR}/fdb-kubernetes-tests/logs/*.log); then echo "TESTS FAILED SEE THESE LOGS:"; echo ; grep -l -- "--- FAIL:" ${CODEBUILD_SRC_DIR}/fdb-kubernetes-tests/logs/*.log; exit 1; fi. Reason: exit status 1
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@fdb-windows-ci

Copy link
Copy Markdown
Collaborator

Doxense CI Report for Windows 10

@flowguru
flowguru force-pushed the b2 branch 2 times, most recently from d0276ea to 66c7210 Compare November 9, 2022 08:20
This change adds bytelimit for prefetch API inside fdbserver,
in order to do that, a better granularity is provided when fetching
indexes and record.

Instead of fetching index once for each prefetch call, now there might
be multiple index fetches.
@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang-ide on Linux CentOS 7

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang-ide on Linux CentOS 7

  • Commit ID: 66c7210
  • Duration 0:10:23
  • Result: ❌ FAILED
  • Error: reference not found for primary source and source version 66c7210ec95178c6de43c55b143d0680f1af73cc
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang on Linux CentOS 7

  • Commit ID: 66c7210
  • Duration 0:10:19
  • Result: ❌ FAILED
  • Error: reference not found for primary source and source version 66c7210ec95178c6de43c55b143d0680f1af73cc
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@fdb-windows-ci

Copy link
Copy Markdown
Collaborator

Doxense CI Report for Windows 10

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang on Linux CentOS 7

  • Commit ID: d0276ea
  • Duration 0:21:58
  • Result: ❌ FAILED
  • Error: Error while executing command: ctest -j ${NPROC} --no-compress-output -T test --output-on-failure. Reason: exit status 8
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-macos on macOS Monterey 12.x

  • Commit ID: 66c7210
  • Duration 0:11:17
  • Result: ❌ FAILED
  • Error: reference not found for primary source and source version 66c7210ec95178c6de43c55b143d0680f1af73cc
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr on Linux CentOS 7

  • Commit ID: d0276ea
  • Duration 0:27:50
  • Result: ❌ FAILED
  • Error: Error while executing command: ctest -j ${NPROC} --no-compress-output -T test --output-on-failure. Reason: exit status 8
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang-ide on Linux CentOS 7

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang on Linux CentOS 7

  • Commit ID: b729562
  • Duration 0:23:46
  • Result: ❌ FAILED
  • Error: Error while executing command: ctest -j ${NPROC} --no-compress-output -T test --output-on-failure. Reason: exit status 8
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr on Linux CentOS 7

  • Commit ID: 66c7210
  • Duration 0:30:29
  • Result: ❌ FAILED
  • Error: Error while executing command: ctest -j ${NPROC} --no-compress-output -T test --output-on-failure. Reason: exit status 8
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-macos-m1 on macOS BigSur 11.5.2

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr on Linux CentOS 7

  • Commit ID: b729562
  • Duration 0:28:46
  • Result: ❌ FAILED
  • Error: Error while executing command: ctest -j ${NPROC} --no-compress-output -T test --output-on-failure. Reason: exit status 8
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-cluster-tests on Linux CentOS 7

  • Commit ID: b729562
  • Duration 0:29:48
  • Result: ❌ FAILED
  • Error: Error while executing command: docker build --label "org.foundationdb.version=${FDB_VERSION}" --label "org.foundationdb.build_date=${BUILD_DATE}" --label "org.foundationdb.commit=${COMMIT_SHA}" --progress plain --build-arg FDB_VERSION="${FDB_VERSION}" --build-arg FDB_LIBRARY_VERSIONS="${FDB_VERSION}" --build-arg FDB_WEBSITE="${FDB_WEBSITE}" --tag foundationdb/ycsb:${FDB_VERSION}-${COMMIT_SHA} --file Dockerfile --target ycsb .. Reason: exit status 1
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@fdb-windows-ci

Copy link
Copy Markdown
Collaborator

Doxense CI Report for Windows 10

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-cluster-tests on Linux CentOS 7

  • Commit ID: d0276ea
  • Duration 1:57:22
  • Result: ❌ FAILED
  • Error: Error while executing command: if $(grep -q -- "--- FAIL:" ${CODEBUILD_SRC_DIR}/fdb-kubernetes-tests/logs/*.log); then echo "TESTS FAILED SEE THESE LOGS:"; echo ; grep -l -- "--- FAIL:" ${CODEBUILD_SRC_DIR}/fdb-kubernetes-tests/logs/*.log; exit 1; fi. Reason: exit status 1
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-cluster-tests on Linux CentOS 7

  • Commit ID: 66c7210
  • Duration 1:57:45
  • Result: ❌ FAILED
  • Error: Error while executing command: if $(grep -q -- "--- FAIL:" ${CODEBUILD_SRC_DIR}/fdb-kubernetes-tests/logs/*.log); then echo "TESTS FAILED SEE THESE LOGS:"; echo ; grep -l -- "--- FAIL:" ${CODEBUILD_SRC_DIR}/fdb-kubernetes-tests/logs/*.log; exit 1; fi. Reason: exit status 1
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

alecgrieser
alecgrieser previously approved these changes Nov 9, 2022

@alecgrieser alecgrieser left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM, though I'm not an expert on this code. To summarize, the major changes are:

  1. During the scan of the primary range, a new "page size" parameter is added which breaks up the scan into multiple fetches
  2. The mapping of keys to other keys now checks the remaining bytes and stops executing batches of secondary fetches if the byte limit is exceeded. The batch size default is also decreased from 50 to 10.

Overall, this should result in getting requests to be closer to the configured byte limit, as the amount of potential overrun is limited to one page's worth of the primary range (from step 1) plus one batch's worth of secondary fetches (from step 2)

Comment on lines +4712 to +4716
// fill index KV for open boundary
if (firstBatch && i + offset == 0) {
result->data[0].key = input.data[0].key;
result->data[0].value = input.data[0].value;
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'm not sure I understand what this if block is trying to do. Why does result->data[0] need to be filled in in this case?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

we provide the index key for both the begin and the end of the range, so that client can use them as continuations -- I think it is because we might scan forward/backward, so we add both. Here it is the beginning.

Comment thread fdbserver/storageserver.actor.cpp Outdated
throw;
// these fields always return as the value of the last batch result
result.version = getKeyValuesReply.version;
result.cached = getKeyValuesReply.cached;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

What does this cached value represent? Is it correct to always set it to the last one?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

we can remove it, because I do not think it is used anywhere, @ohadzeliger can you please verify that RL has not been using this field?

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Do you mean cached field?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

oh i mean the value of this field might not used in prefetch code path, not deleting this field from code

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

cahced is not exposed through the Java bindings, we don't see it.

@@ -4602,52 +4602,59 @@ ACTOR Future<Void> mapSubquery(StorageServer* data,
Arena* pArena,
int matchIndex,
bool isRangeQuery,

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Does removing isBoundary make the protocol level change?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

two things:

  • removing the field in java/c bindings might cause issues, and we should be careful about that.
  • but this value is not being used anyway, and this field here is fdbserver internal, so my plan is to not setting it until we remove it. I can add a comments like "to be deleted" in that field

Comment thread fdbclient/ServerKnobs.cpp
init( STRICTLY_ENFORCE_BYTE_LIMIT, false); // If set to false, prefetch response might exceeed byteLimit as records are fetched in batch
// tentatively use the limit of secondary queries so that 1 primary query serves one batch
// we can increase this to gain better performance after proper benchmarking
init( PREFETCH_INDEX_PAGE_SIZE, 20 ); if ( randomize && BUGGIFY ) PREFETCH_INDEX_PAGE_SIZE = deterministicRandom()->randomInt(50, 100);

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

PREFETCH_INDEX_PAGE_SIZE cannot be controlled by the client API, right?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

right, that needs a protocol change, and I am not sure if want to expose that anyways.

Key endTuple = Tuple::makeTuple(prefix, INDEX, indexKey(endId)).getDataAsStandalone();
state KeySelector endSelector = KeySelector(firstGreaterOrEqual(endTuple));
state int limit = 100;
state int byteLimit = deterministicRandom()->randomInt(1, 9) * 10000;

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

What is the purpose of this (why is it random)?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

because when byteLimit is large, we want to test up to(but not exceeding) limit rows can be returned, when it is small, we want to test fewer than limit rows can be returned. So both cases need to be tested.

@fdb-windows-ci

Copy link
Copy Markdown
Collaborator

Doxense CI Report for Windows 10

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang on Linux CentOS 7

  • Commit ID: 81c9adc
  • Duration 0:22:58
  • Result: ❌ FAILED
  • Error: Error while executing command: ninja -v -C build_output -j ${NPROC} all packages strip_targets. Reason: exit status 1
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang-ide on Linux CentOS 7

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr on Linux CentOS 7

  • Commit ID: 81c9adc
  • Duration 0:28:47
  • Result: ❌ FAILED
  • Error: Error while executing command: ctest -j ${NPROC} --no-compress-output -T test --output-on-failure. Reason: exit status 8
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang-ide on Linux CentOS 7

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang on Linux CentOS 7

  • Commit ID: e52043f
  • Duration 0:24:27
  • Result: ❌ FAILED
  • Error: Error while executing command: ninja -v -C build_output -j ${NPROC} all packages strip_targets. Reason: exit status 1
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr on Linux CentOS 7

  • Commit ID: e52043f
  • Duration 0:29:13
  • Result: ❌ FAILED
  • Error: Error while executing command: ctest -j ${NPROC} --no-compress-output -T test --output-on-failure. Reason: exit status 8
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-cluster-tests on Linux CentOS 7

  • Commit ID: 81c9adc
  • Duration 1:58:00
  • Result: ❌ FAILED
  • Error: Error while executing command: if $(grep -q -- "--- FAIL:" ${CODEBUILD_SRC_DIR}/fdb-kubernetes-tests/logs/*.log); then echo "TESTS FAILED SEE THESE LOGS:"; echo ; grep -l -- "--- FAIL:" ${CODEBUILD_SRC_DIR}/fdb-kubernetes-tests/logs/*.log; exit 1; fi. Reason: exit status 1
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@foundationdb-ci

Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-cluster-tests on Linux CentOS 7

  • Commit ID: e52043f
  • Duration 2:00:15
  • Result: ❌ FAILED
  • Error: Error while executing command: if $(grep -q -- "--- FAIL:" ${CODEBUILD_SRC_DIR}/fdb-kubernetes-tests/logs/*.log); then echo "TESTS FAILED SEE THESE LOGS:"; echo ; grep -l -- "--- FAIL:" ${CODEBUILD_SRC_DIR}/fdb-kubernetes-tests/logs/*.log; exit 1; fi. Reason: exit status 1
  • Build Logs (available for 30 days)
  • Build Artifact (available for 30 days)

@flowguru

Copy link
Copy Markdown
Contributor Author

check #8768 instead

@flowguru flowguru closed this Nov 10, 2022
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.

5 participants