ci_template: blacklist a problematic test in check

Also pass --dump-on-failure in the job. While the logs are
artifacts and they are integrated in the MRs, its not as
convinient to findout out what is failling if you are looking
into just a job log, of a commit. Thus make it show logs are also
priting on stdout/stderr.
This commit is contained in:
Jordan Petridis 2018-12-10 20:35:29 +02:00
parent 830507f202
commit a529757dec
No known key found for this signature in database
GPG key ID: 902CC06D159744F5

View file

@ -125,12 +125,14 @@ build android arm64 api28:
# note the -b at the start of each line
# Can't comment inline sadly
# FIXME: get this into gst-validate-launcher KNOWN_ISSUES
# check.gst-plugins-base.elements_multisocketsink.test_sending_buffers_with_9_gstmemories: https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/525
# souphttpsrc.test_icy_stream: https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/307
# h264parse: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/842
# rtspserver.test_shared_tcp: https://gitlab.freedesktop.org/gstreamer/gst-rtsp-server/issues/54
# dtls: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/811
# mpegtsmux.test_align: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/844
BLACKLIST: >
-b check.gst-plugins-base.elements_multisocketsink.test_sending_buffers_with_9_gstmemories
-b check.gst-plugins-good.elements_souphttpsrc.test_icy_stream
-b check.gst-plugins-bad.elements_h264parse.test_parse_packetized
-b check.gst-plugins-bad.elements_dtls.test_data_transfer
@ -146,6 +148,7 @@ build android arm64 api28:
--mute
--shuffle
--no-display
--dump-on-failure
--meson-no-rebuild
-M "${CI_PROJECT_DIR}/validate-output/"
--xunit-file "${CI_PROJECT_DIR}/validate-output/logs/xunit.xml"