Hey Gabe, Right now when there are failures during download, a test fails quietly. I'm not aware of any way to quickly know when this happens. This is definitely far from ideal. I've added a Jira item to change this: https://gem5.atlassian.net/browse/GEM5-948. This isn't the first time this has happened and we should have a clearer message when these problems occur. I'll try to find some time to incorporate this in the coming weeks.
Kind regards, Bobby -- Dr. Bobby R. Bruce Room 2235, Kemper Hall, UC Davis Davis, CA, 95616 web: https://www.bobbybruce.net On Mon, Mar 29, 2021 at 8:34 PM Gabe Black <[email protected]> wrote: > Ok, great, thanks for figuring it out! Is there a way to surface when > there are problems downloading resources like that? Maybe there's a message > that gets buried in a log file that technically exists, it's just not > visible when run through kokoro. If so, that would be a worthwhile problem > to solve, but would be part of a larger effort I would imagine. > > Gabe > > On Mon, Mar 29, 2021 at 10:05 AM Bobby Bruce <[email protected]> wrote: > >> Hey Gabe, >> >> As you can see in my other email, I just fixed this. It was a mess-up on >> my part, I forgot to include the aarch-system tarball in our Google Cloud >> Bucket. TestLib downloads this to run some Arm tests. The reason your tests >> passed locally is you probably had a local, cached version (in >> `tests/gem5/resources/arm` i believe), so your local TestLib didn't try to >> re-download. Kokoro works from a clean environment each time, so always >> downloads the resources it needs to run the tests. >> >> I'm pretty sure the issue is fixed now. >> >> Kind regards, >> Bobby >> -- >> Dr. Bobby R. Bruce >> Room 2235, >> Kemper Hall, UC Davis >> Davis, >> CA, 95616 >> >> web: https://www.bobbybruce.net >> >> >> On Sat, Mar 27, 2021 at 9:13 PM Gabe Black <[email protected]> wrote: >> >>> Hi folks, I've been trying to get a change to pass kokoro tests for a >>> couple days, and I'm about stumped. The change is here: >>> >>> https://gem5-review.googlesource.com/c/public/gem5/+/43347/4 >>> >>> I've run the tests locally and they all pass, and I've even run with the >>> full kokoro docker command which should be about as authentic as it gets, >>> and that passed too. >>> >>> docker run -u $UID:$GID --volume $(pwd):$(pwd) -w $(pwd) >>> gcr.io/gem5-test/ubuntu-20.04_all-dependencies >>> tests/jenkins/presubmit-stage2.sh >>> >>> The log from kokoro doesn't really seem to help either since it just >>> says 6 tests failed, and I can search on the page to see which ones. They >>> all seem to be ARM full system tests, but that's not really enough for me >>> to be able to tell what the problem is. >>> >>> Did something in kokoro just get caught in a weird state? Is there >>> another way to run these tests where I can get something actionable out of >>> them? Any help here would be appreciated. >>> >>> Gabe >>> >>
_______________________________________________ gem5-dev mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
