Giter VIP home page Giter VIP logo

lambdatest / test-at-scale Goto Github PK

View Code? Open in Web Editor NEW
220.0 13.0 127.0 23.54 MB

TAS is an intelligent test execution platform for engineering teams to achieve high development velocity.

Home Page: https://www.lambdatest.com/test-at-scale

License: Apache License 2.0

Makefile 0.26% Dockerfile 1.01% Shell 0.21% Go 97.37% JavaScript 1.15%
test-at-scale test-intelligence test-observability smart-test-selection flaky-test-management skipped-tests testing unit-testing functional-testing test-analytics

test-at-scale's Introduction

Test At Scale

N|Solid

Test Smarter, Release Faster with test-at-scale.

Test at scale - TAS

TAS helps you accelerate your testing, shorten job times and get faster feedback on code changes, manage flaky tests and keep master green at all times.

To learn more about TAS features and capabilities, see our product page.

Features

  • Smart test selection to run only the subset of tests which get impacted by a commit โšก
  • Smart auto grouping of test to evenly distribute test execution across multiple containers based on previous execution times
  • Deep insights about test runs and execution metrics
  • Support status checks for pull requests
  • Advanced analytics to surface test performance and quality data
  • YAML driven declarative workflow management
  • Natively integrates with Github and Gitlab
  • Flexible workflow to run pre-merge and post-merge tests
  • Allows blocking and unblocking tests directly from the UI or YAML directive. No more WIP commits!
  • Support for customizing testing environment using raw commands in pre and poststeps
  • Supports Javascript monorepos
  • Smart depdency caching to speedup subsequent test runs
  • Easily customizable to support all major language and frameworks
  • Available as hosted solution as well as self-hosted opensource runner
  • [Upcoming] Smart flaky test management ๐Ÿช„

Table of contents

Getting Started

Step 1 - Setting up a New Account

In order to create an account, visit TAS Login Page. (Or TAS Home Page)

  • Login using a suitable git provider and select your organization you want to continue with.

  • Tell us your specialization, team size.

    N|Solid

  • Select TAS Self Hosted and click on Proceed.

  • You will find your LambdaTest Secret Key on this page which will be required in the next steps.

    N|Solid


Step 2 - Creating a configuration file for self hosted setup

Before installation we need to create a file that will be used for configuring test-at-scale.

  • Open any Terminal of your choice.
  • Move to your desired directory or you can create a new directory and move to it using the following command.
  • Download our sample configuration file using the given command.
mkdir ~/test-at-scale
cd ~/test-at-scale
curl https://raw.githubusercontent.com/LambdaTest/test-at-scale/main/.sample.synapse.json -o .synapse.json
  • Open the downloaded .synapse.json configuration file in any editor of your choice such as vi, nano, code, etc.

NOTE: .synapse.json file is hidden by default. You can list it using ls -la command.

  • You will need to add the following in this file:
    • 1- LambdaTest Secret Key, that you got at the end of Step 1.
    • 2- Git Token, that would be required to clone the repositories after Step 3. Generating GitHub, GitLab personal access token.
  • This file will also be used to store certain other parameters such as Repository Secrets (Optional), Container Registry (Optional) etc that might be required in configuring test-at-scale on your local/self-hosted environment. You can learn more about the configuration options here.

Step 3 - Installation

Installation on Docker

Prerequisites
Docker Compose
  • Run the docker application.

    docker info --format "CPU: {{.NCPU}}, RAM: {{.MemTotal}}"
  • Execute the above command to ensure that resources usable by Docker are atleast CPU: 2, RAM: 4294967296.

    NOTE: In order to run test-at-scale you require a minimum configuration of 2 CPU cores and 4 GiBs of RAM.

  • The .synapse.json configuration file made in Step 2 will be required before executing the next command.

  • Download and run the docker compose file using the following command.

    cd ~/test-at-scale
    curl -L https://raw.githubusercontent.com/LambdaTest/test-at-scale/main/docker-compose.yml -o docker-compose.yml
    docker-compose up -d

NOTE: This docker-compose file will pull the latest version of test-at-scale and install on your self hosted environment.

Installation without Docker Compose

To get up and running quickly, you can use the following instructions to setup Test at Scale on Self hosted environment without docker-compose.

  • The .synapse.json configuration file made in Step 2 will be required before executing the next command.
  • Execute the following command to run Test at Scale docker container
cd ~/test-at-scale
docker network create --internal test-at-scale
docker run --name synapse --restart always \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -v /tmp/synapse:/tmp/synapse \
    -v ${PWD}/.synapse.json:/home/synapse/.synapse.json \
    -v /etc/machine-id:/etc/machine-id \
    --network=test-at-scale \
    lambdatest/synapse:latest

WARNING: We strongly recommend to use docker-compose while Test at Scale on Self hosted environment.

Installation on Local Machine & Supported Cloud Platforms
  • Once the installation is complete, go back to the TAS portal.
  • Click the 'Test Connection' button to ensure test-at-scale self hosted environment is connected and ready.
  • Hit Proceed to move forward to Step 4

Step 4 - Importing your repo

NOTE: Currently we support Mocha, Jest and Jasmine for testing Javascript codebases.

  • Click the Import button for the JS repository you want to integrate with TAS.

  • Once Imported successfully, click on Go to Project to proceed further.

  • You will be asked to setup a post-merge here. We recommend to proceed ahead with default settings. (You can change these later.)

    N|Solid


Step 5 - Configuring TAS yml

A .tas.yml file is a basic yaml configuration file that contains steps required for installing necessary dependencies and executing the tests present in your repository.

  • In order to configure your imported repository, follow the steps given on the .tas.yml configuration page.

  • You can also know more about .tas.yml configuration parameters here.

    N|Solid

  • Placing the .tas.yml configuration file.

    • Create a new file as .tas.yml at the root level of your repository .
    • Copy the configuration from the TAS yml configuration page and paste them in the .tas.yml file you just created.
    • Commit and Push the changes to your repo.

    N|Solid

Language & Framework Support

Currently we support Mocha, Jest and Jasmine for testing Javascript codebases.

Tutorials

Contribute

We love our contributors! If you'd like to contribute anything from a bug fix to a feature update, start here:

Join our community

Engage with Developers, SDETs, and Testers around the world.

  • Get the latest product updates.
  • Discuss testing philosophies and more. Join the Test-at-scale Community on Discord. Click here if you are already an existing member.

Support & Troubleshooting

The documentation and community will help you troubleshoot most issues. If you have encountered a bug, you can contact us using one of the following channels:

We are committed to fostering an open and welcoming environment in the community. Please see the Code of Conduct.

License

TestAtScale is available under the Apache License 2.0. Use it wisely.

test-at-scale's People

Contributors

anmolg-lt avatar muditlambda avatar nevilm-lt avatar palashmarantas avatar phoenix24 avatar psych0der avatar rishabh-arya95 avatar sachin-rungta avatar sachinkumargit avatar saurabh-prakash avatar shahid-lt avatar shirish4 avatar shmsr avatar spot-anmol avatar utkarsh-lambdatest avatar vikrantks avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

test-at-scale's Issues

[Feature]: Websocket reconnect

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

I like to add following functionality

  • If there is network partition between synapse and lambdatest server , it should try to reconnect with exponential backoff factor
  • If lambdatest server sends auth failed message or duplicate connection message , it should exit and not retry

Why should this be worked on?

This feature improves fault tolerance

Other details

No response

[Feature]: Add support for test splitting modes

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

We need to add support for test distribution based on files as well as individual test cases.

Why should this be worked on?

Can be useful in a large repository like react where there is a large number of test files.

Other details

No response

Remove deriving of task status from nucleus

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

Task status will be derived on the server end.

Why should this be worked on?

Currently, task status is derived at the nucleus end where we iterate the results array. the

Other details

No response

[Feature]: Add unit tests for Nucleus packages

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

Add unit tests for nucleus packages

Why should this be worked on?

This offers the following:

  • improve and maintain code quality
  • increase code readability
  • improve debugging process
  • increase development velocity

Other details

No response

[Feature]: Faster Compression

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

Faster workspace compression for test runs.

Why should this be worked on?

This will speed up the testing pipeline.

Other details

No response

[Feature]: Add synapse name in config

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

Attach name to each instance of synapse

Why should this be worked on?

To add more visibility to lambdatest dashboard we can attach name to each synapse instance
This functionality will be optional , a user may opt to not add name field in synapse config

Other details

No response

[Bug]: Oauth parsing structure changes

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

Currently synapse write the OAuth in the format
{"data": {"access_token": "", "expiry": "", "refresh_token": "", "token_type": ""}}

But nucleus reads OAuth in the following format
{"access_token": "", "expiry": "", "refresh_token": "", "token_type": ""}

What is the expected behavior?

The read and write structure of OAuth should be consistent for proper functioning of synapse
Synapse write structure should be
{"access_token": "", "expiry": "", "refresh_token": "", "token_type": ""}

Steps To Reproduce

  1. Connect synapse
  2. Run a job (via adding commit)
  3. The job will fail

Version

Test-at-scale Community Edition

[Bug]: Error message not getting passed in jobInfo

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

Currently , error message is not passed if there is job failure in synapse side (possible docker issue)

What is the expected behavior?

Error message of job failure should be passed

Steps To Reproduce

Mention invalid custom Image in tas file
Run the job
The job will be failed in execution state
But the error message will not be passed and displayed in TAS server

Version

Test-at-scale Community Edition

[Bug]: CI - Linting checks are not catching issues properly

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

Though we have golangci-lint checks running, something is missing due to which common linting problems are not being caught.

What is the expected behavior?

golangci-lint should catch linting issues properly

Steps To Reproduce

  1. Make a commit with some noOp/dummy code that is >150 length on a single-line.
  2. Push it and raise a PR.
  3. golangci-lint simply passes. It should've errored out / failed.

Version

Test-at-scale Community Edition

[Feature]: Mapping for PI

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

Adding mapping of pi env to lambdatest api endpoints

Why should this be worked on?

Needed for connection with lambdatest pi env

Other details

No response

[Bug]: PreRun logs are not uploaded when the command fails

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

PreRun logs are not uploaded when the command fails

What is the expected behavior?

PreRun logs should be uploaded when the command fails and they should be viewable in TAS portal.

Steps To Reproduce

Run a repo on TAS Cloud but give a command in preRun that exits with non-zero exitCode. Observe that the logs are not shown on TAS portal

Version

Test-at-scale Cloud

[Bug]: Documentation Fixes

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

This is a Generic Issue Ticket for documentation Fixes.

What is the expected behavior?

This is a Generic Issue Ticket for documentation Fixes.

Steps To Reproduce

N/A

Version

Test-at-scale Cloud

[Feature]: Capture and send test failureReason

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

We'd like to send the failureReason for a test-case back to TAS Cloud for better UX as to why a test-case failed

Why should this be worked on?

Adding this feature gives users the ability to debug what went wrong in a failing test-case on TAS portal.

Other details

No response

[Bug]: Actual git clone is not performed

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

Actual git clone is not performed causing husky scripts (or git hooks scripts) to fail causing integration error. This is causing TAS error or test-failure while integrating repos such as docusaurus, next.js.

What is the expected behavior?

If we had performed an actual git clone, the husky commands that run as part of post install script won't fail.

Steps To Reproduce

  1. Try to integrate next.js or docusaurus repositories on TAS Cloud.
  2. in docusaurus, 2 test-cases fail. In next.js, preRun script fails.

Version

Test-at-scale Cloud

[Bug]: CPU Percentage calculation of testcases are incorrect

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

We are calculating getting the CPU percentage through underlying CPUPercent() function of psutil library which gives the averaged out percentage value since the start of the process.

What is the expected behavior?

We should track the percentage of CPU times used instead for a better estimation of CPU usage by the test-runner process. Also, the overall percentage should be <= 100% because the end-user sees it as a percentage overall irrespective of how many vCPUs the process is using.

Steps To Reproduce

  1. Run a job for react repository on TAS.
  2. Observe the very linear graph of test CPU metrics
  3. Observe the CPU percentage going beyond 100%

Version

Test-at-scale Cloud

[Bug]: No personal access token available on Bitbucket for synapse integration

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

In the case of Bitbucket cloud, there is no personal access token available. Without personal token we can not set up Synapse.

What is the expected behavior?

There should be support for the bitbucket app password instead.

Steps To Reproduce

https://community.atlassian.com/t5/Bitbucket-questions/Personal-Access-Token-for-Bitbucket-Cloud/qaq-p/677663

Version

Test-at-scale Community Edition

[Feature]: Adding auth in internal routes.

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

I want to add the query params in the internal routes, i.e buildID, repoID, orgID which creates the JWT with the secret string.

Why should this be worked on?

If there is no authorization added in the routes, anyone can call the routes of other jobs.

Other details

No response

[Feature]: Move secret masker to logging pkg

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

We need to move the masker implementation to use it inside our log initialization step ie the logger object returned by the pkg should itself do the masking for underlying log-implementations (be it zap or logrus).

Why should this be worked on?

We need to do this to prevent any accidental leakage of secrets in log files by contributors. Contributors heavily put log lines in their contributions and may accidentally write secrets.

Other details

No response

[Feature]: Make test-at-scale a valid go-module

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

Right now, this golang lib is still moduled as synapse. It should be corrected to test-at-scale for easy go-get (reusable module). Also, we can refactor TAS yml validation as a util func for reuse.

Why should this be worked on?

Want to expose the yml validation in TAS Portal readily, therefore require this refactor so that logic can be reused.

Other details

No response

[Feature]: Use docker volumes instead of mounting data on host

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

  • Store build wide shared data into docker volumes instead of using host path

Why should this be worked on?

  • Improve security
  • Better storage management

Other details

No response

[Bug]: Security issues in docker image

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

Current docker image contains lot of security related issues. We need to fix the base docker image and try to minimize vulnerability.

What is the expected behavior?

Docker image should be secure.

Steps To Reproduce

Tested for security vulnerability via docker image scan (snyk).

Version

Test-at-scale Cloud

[Feature]: Support for Github Apps

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

Replace download zip URL with zipball API as the GitHub apps do not support the current zip URL

Why should this be worked on?

To support GitHub apps

Other details

No response

[Feature]: Support for pnpm cache

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

Caching for pnpm package manager for faster execution

Why should this be worked on?

Lots of repositories are using pnpm packages ex - redux-devtools
We need to support caching for pnpm in code base for faster execution

Other details

No response

[Bug]: synapse reconnection

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

Currently synapse is not retrying just after network partition , rather it waits for certain default duration

What is the expected behavior?

Synapse should start retry connecting to lambdatest server with minimal delay (around 30-60s) after there is network partition

Steps To Reproduce

  1. connect synapse to lambdatest server
  2. disconnect the wifi

Version

Test-at-scale Community Edition

[Bug]: Retry on open connection

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

While creating connection with lambdatest server , if server sends open connection error , the synapse never retries to reconnect with server

What is the expected behavior?

It should retry even if there is open connection issue

Steps To Reproduce

  1. connect the synapse with server
  2. turn off internet connection
  3. after certain duration say 30 s , reconnect the internet

Version

Test-at-scale Community Edition

[Bug]: Issue in changing clone file name in case of github public repo

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

De to different file name then expected we are getting tas error unable to clone repo

What is the expected behavior?

Need to create different filename for private and public repo

Steps To Reproduce

Run a job on github public repo, it will fail where as private repo will run fine

Version

Test-at-scale Cloud

[Feature]: Add FTM mode in nucleus

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

Adding FTM mode in nucleus

Why should this be worked on?

Addin FTM mode in nucleus so as to run it as a separate task

Other details

No response

[Bug]: Fix custom image support

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

Even if containerImage is mentioned in tas yml the containerImage is not getting used in execution

What is the expected behavior?

The synapse should use the specify image in tas yml file for test execution

Steps To Reproduce

  1. In tas yml add containerImage: <>
  2. Commit the changes
  3. Check the synapse logs
  4. The Image which was pulled and used will not be the containerImage that we mention

Version

Test-at-scale Community Edition

[Bug]: Bitbucket, No support for downstream forked PRs

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

In bitbucket, we need forked repoSlug in order to download its commit zip or fetch the diff. Currently we don't have forkSlug available so it will give not found error.

What is the expected behavior?

Premerge job should run properly on downstream PRs too.

Steps To Reproduce

Fork your repo from a different workspace and then raise a PR

Version

Test-at-scale Cloud

[Bug]: Throw execution errors i.e out of memory , out of stack etc.

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

Not returning errors found in test execution

What is the expected behavior?

returning all errors when test execution result is null

Steps To Reproduce

add below code any of the testcase . this will cause Out of memory error
function countDown(fromNumber: Number) {
const t = new Array(1000000)
countDown(fromNumber);
}
countDown(223)

Version

Test-at-scale Cloud

[Feature]: Support for multiple container registry

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

  • Support to use privately hosted container images from different providers.
    • Azure Container Registry
    • Amazon Elastic Container Registry

Why should this be worked on?

This feature will allow users to use nucleus docker images that are privately hosted on Azure Container Registry or Amazon Elastic Container Registry.

Other details

No response

[Bug]: Cleanup commitID in testPayload

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

Cleanup commitID from testBody.

Why should this be worked on?

commitID is already going as part of outer field in DiscoveryResult and ExecutionResult. Therefore, there's no need to add it with each test-case.

Other details

No response

[Feature]: Add unit test for docker runner

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

  • Unit test for runner code base and minor refactoring
  • Fix docker stop functionality

Why should this be worked on?

These units helps in determining if there is regression introduce while updating docker package
It also fixes docker stop functionality if synapse gracefully stop

Other details

No response

[Feature]: Bitbucket Support

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

  • Support for Bitbucket as Git provider

Why should this be worked on?

It'll allow users to run their Bitbucket repos' test pipelines on TAS, Adding support for one of the largest Git providers.

Other details

No response

[Feature]: Support for multiple testing framework

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

The following features need to be added

  • Support multiple framework for a repo
  • Support for mono repos (having different sub packages and it's dependency)
  • Support for different test configuration each sub packages

Why should this be worked on?

  • There are a lot of repos who either has multiple testing framework dependency or monorepo structure

Other details

No response

[Bug]: Lint errors in tests files

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

Running golangci-lint shows many lint errors in tests files.

What is the expected behavior?

There should not be lint errors in test cases code.

Steps To Reproduce

On local use this command golangci-lint run.

Version

Test-at-scale Community Edition

[Bug]: Calling Runners process n times to run test multiple times.

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

With higher values of N. Runners is going out of memory.

What is the expected behavior?

It should work fine with higher values of N until build execution duration is <= 3 hrs.

Steps To Reproduce

Provide Higher values of N in locator config.

Version

Test-at-scale Cloud

[Bug]: Job error due to race condition in persisting vs reading workspace cache

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

Some jobs are erring out because of a race condition in when we are persisting the workspace in discovery phase vs when we are reading it in execution phase.

Discovery phase calls the /test-list API after discovery completion and it schedules the execution pods for running. However, the persisting of the workspace has still not happened yet, and therefore, if the execution pod spins up early, it doesn't find the workspace cache and exits with non-zero exitCode eventually erring out the job and causing cleanups. This cleanup will also fail the discovery pod which might be writing into the area that got cleaned up.

What is the expected behavior?

The jobs shouldn't fail.

Steps To Reproduce

  1. Load test TAS Cloud on cloudsploit repository and we observe job failures 1/5 times occasionally.

Version

Test-at-scale Cloud

[Feature]: Increase git clone timeout

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

Increase git clone timeout

Why should this be worked on?

Heavy repos that have assets in their repos take much longer than 45s to clone. Therefore, increasing the timeout is required.

Other details

No response

[Feature]: Support for execution logs files

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

Support for execution logs.

  • Each execution container that is spawned for build tasks should create a separate log file.

Why should this be worked on?

  • This would enable us to easily debug root cause for execution related errors.

Other details

No response

[Bug]: API retry not working for server side error

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

If we disconnect wifi while running build over synapse , API will not retry it as synapse proxy will throw 502 status error

What is the expected behavior?

API should retry if internet break while running build via synapse

Steps To Reproduce

  1. connect synapse
  2. trigger a build
  3. disconnect wifi
  4. check the logs of the build

Version

Test-at-scale Community Edition

[Bug]: set yaml version to default 1.0.0 if not provided

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

If version is not mention in tas yml file the build will be errored out

What is the expected behavior?

If no version is mentioned , version should 1.0.0 by default

Steps To Reproduce

  1. remove version
  2. run the build by making a commit
  3. the build should errored out

Version

Test-at-scale Community Edition

[Feature]: Give Sudo privileges to container user

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

Add container user to sudo group

Why should this be worked on?

Sudo privileges is required to install dependencies like database, browser etc to run tests.

Other details

No response

[Bug]: support for versioning in nucleus and synapse binaries

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

  • Both synapse and nucleus binaries are using 0.0.1 version.

What is the expected behavior?

  • Synapse and nucleus version should be similar to tag being used.

Steps To Reproduce

  1. Run synapse
  2. Check logs

Version

Test-at-scale Cloud

[Feature]: Add support for supporting both yml and yaml extensions

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

Adding support for supporting both yml and yaml extensions for tas configuration file.

Why should this be worked on?

If someone uses .tas.yaml extension, the build will break, so for smoother on-boarding we add support for both yaml extensions

Other details

No response

[Bug]: Build cache folder removal

Is there an existing issue for this?

  • I have searched the existing issues

What is the current behavior?

All build containers are mounting /tmp/synapse that is used to store build cache. Which is filling the storage.

What is the expected behavior?

There should be a cleanup mechanism to remove build cache files periodically.

Steps To Reproduce

  1. Run big repos multiple times.

Version

Test-at-scale Cloud

[Feature]: Refactor multiconfig code

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

Refactored multiconfig code

Why should this be worked on?

To make it more compact and increase readibility

Other details

No response

[Feature]: Aborting jobs on Synapse

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to add?

Support for aborting running jobs on synapse.

Why should this be worked on?

If a user do not want to wait for completion of the build running on the synapse, he/she will need to abort running build.

Other details

No response

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.