Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(ci): fix breaking tests #8413

Merged
merged 7 commits into from
Nov 4, 2022
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions .github/workflows/ci-dgraph-load-tests.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
name: ci-dgraph-load-tests
name: ci-dgraph-load-tests-amd64
Copy link
Contributor

Choose a reason for hiding this comment

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

@joshua-goldstein - can we remove this line change?

I had mentioned this to @adityasadalage, and indicated to specify the x64, and not change the name.

We will lose history when we make a name change. Also, the future plan is to use matrix and bring in all the runner types into this workflow.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@skrdgraph yeah I wasn't sure on this point - I just reverted the change

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah ci-dgraph-tests-arm64.yml pipeline was given the new name. Would that need to be reverted to accommodate the matrix change later on?

on:
push:
branches:
Expand All @@ -16,13 +16,18 @@ on:
jobs:
dgraph-load-tests:
if: github.event.pull_request.draft == false
runs-on: self-hosted
runs-on: [self-hosted, x64]
steps:
- uses: actions/checkout@v3
- name: Get Go Version
run: |
#!/bin/bash
GOVERSION=$({ [ -f .go-version ] && cat .go-version; })
echo "GOVERSION=$GOVERSION" >> $GITHUB_ENV
Copy link
Contributor

Choose a reason for hiding this comment

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

+1 ^ thanks for adding this, could you also do this for go-lint?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@skrdgraph Sure, previously the linter yaml was skipping the Go installation step entirely with skip-go-installation: true . I just pushed changes that model the linter after the Badger linter setup (hence the version bumps). Let me know if that looks okay.

- name: Set up Go
uses: actions/setup-go@v3
with:
go-version: 1.18
go-version: ${{ env.GOVERSION }}
- name: Set up Node
uses: actions/setup-node@v3
with:
Expand Down
11 changes: 8 additions & 3 deletions .github/workflows/ci-dgraph-tests.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
name: ci-dgraph-tests
name: ci-dgraph-tests-amd64
on:
push:
branches:
Expand All @@ -16,13 +16,18 @@ on:
jobs:
dgraph-tests:
if: github.event.pull_request.draft == false
runs-on: self-hosted
runs-on: [self-hosted, x64]
steps:
- uses: actions/checkout@v3
- name: Get Go Version
run: |
#!/bin/bash
GOVERSION=$({ [ -f .go-version ] && cat .go-version; })
echo "GOVERSION=$GOVERSION" >> $GITHUB_ENV
- name: Set up Go
uses: actions/setup-go@v3
with:
go-version: 1.18
go-version: ${{ env.GOVERSION }}
- name: Set up Node
uses: actions/setup-node@v3
with:
Expand Down