[1.0.1] Tests fails with segfault
Nessuno ha ancora preso questa issue.
- Lingua principale
- C
- Stelle
- 10.6k
- Fork
- 2.7k
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
Here the log:
Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.XKeCwv
- umask 022
- cd /builddir/build/BUILD
~/build/BUILD/libgit2-1.0.1/my_build ~/build/BUILD/libgit2-1.0.1- cd libgit2-1.0.1
- pushd my_build
- ctest3 -V -j8 ..
UpdateCTestConfiguration from :/builddir/build/BUILD/libgit2-1.0.1/my_build/DartConfiguration.tcl
UpdateCTestConfiguration from :/builddir/build/BUILD/libgit2-1.0.1/my_build/DartConfiguration.tcl
Test project /builddir/build/BUILD/libgit2-1.0.1/my_build
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 1
Start 1: offline1: Test command: /builddir/build/BUILD/libgit2-1.0.1/my_build/libgit2_clar "-v" "-xonline"
1: Test timeout computed to be: 10000000
test 2
Start 2: invasive2: Test command: /builddir/build/BUILD/libgit2-1.0.1/my_build/libgit2_clar "-v" "-score::ftruncate" "-sfilter::stream::bigfile" "-sodb::largefiles" "-siterator::workdir::filesystem_gunk" "-srepo::init" "-srepo::init::at_filesystem_root"
2: Test timeout computed to be: 10000000
test 3
Start 3: online3: Test command: /builddir/build/BUILD/libgit2-1.0.1/my_build/libgit2_clar "-v" "-sonline"
3: Test timeout computed to be: 10000000
test 4
Start 4: gitdaemon4: Test command: /builddir/build/BUILD/libgit2-1.0.1/my_build/libgit2_clar "-v" "-sonline::push"
4: Test timeout computed to be: 10000000
test 5
Start 5: ssh5: Test command: /builddir/build/BUILD/libgit2-1.0.1/my_build/libgit2_clar "-v" "-sonline::push" "-sonline::clone::ssh_cert" "-sonline::clone::ssh_with_paths" "-sonline::clone::path_whitespace_ssh"
5: Test timeout computed to be: 10000000
test 6
Start 6: proxy6: Test command: /builddir/build/BUILD/libgit2-1.0.1/my_build/libgit2_clar "-v" "-sonline::clone::proxy"
6: Test timeout computed to be: 10000000
test 7
Start 7: auth_clone7: Test command: /builddir/build/BUILD/libgit2-1.0.1/my_build/libgit2_clar "-v" "-sonline::clone::cred"
7: Test timeout computed to be: 10000000
test 8
Start 8: auth_clone_and_push8: Test command: /builddir/build/BUILD/libgit2-1.0.1/my_build/libgit2_clar "-v" "-sonline::clone::push" "-sonline::push"
8: Test timeout computed to be: 10000000
2: Loaded 385 suites:
2: Started (test status codes: OK='.' FAILURE='F' SKIPPED='S')
2:
2: core::ftruncateSS
6: Loaded 385 suites:
6: Started (test status codes: OK='.' FAILURE='F' SKIPPED='S')
6:
2: filter::streamS
1/8 Test #7: auth_clone .......................***Exception: SegFault 0.03 sec
6: online::cloneSSS
2/8 Test #6: proxy ............................***Exception: SegFault 0.03 sec
4: Loaded 385 suites:
4: Started (test status codes: OK='.' FAILURE='F' SKIPPED='S')
4:
3/8 Test #1: offline ..........................***Exception: SegFault 0.04 sec
8: Loaded 385 suites:
8: Started (test status codes: OK='.' FAILURE='F' SKIPPED='S')
8:
8: online::clone
5: Loaded 385 suites:
5: Started (test status codes: OK='.' FAILURE='F' SKIPPED='S')
5:
4/8 Test #3: online ...........................***Exception: SegFault 0.05 sec
2: odb::largefilesSSSSSS
2: iterator::workdirS
5/8 Test #2: invasive .........................***Exception: SegFault 0.09 sec
4: online::pushSSSSSSSSSSSSSSSSSSSSS
4:
6/8 Test #4: gitdaemon ........................ Passed 0.34 sec
8: online::pushSSSSSSSSSSSSSSSSSSSSS
8:
7/8 Test #8: auth_clone_and_push .............. Passed 0.34 sec
5: online::pushSSSSSSSSSSSSSSSSSSSSS
5: online::cloneS
5: online::cloneS
5: online::clone
5:
8/8 Test #5: ssh .............................. Passed 0.35 sec38% tests passed, 5 tests failed out of 8
Total Test time (real) = 0.36 sec
The following tests FAILED:
1 - offline (SEGFAULT)
2 - invasive (SEGFAULT)
3 - online (SEGFAULT)
6 - proxy (SEGFAULT)
7 - auth_clone (SEGFAULT)
Errors while running CTest
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Inizia riproducendo il problema con ctest3 -V -j8 .. dalla directory my_build, usando il log di build collegato e i comandi libgit2_clar come punti di ingresso. Confronta le suite che falliscono offline, invasive, online, proxy e auth_clone con le suite che hanno esito positivo gitdaemon, ssh e auth_clone_and_push. Il lavoro è completato quando i test interessati non causano più un segmentation fault e l’esecuzione completa di CTest ha esito positivo.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- c
- Ambito
- testing-qa
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100