Opened 11 years ago
Closed 11 years ago
#5030 closed enhancement (fixed)
gdb-7.7.1
Reported by: | Fernando de Oliveira | Owned by: | Fernando de Oliveira |
---|---|---|---|
Priority: | normal | Milestone: | 7.6 |
Component: | BOOK | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description ¶
Change History (5)
comment:1 by , 11 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:2 by , 11 years ago
Owner: | changed from | to
---|---|
Status: | assigned → new |
comment:3 by , 11 years ago
For now, the number of failures/errors seem to depend on many variables.
- Compilers installed (Fortran, Ada, etc.).
- Tests made locally or remotely.
- Some timeout variable.
- Some environment variables being set or not.
Other problems:
- Time for the tests is more than 13 SBU.
- Very different reasons for the failures, I did not mention, because do not remember anymore.
- The numbers are big: over 40000 tests, almost 1000 unexpected failures, etc.
- Unexpected Success: 1.
My last results were:
# of expected passes 41283 # of unexpected failures 805 # of unexpected successes 1 # of expected failures 82 # of known failures 66 # of unresolved testcases 37 # of untested testcases 55 # of unsupported tests 150
Changing value of the somethin?timeout env variable, numbers of failures changes, but what got me out is that the total number of tests is not conserved.
I have the impression that the tests of this package are for the package developers and we should remove from the book.
I am almost ready to update the package, without considering the tests.
I may be wrong in all I wrote above, that is the reason for giving back to the book. I think soem people with more patience and/or knowledge could do a better judgement.
comment:4 by , 11 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
I will "not recommend" the tests.
Please, if someone disagrees, feel free to fix.
Too many problems with the tests.