bug test_git_update avec git branc réparé

This commit is contained in:
eleonore12345 2024-07-12 18:49:24 +02:00
parent a09a3c1e72
commit 5a2a1e10c7
2 changed files with 8 additions and 8 deletions

View File

@ -1,4 +1,4 @@
## Testing of differeng cloning methods ## Testing of different cloning methods
Our objective is to find the least-consuming method in terms of memory and bandwidth resources. Our objective is to find the least-consuming method in terms of memory and bandwidth resources.
We are interested in cloning one specific state of the repository. We are not interested in its history or the possibility to change it from the server where it has been cloned. The first step is done by the script creation_repo.sh which creates an adequate repository to act as a local remote. The testing in itself is done by performance_tests.sh. We are interested in cloning one specific state of the repository. We are not interested in its history or the possibility to change it from the server where it has been cloned. The first step is done by the script creation_repo.sh which creates an adequate repository to act as a local remote. The testing in itself is done by performance_tests.sh.
@ -57,7 +57,7 @@ OPTIONS
-n number executes test number -n number executes test number
-h prints the help. -h prints the help.
DESCRIPTION DESCRIPTION
This script is in writing. It allows you to measure memory and bandwidth usage. The first four test different cloning methods. Te following apply changes to the local remote before testing fetching and merging commands. This script allows you to measure memory and bandwidth usage. The first five test different cloning methods. Te following apply changes to the local remote before testing fetching and merging commands.
TEST0: classic cloning TEST0: classic cloning
TEST1: --single-branch cloning TEST1: --single-branch cloning
TEST2: --depth=1 --no-single-branch cloning TEST2: --depth=1 --no-single-branch cloning
@ -95,4 +95,4 @@ DESCRIPTION
TEST27: --depth=1 fetching+merging -s ours with reflog and gc after addition of a 1M file TEST27: --depth=1 fetching+merging -s ours with reflog and gc after addition of a 1M file
TEST28: --depth=1 fetching+merging -s ours with reflog and gc after removal of a 1M file TEST28: --depth=1 fetching+merging -s ours with reflog and gc after removal of a 1M file
TEST29: --depth=1 fetching+merging -s ours with reflog and gc after addition then removal of a 1M file" TEST29: --depth=1 fetching+merging -s ours with reflog and gc after addition then removal of a 1M file"

View File

@ -79,8 +79,8 @@ history_check(){
tag_check(){ tag_check(){
local repo_name=$1 local repo_name=$1
cd $repo_name cd $repo_name
run $(git branch) > res git branch > res
if [ $(grep "no branch" res | wc -l) = 1 ];then if [ $(grep "no branch" res | wc -l) = 1 ]; then
echo "The tag instruction has been respected" echo "The tag instruction has been respected"
tag_result=0 tag_result=0
else else
@ -92,8 +92,8 @@ tag_check(){
branch_check(){ branch_check(){
local repo_name=$1 local repo_name=$1
run cd $repo_name run cd $repo_name
run $(git branch) > res git branch > res
if [ $(grep $BRANCH_NAME res | wc -l) = 1 ];then if [ $(grep $BRANCH_NAME res | wc -l) = 1 ];then
echo "The branch instruction has been respected" echo "The branch instruction has been respected"
branch_result=0 branch_result=0
@ -212,7 +212,7 @@ test3(){
TEST4(){ TEST4(){
#CASE 4: git updated ff #CASE 4: git updated ff
section TEST4 section TEST4
} }