github: Add a draft GitHub actions CI job#303
Merged
Conversation
Just running build+test for now with GCC.
Using the same approach as 38df191. This should fix the GCC build in the newly added -Werror github action. ``` In file included from ../target/arm/gdbstub64.c:21: ../target/arm/gdbstub64.c: In function ‘aarch64_cpu_gdb_write_register’: ../target/arm/cpu.h:3652:14: error: array subscript 31 is above array bounds of ‘uint32_t[16]’ {aka ‘unsigned int[16]’} [-Werror=array-bounds] 3652 | env->regs[regnum] = value; | ~~~~~~~~~^~~~~~~~ In file included from ../target/arm/gdbstub64.c:21: ../target/arm/cpu.h:263:14: note: while referencing ‘regs’ 263 | uint32_t regs[16]; | ^~~~ In file included from ../target/arm/gdbstub64.c:21: ../target/arm/cpu.h:3653:43: error: array subscript 31 is above array bounds of ‘const char * const[16]’ [-Werror=array-bounds] 3653 | qemu_log_instr_reg(env, arm32_regnames[regnum], value, regnum, | ~~~~~~~~~~~~~~^~~~~~~~ In file included from ../target/arm/gdbstub64.c:21: ../target/arm/cpu.h:250:27: note: while referencing ‘arm32_regnames’ 250 | extern const char * const arm32_regnames[16]; | ^~~~~~~~~~~~~~ cc1: all warnings being treated as errors ```
The perl test harness is not necessary anymore since commit 3d2f73e ("build: use "meson test" as the test harness"). Thus remove it from tests/lcitool/projects/qemu.yml, run "make lcitool-refresh" and manually clean the remaining docker / vm files that are not managed by lcitool yet. Message-Id: <20220329102808.423681-1-thuth@redhat.com> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org> Signed-off-by: Thomas Huth <thuth@redhat.com> (cherry picked from commit b0dd0a3)
According to our "Supported build platforms" policy, we now do not support Ubuntu 18.04 anymore. Remove the related container files and entries from our CI. Message-Id: <20220516115912.120951-1-thuth@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> Signed-off-by: Thomas Huth <thuth@redhat.com> (cherry picked from commit f3f0cba)
This is needed to be able to add a venv-building step to 'make check'; the clang-user job in particular needs this to be able to run check-unit. Signed-off-by: John Snow <jsnow@redhat.com> Reviewed-by: Paolo Bonzini <pbonzini@redhat.com> Message-Id: <20220526000921.1581503-9-jsnow@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> (cherry picked from commit e184036)
Debian 10 is no longer supported so we have to use
Until we merge up to version 8.0, including these by default will cause the github actions runner to time out.
arichardson
force-pushed
the
github-action
branch
from
2651979 to
af18124
Compare
Apparently the test results produce a 34MB test file which needs this option to be set.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Just running build+test for now with GCC.