Uh oh!
There was an error while loading. Please reload this page.
Update WIT definitions, add tests & CI infra - #7
Conversation
30919ef to
a279d39Compare
erikrose
left a comment
There was a problem hiding this comment.
Hooray! Looking great! Just a few notes.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
29f294e to
c239fccCompareFind an available port and use that for a given test run to avoid interference with other running viceroy instances or services on the local machine.
We key off extra output included when running the server in verbose mode to know when viceroy is ready.
A lot of the extra stuff we had for logging exceptions and such aren't required any longer as the WASI bits are working as they ought to, so we can gut all of that. Also, fixed vcpu_time which does return an integer number of milliseconds in the viceroy impl, so assert on that.
8165059 to
ef3406bCompare
erikrose
left a comment
There was a problem hiding this comment.
So nice to get rid of that 10s sleep. :-D
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We are using these helpers internally and it probably makes sense to have some sort of easier setup for end users. This is the first stab at making that available. Along with those changes, I also incorporated a few chanes to reduce the code for viceroy setup using asyncio (still a bit verbose but is working) and a few other small tweaks. The plugin to get Viceroy output on failure is a hack and we may scrap or have to revisit other approaches (e.g. just immediately outputting to host stdout/stderr) but it is functional and may be a reasonable approach (if ugly in implementation).
Uh oh!
There was an error while loading. Please reload this page.
5c8041a to
2bc81e9CompareWe hide the viceroy_server by making it be an autouse fixture on the class which lets us clean things up a fair bit. It stands to reason that all viceroy based tests will want a server.
erikrose
left a comment
There was a problem hiding this comment.
Looking good. I just want to conclude the threads on mark.integration and the lock that I was curious about.
Uh oh!
There was an error while loading. Please reload this page.
| Returns: | ||
| requests.Response: The HTTP response | ||
| """ | ||
| timeout = kwargs.pop("timeout", self.REQUEST_TIMEOUT) |
There was a problem hiding this comment.
It'd be nice to lift timeout up into the function signature. Not a blocker. More a note to my future self.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| ```bash | ||
| make test # Build and run tests | ||
| pytest -m integration # Run integration tests only |
No description provided.