Skip to content
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

Task failed to compile shader #340

Closed
astrieanna opened this issue Apr 7, 2013 · 6 comments
Closed

Task failed to compile shader #340

astrieanna opened this issue Apr 7, 2013 · 6 comments

Comments

@astrieanna
Copy link
Contributor

@astrieanna astrieanna commented Apr 7, 2013

I finally got servo to build today, but make check results in errors in rust-css and running the executable anyway results in immediate errors from rendergl.rs.
I'm on Fedora 18, 64-bit.

When I run make check, it ends with errors:

make check: rust-css
make[1]: Entering directory `/home/leah/src/servo/build/src/rust-css'
/home/leah/src/servo/build/src/rust/x86_64-unknown-linux-gnu/stage2/bin/rustc -A default_methods -O -L /home/leah/src/servo/build/src/rust-netsurfcss -L /home/leah/src/servo/build/src/rust-wapcaplet /home/leah/src/servo/src/rust-css/css.rc -o css-test --test
/home/leah/src/servo/src/rust-css/test.rs:7:4: 7:20 error: unresolved name
/home/leah/src/servo/src/rust-css/test.rs:7 use std::cell::Cell;
                                                ^~~~~~~~~~~~~~~~
/home/leah/src/servo/src/rust-css/test.rs:7:4: 7:20 error: failed to resolve import: std::cell::Cell
/home/leah/src/servo/src/rust-css/test.rs:7 use std::cell::Cell;
                                                ^~~~~~~~~~~~~~~~
/home/leah/src/servo/src/rust-css/color.rs:194:8: 194:23 error: unresolved name
/home/leah/src/servo/src/rust-css/color.rs:194     use option::unwrap;
                                                       ^~~~~~~~~~~~~~~
/home/leah/src/servo/src/rust-css/color.rs:194:8: 194:23 error: failed to resolve import: option::unwrap
/home/leah/src/servo/src/rust-css/color.rs:194     use option::unwrap;
                                                       ^~~~~~~~~~~~~~~
error: failed to resolve imports
error: aborting due to 5 previous errors
make[1]: *** [css-test] Error 101
make[1]: Leaving directory `/home/leah/src/servo/build/src/rust-css'
make: *** [check-rust-css] Error 2

When I run servo, I get this output:

[leah@localhost build]$ ./servo ../src/test/about-mozilla.html
error: 0
rust: task failed at 'failed to compile shader', /home/leah/src/servo/src/rust-layers/rendergl.rs:79
rust: task failed at 'connection closed', /home/leah/src/servo/src/rust/src/libcore/option.rs:300
rust: task failed at 'killed', /home/leah/src/servo/src/rust/src/libcore/pipes.rs:314
rust: task failed at 'killed', /home/leah/src/servo/src/rust/src/libcore/pipes.rs:314
rust: task failed at 'killed', /home/leah/src/servo/src/rust/src/libcore/pipes.rs:314
rust: task failed at 'killed', /home/leah/src/servo/src/rust/src/libcore/pipes.rs:314
rust: task failed at 'killed', /home/leah/src/servo/src/rust/src/libcore/pipes.rs:314
rust: domain main @0xb3e940 root task failed
rust: task failed at 'killed', /home/leah/src/servo/src/rust/src/libcore/pipes.rs:314
leaked memory in rust main loop (48 objects)
servo: /home/leah/src/servo/src/rust/src/rt/memory_region.cpp:189: memory_region::~memory_region(): Assertion `false' failed.
Aborted (core dumped)
@klutzy
Copy link
Contributor

@klutzy klutzy commented Apr 7, 2013

It seems that test codes are not updated for current Rust: for example cell module is moved from std to core.

@metajack
Copy link
Contributor

@metajack metajack commented Apr 7, 2013

#328 is the bug for the rust-css tests. This is a known problem, and I'm working on a fix. Once you get past the superficial things, there are some borrow checker problems that are not easy to resolve. I have added some things to Rust standard libraries in order to address this, and now that they've landed hopefully rust-css will get updated tomorrow.

I haven't seen the task failed to compile shader issue before. We'll try to reproduce.

@astrieanna
Copy link
Contributor Author

@astrieanna astrieanna commented Apr 9, 2013

I git pulled yesterday afternoon, and it suddenly stopped crashing. I now get a blank, bright-blue window instead.

@metajack
Copy link
Contributor

@metajack metajack commented May 16, 2013

Is this still happening @astrieanna ?

@astrieanna
Copy link
Contributor Author

@astrieanna astrieanna commented May 16, 2013

@metajack No; as I commented above a month ago, it stopped crashing after I pulled again. (I haven't tried it since then.)

@metajack
Copy link
Contributor

@metajack metajack commented May 16, 2013

I meant the bright blue window, which is not the expected behavior. Perhaps it was just the color swap combined with missing fonts. The color swap should now be fixed on master and installing msttcorefonts should solve the missing text.

I'll close this bug since there are already issues for those other things.

@metajack metajack closed this May 16, 2013
ChrisParis pushed a commit to ChrisParis/servo that referenced this issue Sep 7, 2014
Update tests to use normal/long harness timeouts
glennw pushed a commit to glennw/servo that referenced this issue Jan 16, 2017
Add interim support for (brute force) primitive visibility

culling until we do it properly in flatten().

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/webrender/340)
<!-- Reviewable:end -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.