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.

Sign up for GitHub

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

Jump to bottom

Figure out why pipes in compiletest breaks #3034

Closed
eholk opened this issue Jul 26, 2012 · 2 comments
Closed

Figure out why pipes in compiletest breaks #3034

eholk opened this issue Jul 26, 2012 · 2 comments
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc I-crash Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.
Milestone
old 1.0 milestone

Comments

@eholk
Copy link
Contributor

eholk commented Jul 26, 2012

I had to revert the change to use pipes in compiletest (96c6f57). We were having build failures with an invalid argument error in lock_and_signal. This usually means we are trying to acquire an already-freed lock. We need to figure out why this happens.
@ghost ghost assigned eholk Jul 26, 2012
@eholk
Copy link
Contributor Author

eholk commented Aug 9, 2012

This was due to a race condition which has been fixed by reference counting the task during select.

@eholk eholk closed this as completed Aug 9, 2012
@eholk eholk removed their assignment Jun 16, 2014
bors pushed a commit to rust-lang-ci/rust that referenced this issue May 15, 2021
@nrc
Simplify situations in which the last sub-expr in a bin-op can go mul…
b81b902 
…tiline without making the whole expr multiline

Fixes rust-lang#3034
RalfJung pushed a commit to RalfJung/rust that referenced this issue Aug 21, 2023
@bors
Auto merge of rust-lang#3034 - RalfJung:ra, r=RalfJung
a5ba57e 
update recommended RA config

Looks like rust-analyzer.checkOnSave.overrideCommand got renamed to rust-analyzer.check.overrideCommand.
@rust-log-analyzer
Copy link
Collaborator

The job x86_64-gnu-llvm-15 failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot) 
##[endgroup]
Skipping Set({test::src/tools/tidy}) because it is excluded
##[group]Building stage0 library artifacts (x86_64-unknown-linux-gnu)
    Updating crates.io index
error: the lock file /checkout/Cargo.lock needs to be updated but --locked was passed to prevent this
If you want to try to generate the lock file without accessing the network, remove the --locked flag and use --offline instead.
  local time: Mon Aug 21 10:07:01 UTC 2023
  network time: Mon, 21 Aug 2023 10:07:01 GMT
##[error]Process completed with exit code 1.
Post job cleanup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc I-crash Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.
Projects
None yet
Milestone
old 1.0 milestone
Development

No branches or pull requests
2 participants
@eholk @rust-log-analyzer