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.

Sign up for GitHub

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

Jump to bottom

Should be able to run the tests on balenaCI #582

Open
thgreasi opened this issue Sep 28, 2018 · 0 comments · May be fixed by #584
Open

Should be able to run the tests on balenaCI #582

thgreasi opened this issue Sep 28, 2018 · 0 comments · May be fixed by #584
Assignees
@thgreasi

Comments

@thgreasi
Copy link
Member

thgreasi commented Sep 28, 2018 •
edited
Loading

Arch call discussions:
See: https://app.frontapp.com/open/cnv_1ha7dkz use sandboxed accounts for tests
See: https://github.com/balena-io/balena-api/issues/2558
See: https://app.frontapp.com/open/cnv_13stakz signup for a new user on each run of the suite & bypass ratelimiting on balenaCI
@thgreasi thgreasi self-assigned this Sep 28, 2018
@thgreasi thgreasi changed the title Should be able to run test on ResinCI Should be able to run the tests on ResinCI Sep 28, 2018
thgreasi added a commit that referenced this issue Oct 1, 2018
@thgreasi
chore: Add headless Chrome parameters to work on ResinCi
0c0240a 
Resolves: #582
Change-type: patch
See: product-os/balena-concourse#248
See: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md#running-on-alpine
Signed-off-by: Thodoris Greasidis <[email protected]>
@thgreasi thgreasi linked a pull request Oct 1, 2018 that will close this issue
Open
@thgreasi thgreasi mentioned this issue Nov 24, 2019
Closed
@thgreasi thgreasi changed the title Should be able to run the tests on ResinCI Should be able to run the tests on balenaCI Nov 24, 2019
@thgreasi thgreasi mentioned this issue Nov 24, 2019
Closed
thgreasi added a commit that referenced this issue Feb 5, 2020
@thgreasi
Disable balenaCI auto rebase
597c76a 
Having autorebase enabled could lead to having
more then one instances of the sdk tests running in
parallel, which will result all of them failing, b/c they
will use the same test user, and will also add
unnecessary load to the API. Once we get #582 fixed
we can remove this.

Change-type: patch
See: product-os/scripts#80
Signed-off-by: Thodoris Greasidis <[email protected]>
@thgreasi thgreasi mentioned this issue Feb 5, 2020
Merged
4 tasks
thgreasi added a commit that referenced this issue Feb 6, 2020
@thgreasi
Disable balenaCI auto rebase
e3b7cb0 
Having autorebase enabled could lead to having
more then one instances of the sdk tests running in
parallel, which will result all of them failing, b/c they
will use the same test user, and will also add
unnecessary load to the API. Once we get #582 fixed
we can remove this.

Change-type: patch
See: product-os/scripts#80
Signed-off-by: Thodoris Greasidis <[email protected]>
thgreasi added a commit that referenced this issue Feb 6, 2020
@thgreasi
Disable balenaCI auto rebase
a30a648 
Having autorebase enabled could lead to having
more then one instances of the sdk tests running in
parallel, which will result all of them failing, b/c they
will use the same test user, and will also add
unnecessary load to the API. Once we get #582 fixed
we can remove this.

Change-type: patch
See: product-os/scripts#80
Signed-off-by: Thodoris Greasidis <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@thgreasi thgreasi

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

tests: Use a random test user when no env vars are present balena-io/balena-sdk
1 participant
@thgreasi