Closed choksi81 closed 10 years ago
Author: jsamuel These pass for me on Ubuntu 9.04. I can't repeat the error.
In terms of what could cause these errors:
The only place I see 98 is line 610 of nonportable.py with the comment "# Repy exceeded its resource limit, kill it".
For the exit code of -15, that means it was killed by a signal 15, which is a SIGTERM. So, my guess is that's probably also coming from harshexit but is just the difference of what we see as the exit status of the process on Darwin. (Can anyone confirm or refute this?)
So, where would repy log info about killing the webserver so we can find out what restriction is the culprit, assuming it is a restriction from webserver_restrictions.test being exceeded?
Author: justinc I know what the problem is. If you use 'preparetest -t' to set up the software updater tests, there are too many files and the test are either too slow or over quota for disk (likely the latter).
So I think all is well and we should push.
On both ubuntu 8.10 and testbed-mac when attempting to run the software updater test locally, as described in https://seattle.cs.washington.edu/wiki/UpdaterUnitTests I preformed the following steps:
On ubuntu I got:
On testbed-mac I got:
Note: we've tested r3050 and it's ready to push once this is fixed