On 7/12/21 5:10 PM, David Marchand wrote: > On Mon, Jul 12, 2021 at 4:43 PM Ilya Maximets <i.maxim...@ovn.org> wrote: >>>> ovsrobot has issues with reporting the status right now, but this >>>> patch fails the build in GHA: >>>> https://github.com/ovsrobot/ovs/actions/runs/1021787643 >>> >>> Thanks for linking on results. >>> >>> I've spot-checked a bunch of the failing builds, and found 2 fixable code >>> issues. >>> A few of the CI run's I can't find/explain the error, but I don't know of a >>> good >>> way to "jump to the error" line, am I missing a trick, or is scrolling the >>> whole >>> compiler output and checking errors the best method? >> >> typing 'error:' in the 'Search logs' field, usually gets you >> to the actual error faster, but, unfortunately, scrolling is >> the most reliable option. > > GHA ui jumps at the last line of a failing step, but the problem is > that, in OVS, we dump all logs which adds a lot of noise. > > We could stop dumping them, since those logs are attached to the job > as an archive. > Like what is done in DPDK. > http://git.dpdk.org/dpdk/tree/.ci/linux-build.sh#n3 > > WDYT?
Yes, that is good thing to do. We didn't do that because of Travis CI, where we have no artifacts collected. But yes, checking for [ -n "$GITHUB_WORKFLOW" ] is a solution. Best regards, Ilya Maximets. _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
