Rust-GCC / Rust-GCC/gccrs

18 unexpected failures in test suite on Darwin PowerPC

Open
#2,184 20 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C++
Stars
2.9k
Forks
231
Avg merge
19h 55m
Merged PRs (30d)
67

Description

# of expected passes		7241
# of unexpected failures	18
# of expected failures		52
# of unsupported tests		2

FAIL: rust/compile/builtin_macro_recurse.rs scan-tree-dump-times gimple ""test1canary"" 1
FAIL: rust/compile/const-issue1440.rs  at line 49 (test for errors, line 48)
FAIL: rust/compile/const-issue1440.rs  at line 61 (test for errors, line 60)
FAIL: rust/compile/const-issue1440.rs (test for excess errors)
FAIL: rust/compile/torture/issue-1432.rs   -O0  (test for excess errors)
FAIL: rust/compile/torture/issue-1432.rs   -O1  (test for excess errors)
FAIL: rust/compile/torture/issue-1432.rs   -O2  (test for excess errors)
FAIL: rust/compile/torture/issue-1432.rs   -O3 -g  (test for excess errors)
FAIL: rust/compile/torture/issue-1432.rs   -Os  (test for excess errors)
FAIL: rust/compile/torture/issue-1432.rs   -O2 -flto -flto-partition=none  (test for excess errors)
FAIL: rust/compile/torture/issue-1432.rs   -O2 -flto  (test for excess errors)
FAIL: rust/execute/torture/loop-condition-eval.rs   -O0  output pattern test
FAIL: rust/execute/torture/loop-condition-eval.rs   -O1  output pattern test
FAIL: rust/execute/torture/loop-condition-eval.rs   -O2  output pattern test
FAIL: rust/execute/torture/loop-condition-eval.rs   -O3 -g  output pattern test
FAIL: rust/execute/torture/loop-condition-eval.rs   -Os  output pattern test
FAIL: rust/execute/torture/loop-condition-eval.rs   -O2 -flto -flto-partition=none  output pattern test
FAIL: rust/execute/torture/loop-condition-eval.rs   -O2 -flto  output pattern test

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the test suite on Darwin PowerPC and inspect the listed rust/compile and rust/execute tests, especially builtin_macro_recurse.rs, const-issue1440.rs, issue-1432.rs, and loop-condition-eval.rs. Compare the diagnostic and output mismatches with the expected test patterns; done means the 18 reported failures are resolved and the suite passes on that target.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers, operating-systems, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.