| commit | bcd3590c727addc1515a6769e49d865e82112b28 | [log] [tgz] |
|---|---|---|
| author | Marco Miller <marco.miller@ericsson.com> | Mon Apr 06 17:44:03 2020 -0400 |
| committer | Marco Miller <marco.miller@ericsson.com> | Thu Apr 09 16:42:23 2020 -0400 |
| tree | 3d84b60f0395905332fe85c3ae9332afe71f336d | |
| parent | 48e46a9fdc920abbc346f9de24a480a669f36e99 [diff] |
e2e-tests: Stabilize the ReplayRecordsFromFeeder scenario Set the number of repetitions to the maximum order of magnitude that works locally. Setting that number to >10 led to locally crashing with exception traces. Using higher numbers mostly led to no Gatling report generated or failure to generate it (out of exceptions). Replacing 'repeat' with 'forever' led to reaching a crashing state as well. Remove the pull and push commands from the scenario. Either one of these in led to more Gatling KOs than OKs; often only KOs were obtained (red). Basically stabilize that scenario, until further scenarios using git pull, push and/or more load can be steadily developed. Goal being, to be able to reproduce successful executions of such introductory core scenarios. External harnessing, if any, is to be included just as well. The exception below can still often be seen when running this test locally, but it doesn't prevent the scenario from reporting OKs (green). [JGit-WorkQueue] ERROR o.e.j.internal.storage.file.LockFile - Unlocking LockFile '/tmp/gatling-1586283237616/609/ loadtest-repo-worktree/.git/gc.log.lock' failed java.io.IOException: Could not delete file /tmp/gatling-1586283237616/609/loadtest-repo-worktree/.git/gc.log.lock at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:219) at org.eclipse.jgit.internal.storage.file.LockFile.unlock(LockFile.java:520) at org.eclipse.jgit.internal.storage.file.GcLog.unlock(GcLog.java:143) at org.eclipse.jgit.internal.storage.file.GC.lambda$0(GC.java:279) (...) Bug: Issue 12332 Change-Id: Ifb332276b9650ac7a4133f2fe35b9ae36c615c9d
Gerrit is a code review and project management tool for Git based projects.
Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.
Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.
For information about how to install and use Gerrit, refer to the documentation.
Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.
Please report bugs on the issue tracker.
Gerrit is the work of hundreds of contributors. We appreciate your help!
Please read the contribution guidelines.
Note that we do not accept Pull Requests via the Github mirror.
The Developer Mailing list is repo-discuss on Google Groups.
Gerrit is provided under the Apache License 2.0.
Install Bazel and run the following:
git clone --recurse-submodules https://gerrit.googlesource.com/gerrit
cd gerrit && bazel build release
The instruction how to configure GerritForge/BinTray repositories is here
On Debian/Ubuntu run:
apt-get update & apt-get install gerrit=<version>-<release>
NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.
On CentOS/RedHat run:
yum clean all && yum install gerrit-<version>[-<release>]
On Fedora run:
dnf clean all && dnf install gerrit-<version>[-<release>]
Docker images of Gerrit are available on DockerHub
To run a CentOS 7 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-centos7[:version]
To run a Ubuntu 15.04 based Gerrit image:
docker run -p 8080:8080 gerritforge/gerrit-ubuntu15.04[:version]
NOTE: release is optional. Last released package of the version is installed if the release number is omitted.