|
Bugzilla – Full Text Bug Listing |
| Summary: | test.py should exit if waf dies | ||
|---|---|---|---|
| Product: | ns-3 | Reporter: | Andrey Mazo <ahippo> |
| Component: | test framework | Assignee: | ns-bugs <ns-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | craigdo, gjcarneiro |
| Priority: | P5 | ||
| Version: | ns-3-dev | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: | proposed fix | ||
(In reply to comment #0) > Created an attachment (id=866) [details] > proposed fix Looks good. Craig, you still around? :-) Fixed changeset 1f53e122254b
> Craig, you still around? :-)
No. I find myself in an alternate universe where everything starts with "Q" and there are strange rituals called "meetings".
|
Created attachment 866 [details] proposed fix Currently test.py runs waf by default before executing tests, but doesn't check its return code. So it's possible for waf to die with compilation error and test.py to run tests against mixture of old and new libraries/executables. It may introduce some problems to an inattentive user.