Skip to content

chore(operations): Compare test harness output with nightly/latest#2204

Merged
binarylogic merged 1 commit into
masterfrom
test-harness-output
Aug 1, 2020
Merged

chore(operations): Compare test harness output with nightly/latest#2204
binarylogic merged 1 commit into
masterfrom
test-harness-output

Conversation

@binarylogic

Copy link
Copy Markdown
Contributor

This defaults the test harness output to compare to the nightly/latest version. The only outstanding issue here is the use -c default since this is not always the case. For example, #2145 (comment) run a test with the -c big-vms flag which also needs to be passed to the bin/compare command.

Signed-off-by: binarylogic <bjohnson@binarylogic.com>
@binarylogic binarylogic requested a review from MOZGIII April 2, 2020 13:46
args: |
bash -o pipefail -xc "cd /vector-test-harness \
&& bin/compare -s vector -c default $(echo '${{ github.event.comment.body }}' | head -n 1 | sed 's|^/test ||') | tee \"$GITHUB_WORKSPACE/output\""
&& bin/compare -s vector -c default -v nightly/latest -v ${{ steps.cloned-repo-info.outputs.test_harness_vector_version }} $(echo '${{ github.event.comment.body }}' | head -n 1 | sed 's|^/test ||') | tee \"$GITHUB_WORKSPACE/output\""

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.

@MOZGIII I'm curious how you think we should go about carrying over the -c flag to here?

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.

If we make -c flag settable via env vars, we'll be able to assign it by default to default just like at the test command above.

I'm also thinking about adding a command to the test harness repo that would be dedicated to handling the Github Action invocations. This would better decouple the test harness logic from the Github Action logic - I believe it'd be better if the latter is scoped to just triggering test harness, so that we offload unrelated logic from it as much as possible.

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.

If we make -c flag settable via env vars, we'll be able to assign it by default to default just like at the test command above.

Btw, the same applies to -s.

@MOZGIII MOZGIII 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.

Looks good! Let's address the default config issue via a separate PR. This change is contained and looks correct, I see no reason why we should hesitate with merging it.

@binarylogic binarylogic added domain: ci Anything related to Vector's CI environment and removed domain: operations labels Jul 29, 2020
@binarylogic binarylogic merged commit af17d88 into master Aug 1, 2020
@binarylogic binarylogic deleted the test-harness-output branch August 1, 2020 16:04
mengesb pushed a commit to jacobbraaten/vector that referenced this pull request Dec 9, 2020
…ectordotdev#2204)

Signed-off-by: binarylogic <bjohnson@binarylogic.com>
Signed-off-by: Brian Menges <brian.menges@anaplan.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

domain: ci Anything related to Vector's CI environment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants