-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SIGILL in a heavy test #3783
Comments
It's not
I think |
Hi, thanks a lot for your super fast answer! I forked the project this morning, the last commit seems to be the master tip: 6f0d8db
I think so as well, the trace states it panicked while panicking:
What I would actually try to do is have the test pass (and maybe figure out what is going on, because it seems like #3754 didnt completely fix it) |
yeah, I can rerproduce the problem locally. @o0Ignition0o if you have time to look into this, go for it! Otherwise, I'll try to fix this later today, flaky tests are bad. |
Ah, bummer.
Yeah, that's probably the reason it aborts in that way.
I think so, but I have no idea what's wrong :-). |
actually, let me take a look at this rn, as it blocks other PRs... |
3777: Add basic task support r=matklad a=Timmmm This adds basic support for running `cargo build`, `cargo run`, etc. Fixes #1935 I have tested this and it seems to work. There are two things I'm not sure about: 1. The workspace folder handling seems wrong - just get the first workspace folder? Is this just a TODO item? I don't know if it is right to lift `workspaceFolder` up to `activate()` but I couldn't see another way. 2. If you manually add an entry to `tasks.json` like this: ``` { "type": "cargo", "command": "build", "problemMatcher": [ "$rustc" ], "group": "build" } ``` then VSCode somehow magically knows to run `cargo build`. The documentation for `resolveTask` *sounds* like I should have to implement that for it to work: ``` * Resolves a task that has no [`execution`](#Task.execution) set. Tasks are * often created from information found in the `tasks.json`-file. Such tasks miss * the information on how to execute them and a task provider must fill in * the missing information in the `resolveTask`-method. ``` But then it also says this: ``` * This method will not be * called for tasks returned from the above `provideTasks` method since those * tasks are always fully resolved. A valid default implementation for the * `resolveTask` method is to return `undefined`. ``` Either way, it works without implementing it so the only thing I can think is that it is doing some kind of crazy pattern matching of the tasks returned by `provideTasks()` and the ones found in `tasks.json`. 3784: Ignore createProgress request in tests r=matklad a=matklad closes #3783 bors r+ 🤖 Co-authored-by: Tim <tdhutt@gmail.com> Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>
Automatic Rustup
As I was running heavy tests for #3781, I stumbled upon a SIGILL for test
preserves_dos_line_endings
:The command I ran was:
Here's the output I got:
I would love to figure it out, if you can assign it to me :)
The text was updated successfully, but these errors were encountered: