-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI test run does not reflect real production systems #68
Comments
test suite seems to be really unstable. Trying all cases (ruby runtest.rb -c, -c -n, -c -n -a) on Ubuntu 14.04, Fedora 23, Fedora 23 with make 3.81 in I wish I had at least one combination with 0 :-/ |
Now runtest.rb sets SHELL=/bin/bash and "ln -sf /bin/bash /bin/sh" was removed from the travis CI setting: fc24bd2 I also made a bunch of changes for GNU make 4. Hopefully these changes mitigate your issue? |
Your latest changes improve the situation somewhat. "ruby runtest.rb -c" now passes on my Ubunut 14.04 machine. But other tests can still fail, I think there is something wrong with handling of echo handling when using ninja?
|
Could you tell me the result of
For me, the output is
The line with "FAILED:" should be removed by https://github.com/google/kati/blob/master/runtest.rb#L114 . But it looks like your ninja doesn't have the FAILED: prefix? |
I have two lines, where you have one line:
Maybe you are not using upstream master of ninja? |
Ah, it seems very recent ninja outputs two lines. The above change works? |
Yes, on Ubuntu 14.04 (make 3.81 in $PATH) and Fedora 23 (make 4.0 in $PATH) I now get passing result for -c, -c -n and -c -n -a Closing this issue. |
No wonder that I can't even get passing tests on Ubuntu 14.04. The CI test has a hard-coded
which normal users aren't allowed on production systems. It's a bad idea anyway, because it would corrupt the Ubuntu installation.
IMHO the test cases and/or test runner needs to be updated to use /bin/bash everywhere.
The text was updated successfully, but these errors were encountered: