Jukka Lehtosalo
Jukka Lehtosalo
Looking at the readmes of the different GitHub image versions, none of the changes seem particularly likely to have caused this. Since the failures are somewhat random, it's possible that...
It looks like `fudge_dir_mtimes` used in `mypyc/test/test_run.py` doesn't work reliably any more in GitHub actions. We could replace it with `sleep(1)`, but that would slow down tests. One option would...
I tried moving mtime back 10 seconds but it didn't help.
Now I'm seeing the failure locally using master, on Ubuntu 20.04. I wonder if an Ubuntu upgrade broke the tests. At least this makes it easier to debug the failures.
I merged a workaround that adds a `sleep(1)` on Linux, but it would be nice to figure out the root cause and fix the tests without making them slower.
@hukkinj1 A good point. We could try to get this included in the next public release as a breaking change, perhaps, if there no good arguments against this. cc @ilevkivskyi
`TypedDict({'foo': int, 'bar': bool})` generates a `TypeError` at runtime. To properly support this we'd need changes to `typing.TypedDict`.
> I scheduled for Monday, Sep 26, 5PM Dublin time. That's 9am Pacific.
> FWIW I like this idea, @JukkaL what do you think? Showing error codes by default sounds good to me. We probably still give the misc error code too often...
This is a pretty subtle issue. The `update` call is arguably not type safe. In a more complex program, the argument could be a value of a subtype of `B`...