Hi guys, I hope you don't mind me posting this to devel.
So I built nodejs module today (Friday) [1], went over to taskotron interface
to see if tests were executed [2]. Unfortunately, the tests [3] we have present
in the module dist-git were not triggered. Why?
It would be awesome if I could execute a command locally which would trigger
testing process inside taskotron. This way I could make sure the tests get
picked up correctly -- I definitely don't want to do rebuilds just for sake of
trying out tests.
The second question is about test test_component_profile_installability. Logs
[3] say this:
11:58:56 INFO | Command 'machinectl shell root(a)bash_1497613819.523692 /bin/bash -c
"(rpm -q --qf='%{name}\n' nodejs)>/var/tmp/stdout 2>/var/tmp/stderr;
echo $?>/var/tmp/retcode; sleep 1" ' finished with 0 after 1.07665395737s
11:58:56 INFO | Running 'bash -c "cat
/opt/chroot_bash_1497613819.523692/var/tmp/stdout; cat
/opt/chroot_bash_1497613819.523692/var/tmp/stderr > /dev/stderr; exit `cat
/opt/chroot_bash_1497613819.523692/var/tmp/retcode`"'
11:58:56 DEBUG| [stdout] package nodejs is not installed
I understand that as a failure, but the test is marked as passed, can you
clarify? Also, what install profiles are you trying out? Would be awesome to
try installing every instal profile.
[1]
https://pdc.fedoraproject.org/rest_api/v1/unreleasedvariants/?variant_uid...
[1]
https://taskotron.fedoraproject.org/artifacts/all/b1243986-5289-11e7-b49b...
[2]
http://pkgs.fedoraproject.org/cgit/modules/nodejs.git/tree/tests?h=f26
[4]
https://taskotron.fedoraproject.org/artifacts/all/b1243986-5289-11e7-b49b...
Looking forward to the enlightenment,
Tomas