Harshavardhana
5 years ago
committed by
kannappanr
parent
c260182412
commit
ef1aa870c5
@ -1,4 +0,0 @@ |
|||||||
{ |
|
||||||
"numFilesToCheck": 10, |
|
||||||
"requiredOrgs": ["minio"] |
|
||||||
} |
|
||||||
@ -1,67 +0,0 @@ |
|||||||
#!/bin/bash |
|
||||||
|
|
||||||
# usage: ./benchcmp.sh <commit-sha1> <commit-sha2> |
|
||||||
# Exit on any non zero return value on execution of a command. |
|
||||||
set -e |
|
||||||
|
|
||||||
# path of benchcmp. |
|
||||||
benchcmp=${GOPATH}/bin/benchcmp |
|
||||||
|
|
||||||
# function which runs the benchmark comparison. |
|
||||||
RunBenchCmp () { |
|
||||||
# Path for storing output of benchmark at commit 1. |
|
||||||
commit1Bench=/tmp/minio-$1.bench |
|
||||||
# Path for storing output of benchmark at commit 2. |
|
||||||
commit2Bench=/tmp/minio-$2.bench |
|
||||||
# switch to commit $1. |
|
||||||
git checkout $1 |
|
||||||
# Check if the benchmark results for given commit 1 already exists. |
|
||||||
# Benchmarks are time/resource consuming operations, run only if the the results doesn't exist. |
|
||||||
if [[ ! -f $commit1Bench ]] |
|
||||||
then |
|
||||||
|
|
||||||
echo "Running benchmarks at $1" |
|
||||||
go test -run=NONE -bench=. | tee $commit1Bench |
|
||||||
fi |
|
||||||
# get back to the commit from which it was started. |
|
||||||
git checkout - |
|
||||||
echo "Checking into commit $2" |
|
||||||
# switch to commit $2 |
|
||||||
git checkout $2 |
|
||||||
# Check if the benchmark results for given commit 2 already exists. |
|
||||||
# Benchmarks are time/resource consuming operations, run only if the the results doesn't exist. |
|
||||||
if [[ ! -f $commit2Bench ]] |
|
||||||
then |
|
||||||
# Running benchmarks at $2. |
|
||||||
echo "Running benchmarks at $2" |
|
||||||
go test -run=NONE -bench=. | tee $commit2Bench |
|
||||||
fi |
|
||||||
|
|
||||||
# get back to the commit from which it was started. |
|
||||||
git checkout - |
|
||||||
# Comparing the benchmarks. |
|
||||||
echo "Running benchmark comparison between $1 and $2 ..." |
|
||||||
$benchcmp $commit1Bench $commit2Bench |
|
||||||
echo "Done." |
|
||||||
} |
|
||||||
|
|
||||||
# check if 2 commit SHA's of snapshots of code for which benchmp has to be done is provided. |
|
||||||
if [ ! $# -eq 2 ] |
|
||||||
then |
|
||||||
# exit if commit SHA's are not provided. |
|
||||||
echo $# |
|
||||||
echo "Need Commit SHA's of 2 snapshots to be supplied to run benchmark comparison." |
|
||||||
exit 1 |
|
||||||
fi |
|
||||||
|
|
||||||
# check if benchcmp exists. |
|
||||||
if [[ -x "$benchcmp" ]] |
|
||||||
then |
|
||||||
RunBenchCmp $1 $2 |
|
||||||
else |
|
||||||
# install benchcmp if doesnt't exist. |
|
||||||
echo "fetching Benchcmp..." |
|
||||||
go get -u golang.org/x/tools/cmd/benchcmp |
|
||||||
echo "Done." |
|
||||||
RunBenchCmp $1 $2 |
|
||||||
fi |
|
||||||
@ -0,0 +1,80 @@ |
|||||||
|
# Contributor Covenant Code of Conduct |
||||||
|
|
||||||
|
## Our Pledge |
||||||
|
|
||||||
|
In the interest of fostering an open and welcoming environment, we as |
||||||
|
contributors and maintainers pledge to making participation in our project and |
||||||
|
our community a harassment-free experience for everyone, regardless of age, body |
||||||
|
size, disability, ethnicity, gender identity and expression, level of experience, |
||||||
|
nationality, personal appearance, race, religion, or sexual identity and |
||||||
|
orientation. |
||||||
|
|
||||||
|
## Our Standards |
||||||
|
|
||||||
|
Examples of behavior that contributes to creating a positive environment |
||||||
|
include: |
||||||
|
|
||||||
|
* Using welcoming and inclusive language |
||||||
|
* Being respectful of differing viewpoints and experiences |
||||||
|
* Gracefully accepting constructive criticism |
||||||
|
* Focusing on what is best for the community |
||||||
|
* Showing empathy towards other community members |
||||||
|
|
||||||
|
Examples of unacceptable behavior by participants include: |
||||||
|
|
||||||
|
* The use of sexualized language or imagery and unwelcome sexual attention or |
||||||
|
advances |
||||||
|
* Trolling, insulting/derogatory comments, and personal or political attacks |
||||||
|
* Public or private harassment |
||||||
|
* Publishing others' private information, such as a physical or electronic |
||||||
|
address, without explicit permission |
||||||
|
* Other conduct which could reasonably be considered inappropriate in a |
||||||
|
professional setting |
||||||
|
|
||||||
|
## Our Responsibilities |
||||||
|
|
||||||
|
Project maintainers are responsible for clarifying the standards of acceptable |
||||||
|
behavior and are expected to take appropriate and fair corrective action in |
||||||
|
response to any instances of unacceptable behavior, in compliance with the |
||||||
|
licensing terms applying to the Project developments. |
||||||
|
|
||||||
|
Project maintainers have the right and responsibility to remove, edit, or |
||||||
|
reject comments, commits, code, wiki edits, issues, and other contributions |
||||||
|
that are not aligned to this Code of Conduct, or to ban temporarily or |
||||||
|
permanently any contributor for other behaviors that they deem inappropriate, |
||||||
|
threatening, offensive, or harmful. However, these actions shall respect the |
||||||
|
licensing terms of the Project Developments that will always supersede such |
||||||
|
Code of Conduct. |
||||||
|
|
||||||
|
## Scope |
||||||
|
|
||||||
|
This Code of Conduct applies both within project spaces and in public spaces |
||||||
|
when an individual is representing the project or its community. Examples of |
||||||
|
representing a project or community include using an official project e-mail |
||||||
|
address, posting via an official social media account, or acting as an appointed |
||||||
|
representative at an online or offline event. Representation of a project may be |
||||||
|
further defined and clarified by project maintainers. |
||||||
|
|
||||||
|
## Enforcement |
||||||
|
|
||||||
|
Instances of abusive, harassing, or otherwise unacceptable behavior may be |
||||||
|
reported by contacting the project team at dev@min.io. The project team |
||||||
|
will review and investigate all complaints, and will respond in a way that it deems |
||||||
|
appropriate to the circumstances. The project team is obligated to maintain |
||||||
|
confidentiality with regard to the reporter of an incident. |
||||||
|
Further details of specific enforcement policies may be posted separately. |
||||||
|
|
||||||
|
Project maintainers who do not follow or enforce the Code of Conduct in good |
||||||
|
faith may face temporary or permanent repercussions as determined by other |
||||||
|
members of the project's leadership. |
||||||
|
|
||||||
|
## Attribution |
||||||
|
|
||||||
|
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, |
||||||
|
available at [http://contributor-covenant.org/version/1/4][version] |
||||||
|
|
||||||
|
This version includes a clarification to ensure that the code of conduct is in |
||||||
|
compliance with the free software licensing terms of the project. |
||||||
|
|
||||||
|
[homepage]: http://contributor-covenant.org |
||||||
|
[version]: http://contributor-covenant.org/version/1/4/ |
||||||
Loading…
Reference in new issue