[gem5-dev] Re: The Nightly Build system is now Live (Compiler tests too!)
Thanks Bobby and Mike! These are amazing news Giacomo From: Bobby Bruce via gem5-dev Sent: 27 July 2020 19:55 To: gem5 Developer List Cc: Bobby Bruce Subject: [gem5-dev] The Nightly Build system is now Live (Compiler tests too!) Dear all, After some tinkering, we now have a nightly build system deployed, run from our Jenkins: https://jenkins.gem5.org. If I've set up the permissions correctly, everyone should be able to see the status of all our builds from there. Please note, at the time of writing, we're still experimenting with other testing/building setups, so there may be builds there that I haven't explained in this email. These can be ignored. Right now, the Nightly Builds compile the NULL, ARM, MIPS, POWER, RISCV, SPARC, and X86 ".opt" variants of gem5, run the unit tests (those executed via `scons build/null/unittests.opt`), and the "long" testlib regression tests (those executed via `scons ./main.py run --length long` from the `tests` directory) on the gem5 develop branch. In order to test that our email provider is functioning correctly, I've set this up to send an email to the gem5-dev mailing list on success or failure, though once I've confirmed the email notifications are working correctly I'll switch this to send on failure only. The nightly builds will execute every day at 11PM PST (6AM UTC). They take around 6 to 7 hours to complete, therefore normally finishing around 6 to 7 AM PST (1PM to 2PM UTC). The email sent on the failure will list the commits included since the last run (in addition to the stdout/stderr logs, and a link to an archive of the `test/.testing-results` directory) which should help us narrow down any cause-of-failure. In addition to the Nightly Builds, there are also Compile Tests, which I've setup to run every Wednesday. These take roughly 24 hours to complete in our current setups, so expect results on Thursdays. The Compiler Tests simply run the `./util/compiler-tests.sh` script on the develop branch. In short, these run all variants of gem5, ".opt" and '.fast", across all major versions of our supported compilers (not a complete cross product, but decent coverage -- please see the script if you want to know exactly what's run). That's pretty much it for now. We've got plans to expand what's tested in the near future: running more tests, more frequently, as well as improve testing for gem5 in general. I hope this email has given a decent overview of what's going on, but please don't hesitate to get in contact with me if you have any questions. I'd also like to take this opportunity to thank Mike Upton for helping us set up the Jenkins server and deal with all the teething problems. His assistance is much appreciated. Kind regards, Bobby -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. ___ gem5-dev mailing list -- gem5-dev@gem5.org To unsubscribe send an email to gem5-dev-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
[gem5-dev] Re: The Nightly Build system is now Live (Compiler tests too!)
It's running on a Google Cloud VM. We're currently getting a feel for what kind of processing power we need, especially as we start to expand and automate more testing over the next few months. So, right now, this gives us flexibility. There are plenty of ways to expand from here: a beefier VM, dedicated notes to spin jobs off to, etc. FYI (bit of an @all): Seems like Jenkins doesn't like pestering people with emails if a built was successful, so no email last night. I'm looking forward to seeing our first failure be posted here (well, kinda...), but if you want to see our tests passing, just visit https://jenkins.gem5.org :). Kind regards, Bobby -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Mon, Jul 27, 2020 at 11:48 PM Ciro Santilli wrote: > Fantastic!!! > > Which infrastructure does it run on? Google Cloud or something else? > -- > *From:* Bobby Bruce via gem5-dev > *Sent:* Monday, July 27, 2020 7:54 PM > *To:* gem5 Developer List > *Cc:* Bobby Bruce > *Subject:* [gem5-dev] The Nightly Build system is now Live (Compiler > tests too!) > > Dear all, > > After some tinkering, we now have a nightly build system deployed, run > from our Jenkins: https://jenkins.gem5.org. If I've set up the > permissions correctly, everyone should be able to see the status of all our > builds from there. Please note, at the time of writing, we're still > experimenting with other testing/building setups, so there may be builds > there that I haven't explained in this email. These can be ignored. > > Right now, the Nightly Builds compile the NULL, ARM, MIPS, POWER, RISCV, > SPARC, and X86 ".opt" variants of gem5, run the unit tests (those executed > via `scons build/null/unittests.opt`), and the "long" testlib regression > tests (those executed via `scons ./main.py run --length long` from the > `tests` directory) on the gem5 develop branch. In order to test that our > email provider is functioning correctly, I've set this up to send an email > to the gem5-dev mailing list on success or failure, though once I've > confirmed the email notifications are working correctly I'll switch this to > send on failure only. > > The nightly builds will execute every day at 11PM PST (6AM UTC). They take > around 6 to 7 hours to complete, therefore normally finishing around 6 to 7 > AM PST (1PM to 2PM UTC). The email sent on the failure will list the > commits included since the last run (in addition to the stdout/stderr logs, > and a link to an archive of the `test/.testing-results` directory) which > should help us narrow down any cause-of-failure. > > In addition to the Nightly Builds, there are also Compile Tests, which > I've setup to run every Wednesday. These take roughly 24 hours to complete > in our current setups, so expect results on Thursdays. The Compiler Tests > simply run the `./util/compiler-tests.sh` script on the develop branch. In > short, these run all variants of gem5, ".opt" and '.fast", across all major > versions of our supported compilers (not a complete cross product, but > decent coverage -- please see the script if you want to know exactly what's > run). > > That's pretty much it for now. We've got plans to expand what's tested in > the near future: running more tests, more frequently, as well as improve > testing for gem5 in general. I hope this email has given a decent overview > of what's going on, but please don't hesitate to get in contact with me if > you have any questions. > > I'd also like to take this opportunity to thank Mike Upton for helping us > set up the Jenkins server and deal with all the teething problems. His > assistance is much appreciated. > > Kind regards, > Bobby > -- > Dr. Bobby R. Bruce > Room 2235, > Kemper Hall, UC Davis > Davis, > CA, 95616 > > web: https://www.bobbybruce.net > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > ___ gem5-dev mailing list -- gem5-dev@gem5.org To unsubscribe send an email to gem5-dev-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
[gem5-dev] Re: The Nightly Build system is now Live (Compiler tests too!)
Fantastic!!! Which infrastructure does it run on? Google Cloud or something else? From: Bobby Bruce via gem5-dev Sent: Monday, July 27, 2020 7:54 PM To: gem5 Developer List Cc: Bobby Bruce Subject: [gem5-dev] The Nightly Build system is now Live (Compiler tests too!) Dear all, After some tinkering, we now have a nightly build system deployed, run from our Jenkins: https://jenkins.gem5.org. If I've set up the permissions correctly, everyone should be able to see the status of all our builds from there. Please note, at the time of writing, we're still experimenting with other testing/building setups, so there may be builds there that I haven't explained in this email. These can be ignored. Right now, the Nightly Builds compile the NULL, ARM, MIPS, POWER, RISCV, SPARC, and X86 ".opt" variants of gem5, run the unit tests (those executed via `scons build/null/unittests.opt`), and the "long" testlib regression tests (those executed via `scons ./main.py run --length long` from the `tests` directory) on the gem5 develop branch. In order to test that our email provider is functioning correctly, I've set this up to send an email to the gem5-dev mailing list on success or failure, though once I've confirmed the email notifications are working correctly I'll switch this to send on failure only. The nightly builds will execute every day at 11PM PST (6AM UTC). They take around 6 to 7 hours to complete, therefore normally finishing around 6 to 7 AM PST (1PM to 2PM UTC). The email sent on the failure will list the commits included since the last run (in addition to the stdout/stderr logs, and a link to an archive of the `test/.testing-results` directory) which should help us narrow down any cause-of-failure. In addition to the Nightly Builds, there are also Compile Tests, which I've setup to run every Wednesday. These take roughly 24 hours to complete in our current setups, so expect results on Thursdays. The Compiler Tests simply run the `./util/compiler-tests.sh` script on the develop branch. In short, these run all variants of gem5, ".opt" and '.fast", across all major versions of our supported compilers (not a complete cross product, but decent coverage -- please see the script if you want to know exactly what's run). That's pretty much it for now. We've got plans to expand what's tested in the near future: running more tests, more frequently, as well as improve testing for gem5 in general. I hope this email has given a decent overview of what's going on, but please don't hesitate to get in contact with me if you have any questions. I'd also like to take this opportunity to thank Mike Upton for helping us set up the Jenkins server and deal with all the teething problems. His assistance is much appreciated. Kind regards, Bobby -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net ___ gem5-dev mailing list -- gem5-dev@gem5.org To unsubscribe send an email to gem5-dev-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
