Project

Profile

Help

Task #7161

Non obvious decision about build status

Added by Mark Zaslavskiy almost 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
High
Assignee:
Timofey Turenko
Category:
mariadb testing
Sprint/Milestone:
Start date:
29.06.2016
Due date:
% Done:

0%

Estimated time:
2:00 h
Target branch:
Test scenario:

Added file scripts/build_parser/README.md which describes how to setup DB from the scratch and setup password file.

http://maxscale-jenkins.mariadb.com:8090/job/mdbci_integration_test/372/


Description

See attached log.

consoleText.txt (497 KB) consoleText.txt Mark Zaslavskiy, 29.06.2016 14:33

History

#1 Updated by Mark Zaslavskiy almost 5 years ago

  • Estimated time set to 2:00 h

#2 Updated by Mark Zaslavskiy almost 5 years ago

  • Status changed from New to Active / In progress

#3 Updated by Mark Zaslavskiy almost 5 years ago

162: maxscale_IP: 192.168.121.129
162: cp: kan inte ta status på ”/tmp/core*”: Filen eller katalogen finns inte
162: Logs publish dir is /home/turenko/LOGS/20160624-20/avro1/2.0.0-jun20-debug/
162: 212.236195: fl = 0
162: 212.236204: TEST_FAILED! not enough lines in avrocheck output
162: 213.983873: Executing /home/turenko/.jenkins/jobs/run_test/workspace/copy_logs.sh avro
162: 214.719176: copy_logs.sh OK!
1/1 Test #162: avro .............................***Failed 254.90 sec

0% tests passed, 1 tests failed out of 1

Total Test time (real) = 255.19 sec

The following tests FAILED:
162 - avro (Failed)

#4 Updated by Mark Zaslavskiy almost 5 years ago

Uploaded: /home/turenko/.jenkins/jobs/run_test/workspace/Testing/20160624-0100/Test.xml
Upload file: /home/turenko/.jenkins/jobs/run_test/workspace/Testing/20160624-0100/Update.xml to http://jenkins.engskysql.com/CDash/submit.php?project=MaxScale&FileName=turenko-home___avro1___20160624-0100-Nightly___XML___Update.xml&MD5=67bc84001d33a88ba904db07b319d450 Size: 637
Uploaded: /home/turenko/.jenkins/jobs/run_test/workspace/Testing/20160624-0100/Update.xml
Submission successful
Errors while running CTest

#5 Updated by Mark Zaslavskiy almost 5 years ago

  • Status changed from Active / In progress to Testing
  • Assignee changed from Mark Zaslavskiy to Timofey Turenko
  • Test scenario updated (diff)

#6 Updated by Mark Zaslavskiy almost 5 years ago

14:08]
timofey.turenko по поводу https://dev.osll.ru/issues/7161: run_test.sh завершаеться успехом, я включил отладку:

[14:09]
Errors while running CTest
+ rsync -a LOGS /home/turenko/LOGS/run_test-207
+ chmod a+r /home/turenko/LOGS/run_test-207/LOGS
+ cd /home/turenko/mdbci/jun12
+ '[' yes '!=' yes ']'

[14:09]
вот код в конце run_test.sh

[14:09]
rsync -a LOGS $logs_publish_dir
chmod a+r $logs_publish_dir/*

else
vagrant destroy -f
rm ~/vagrant_lock
exit 1
fi

cd ~/mdbci/$name
if [ "$do_not_destroy_vm" != "yes" ] ; then
vagrant destroy -f
fi

[14:11]
последнее что выполнилось - if [ "$do_not_destroy_vm" != "yes" ] ; then, условие не сработало, скрип завершился

[14:11]
а вот дальше по логу дженкинса:

[14:11]
"/tmp/hudson425946994343557745.sh: 2: /tmp/hudson425946994343557745.sh: Bad substitution
Build step 'Execute shell' marked build as failure"

[14:13]
что может быть не так тут?

[14:13]
~/build-scripts/test/run_test.sh | tee $WORKSPACE/build_log_$BUILD_ID; echo ${PIPESTATUS0} > result_$BUILD_ID

#7 Updated by Mark Zaslavskiy almost 5 years ago

  • Status changed from Testing to Active / In progress
  • Assignee changed from Timofey Turenko to Mark Zaslavskiy

#8 Updated by Mark Zaslavskiy almost 5 years ago

  • Status changed from Active / In progress to Testing
  • Assignee changed from Mark Zaslavskiy to Timofey Turenko

Possible reasons:
- something at ~/build-scripts/test/run_test.sh | tee $WORKSPACE/build_log_$BUILD_ID; echo ${PIPESTATUS0} > result_$BUILD_ID
- default interpretier differ from /bin/bash

#9 Updated by Mark Zaslavskiy almost 5 years ago

  • Status changed from Testing to Active / In progress
  • Assignee changed from Timofey Turenko to Mark Zaslavskiy

#10 Updated by Timofey Turenko almost 5 years ago

added #!bin/bash

after it got error that mysql2 ruby gem is missing, installed it

got access to db denied error

added user test_bot to DB, waiting for test results (I suspect there will be error - missing tables).

Following to be fixed:
- add requirement for mysql2 gem to the MDBCI documentation
- get rid of hardcoded username and password in write_build_results.rb and 'show result' Jenkins job (should it be in the separate file?)
- add requirement for DB access to the MDBCI documentation and add description "how to configure DB'
- check the possibility to create results DB and tables automatically if they do not exist

- probably check for mysql errors in write_build_results.rb

#11 Updated by Mark Zaslavskiy almost 5 years ago

  • Status changed from Active / In progress to New

#12 Updated by Mark Zaslavskiy almost 5 years ago

  • Priority changed from Normal to High

#13 Updated by Mark Zaslavskiy almost 5 years ago

Last requirement moved to separated task https://dev.osll.ru/issues/7225

#16 Updated by Mark Zaslavskiy almost 5 years ago

  • Test scenario updated (diff)

#17 Updated by Mark Zaslavskiy almost 5 years ago

  • Status changed from New to Review

#18 Updated by Mark Zaslavskiy almost 5 years ago

  • Status changed from Review to Testing

#19 Updated by Mark Zaslavskiy almost 5 years ago

  • Assignee changed from Mark Zaslavskiy to Timofey Turenko

#20 Updated by Timofey Turenko almost 5 years ago

  • Status changed from Testing to Closed

Also available in: Atom PDF