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

Teach cargo to failfast on recursive/corecursive aliases #9791

Merged
merged 2 commits into from
Aug 16, 2021

Conversation

nipunn1313
Copy link
Contributor

@nipunn1313 nipunn1313 commented Aug 15, 2021

Eg.
[alias]
test-1 = test-2
test-2 = test-3
test-3 = test-1

Previously it would stack overflow
Pulled out non controversial bits from from #9768

@rust-highfive
Copy link

r? @Eh2406

(rust-highfive has picked a reviewer for you, use r? to override)

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Aug 15, 2021
@nipunn1313 nipunn1313 force-pushed the cargo_crash_alias_loop branch from 829b40d to 5a6c8aa Compare August 15, 2021 01:12
@nipunn1313 nipunn1313 force-pushed the cargo_crash_alias_loop branch from 5a6c8aa to 4a30009 Compare August 15, 2021 05:38
Eg.
[alias]
test-1 = test-2
test-2 = test-3
test-3 = test-1

Previously it would stack overflow

It pulls out non controversial bits from from rust-lang#9768
@nipunn1313
Copy link
Contributor Author

Hit some kind of probably unrelated error https://github.com/rust-lang/cargo/pull/9791/checks?check_run_id=3332095132

---- concurrent::no_deadlock_with_git_dependencies stdout ----
thread 'concurrent::no_deadlock_with_git_dependencies' panicked at 'Deadlock!: Timeout', tests/testsuite/concurrent.rs:506:63
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: test failed, to rerun pass '--test testsuite'

Was unable to repro - maybe something happened in CI?

I'll repush so it reruns

@nipunn1313 nipunn1313 force-pushed the cargo_crash_alias_loop branch from 4a30009 to 28e1289 Compare August 15, 2021 18:27
@alexcrichton
Copy link
Member

Hm how odd! We can always dig in more if it crops up more I suppose. In any case thanks!

@bors: r+

@bors
Copy link
Contributor

bors commented Aug 16, 2021

📌 Commit 28e1289 has been approved by alexcrichton

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Aug 16, 2021
@bors
Copy link
Contributor

bors commented Aug 16, 2021

⌛ Testing commit 28e1289 with merge 531958b...

@bors
Copy link
Contributor

bors commented Aug 16, 2021

☀️ Test successful - checks-actions
Approved by: alexcrichton
Pushing 531958b to master...

@bors bors merged commit 531958b into rust-lang:master Aug 16, 2021
bors added a commit to rust-lang-ci/rust that referenced this pull request Aug 18, 2021
Update cargo

8 commits in b51439fd8b505d4800a257acfecf3c69f81e35cf..e96bdb0c3d0a418e7fcd7fbd69be08abf830b4bc
2021-08-09 18:40:05 +0000 to 2021-08-17 22:58:47 +0000
- Support using rustbot to ping the Windows group (rust-lang/cargo#9802)
- Show information about abnormal `fix` errors. (rust-lang/cargo#9799)
- Bump jobserver. (rust-lang/cargo#9798)
- Render build-std web links as hyperlinks (rust-lang/cargo#9795)
- Teach cargo to failfast on recursive/corecursive aliases (rust-lang/cargo#9791)
- Fix value-after-table error with profiles. (rust-lang/cargo#9789)
- Fix plugin registrar change. (rust-lang/cargo#9790)
- Ability to specify the output name for a bin target different from the crate name (rust-lang/cargo#9627)
@nipunn1313 nipunn1313 deleted the cargo_crash_alias_loop branch September 3, 2021 02:30
@ehuss ehuss added this to the 1.56.0 milestone Feb 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants