All of lore.kernel.org
 help / color / mirror / Atom feed
From: raptor <raptor@tvskat.net>
To: lartc@vger.kernel.org
Subject: [LARTC] [tcng8u] make test errors
Date: Thu, 19 Sep 2002 07:52:52 +0000	[thread overview]
Message-ID: <marc-lartc-103242197213932@msgid-missing> (raw)

here are the errors I'm getting
--------------------------------------------
[root@qos tcng]# cat _ref.4609 
<stdin>:1: warning: unused variable x

[root@qos tcng]# cat _out.4609 
<stdin>:17: warning: unused variable x


[root@qos tcng]# cat _in.4609 
$a = { $x = 13; 7; };
field foo = raw if $a = $a;

-------------------------------------------------
bare words for strings are forbidden: PASSED
quoted strings for strings are okay: PASSED
bare words for warning labels are forbidden: PASSED (warning: output differs)
  Standard output:
  | <stdin>:17: syntax error near "nounused"
  Reference output:
  | <stdin>:1: syntax error near "nounused"
quoted strings for warning labels are okay: PASSED
bare words are still okay for device names: PASSED
quoted strings are also okay for device names: PASSED
typos don't turn into strings (1): PASSED

........................................

qdisc collision from distinct blocks is detected (1): PASSED
qdisc collision from distinct blocks is detected (2): PASSED
"inner" blocks are shown correctly in variable use output: PASSED
bucket: can define variables: PASSED
bucket: can use with conform, count: PASSED
bucket: policer parameters are refused: PASSED (warning: output differs)
  Standard output:
  | <stdin>:17: unrecognized parameter "mtu"
  Reference output:
  | <stdin>:1: unrecognized parameter "mtu"

........................

compound construct with multiple assignments: PASSED
compound construct must end with semicolon: PASSED (warning: output differs)
  Standard output:
  | <stdin>:17: syntax error near "}"
  Reference output:
  | <stdin>:1: syntax error near "}"
compound construct may end with multiple semicolons: PASSED
compound construct requires semicolon after assignment: PASSED (warning: output differs)
  Standard output:
  | <stdin>:17: syntax error near "$x"
  Reference output:
  | <stdin>:1: syntax error near "$x"
compound construct allows multiple semicolons after assignment: PASSED
compound construct warns about unused variables: FAILED
File:      tests/compound
Command:   tcc -c 2>&1
Input:     _in.4609
Output:    _out.4609
Reference: _ref.4609
scripts/runtests.sh: line 2:  4633 Broken pipe             cat
scripts/run-all-tests: line 14: 15771 Broken pipe             cat $n
make: *** [test] Error 
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-09-19  7:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-19  7:52 raptor [this message]
2002-09-19  8:29 ` [LARTC] [tcng8u] make test errors raptor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-103242197213932@msgid-missing \
    --to=raptor@tvskat.net \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.