Hi Bjoern, These tests are wildly out of date. I've been considering shutting them down since we started running CI tests on the review site. Now, every changeset must pass the CI tests before it can be merged.
The only downside to killing these tests is that not all of them have been migrated to the CI service. We need help doing this :). Cheers, Jason On Mon, May 27, 2019 at 2:40 PM Bjoern A. Zeeb < [email protected]> wrote: > On 27 May 2019, at 21:28, Cron Daemon wrote: > > > ***** > > build/ALPHA/tests/opt/long/fs/10.linux-boot/alpha/linux/tsunami-o3: > > FAILED! > > ***** > > build/ALPHA/tests/opt/long/fs/10.linux-boot/alpha/linux/tsunami-o3-dual: > > FAILED! > > ***** > > > build/ALPHA/tests/opt/long/fs/10.linux-boot/alpha/linux/tsunami-switcheroo-full: > > > FAILED! > > ***** > > build/NULL/tests/opt/quick/se/60.rubytest/null/none/rubytest-ruby: > > FAILED! > > ***** > > > build/NULL_MOESI_hammer/tests/opt/quick/se/60.rubytest/null/none/rubytest-ruby-MOESI_hammer: > > > FAILED! > > ***** > > > build/NULL_MESI_Two_Level/tests/opt/quick/se/60.rubytest/null/none/rubytest-ruby-MESI_Two_Level: > > > FAILED! > > ***** > > > build/NULL_MOESI_CMP_directory/tests/opt/quick/se/60.rubytest/null/none/rubytest-ruby-MOESI_CMP_directory: > > > FAILED! > > ***** > > > build/NULL_MOESI_CMP_token/tests/opt/quick/se/60.rubytest/null/none/rubytest-ruby-MOESI_CMP_token: > > > FAILED! > > ***** > > build/X86/tests/opt/long/fs/10.linux-boot/x86/linux/pc-o3-timing: > > FAILED! > > ***** > > build/X86/tests/opt/long/fs/10.linux-boot/x86/linux/pc-switcheroo-full: > > FAILED! > > ***** > > > build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64c/simple-timing: > > FAILED! > > ***** > > build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64f/o3-timing: > > FAILED! > > ***** > > build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64c/o3-timing: > > FAILED! > > ***** > > > build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64c/minor-timing: > > FAILED! > > ***** > > > build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64c/simple-timing-ruby: > > > FAILED! > > ***** > > build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64a/o3-timing: > > FAILED! > > ***** > > > build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64c/simple-atomic: > > FAILED! > > ***** > > > build/ALPHA/tests/opt/quick/se/03.learning-gem5/alpha/linux/learning-gem5-p1-simple: > > > CHANGED! > .. > .. > .. > .. is there any interest in actually getting things to pass again or > ..? > > I am mostly wondering, having watched this for a while now, in what > state the current repo is in, and if anything is supposed to work or if > the tests are out of date or ..? > > It doesn’t leave people with a lot of confidence and given there is no > updated stable branch anymore, you simply cannot afford keeping such a > state for long. > > > /bz > _______________________________________________ > gem5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/gem5-dev _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
